MCP servers observed by Lowdown
io.github.cometchat/docs-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); 54 tools listed. MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-10; tool definitions last changed on 2026-11-13 after 3 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.cometchat/docs-mcp
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.cometchat/docs-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-13: input or output schemas changed, descriptions changed, tool names changed, server version changed; tool count 4 → 54
What tools does it list?
54 tools on 2026-11-16:
cometchat_add_group_memberscometchat_create_api_keycometchat_create_appcometchat_create_auth_tokencometchat_create_groupcometchat_create_moderation_listcometchat_create_rolecometchat_create_userscometchat_create_webhookcometchat_delete_api_keycometchat_delete_groupcometchat_delete_messagecometchat_delete_moderation_listcometchat_delete_moderation_rulecometchat_delete_push_providercometchat_delete_rolecometchat_delete_userscometchat_delete_webhookcometchat_get_app_credentialscometchat_get_app_settingscometchat_get_plancometchat_get_push_setupcometchat_get_usagecometchat_get_usercometchat_invite_team_membercometchat_list_api_keyscometchat_list_appscometchat_list_call_logscometchat_list_conversationscometchat_list_featurescometchat_list_flagged_messagescometchat_list_group_memberscometchat_list_groupscometchat_list_messagescometchat_list_moderation_listscometchat_list_moderation_rulescometchat_list_rolescometchat_list_teamcometchat_list_userscometchat_list_webhook_triggerscometchat_list_webhookscometchat_remove_group_membercometchat_revoke_auth_tokenscometchat_set_featurecometchat_set_moderation_rulecometchat_set_openai_keycometchat_set_users_activecometchat_update_app_settingscometchat_update_usercometchat_whoamifetch_cometchat_doc_pageget_cometchat_implementation_bundlelist_cometchat_bundlessearch_cometchat_docs
MCP Registry declaration
- Registry name:
io.github.cometchat/docs-mcp - Declared version: 0.2.1
- Status: active
- Declared hosts:
mcp.cometchat.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.cometchat/docs-mcp", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.cometchat/docs-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).