MCP servers observed by Lowdown
io.github.gumlet/mcp MCP server: daily status and tool changes
Answered initialize and tools/list on all 3 checks recorded in the last 30 days (2026-11-10 to 2026-11-16) (Lowdown checks this server every 3 days); 95 tools listed. MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-10; tool definitions last changed on 2026-11-16 after 6 days without change; no agent-reported interactions.
Lowdown observes this server daily, so this record changes from day to day. A copy older than 1 day may be outdated. Current record (JSON): GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.gumlet/mcp
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.gumlet/mcp?menu=install-check · other questions: menu
Does it respond?
Latest daily check: 2026-11-16: the server answered initialize and tools/list.
- Observed days in the last 30: 3
- Answered initialize and tools/list: 3
- Required authentication: 0
- No response: 0
- Remotes differed: 0
Does it require authentication?
It did not return HTTP 401/403 on any of the 3 observed days. Lowdown checks without credentials.
Did its tools change recently?
Tool definitions changed on 1 of 2 compared days.
- 2026-11-16: input or output schemas changed
What tools does it list?
95 tools on 2026-11-16:
add_asset_playlistanalytics_aggregated_dataanalytics_breakdown_dataasset_analyticsasset_audio_uploadasset_status_historyassets_delete_manyassets_tag_manycomplete_audio_uploadcomplete_live_streamcomplete_multipart_uploadcomplete_subtitle_uploadcreate_assetcreate_asset_direct_uploadcreate_foldercreate_image_sourcecreate_live_assetcreate_playlistcreate_profilecreate_update_chaptercreate_webhookcreate_workspacedelete_assetdelete_folderdelete_live_assetdelete_playlistdelete_profiledelete_sourcedelete_webhookdelete_workspacefetch_audit_logsfetch_billing_detailsfetch_orgfetch_upcoming_invoicefetch_userfilter_live_assetsget_all_playlistsget_asset_detailsget_folderget_image_sources_source_idget_live_asset_statusget_playlist_assetsget_profileget_sdkget_workspaceglobal_searchimage_purgeimport_from_vimeoinsights_aggregated_datainsights_breakdown_datainvite_channel_viewersinvite_channel_viewers_csvlist_assetslist_channel_subscriberslist_folderslist_invoiceslist_live_workspaceslist_profileslist_recycle_binlist_sdkslist_sourceslist_webhookslist_workspaceslive_usage_analyticslive_workspace_createlive_workspace_deletelive_workspace_updatemultipart_upload_abortmultipart_upload_listpurge_image_cacherecoverremove_asset_playlistremove_assets_folderremove_channel_viewersreorder_asset_playlistretrieve_analyticsretrieve_image_analyticsretrieve_part_urlstart_livethumbnail_selectthumbnail_uploadthumbnail_upload_livetop_assetsupdate_assetupdate_billing_detailsupdate_folderupdate_image_sourceupdate_live_assetupdate_playlistupdate_profileupdate_webhookupdate_workspaceupload_subtitlesviewer_analytics_datawebhook_history
MCP Registry declaration
- Registry name:
io.github.gumlet/mcp - Declared version: 2.3.7
- Status: active
- Declared hosts:
mcp.gumlet.com
Before installing: how to check
From an agent: add the remote MCP server https://lowdown-proxy.vercel.app/mcp (streamable HTTP, no authentication) and call get_lowdown with {"target": "mcp:io.github.gumlet/mcp", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.gumlet/mcp?menu=install-check
The same facts in machine-readable form are in this page's <script type="application/json" id="lowdown-evidence"> block (schema lowdown.evidence-snapshot v1).