MCP servers observed by Lowdown
ai.centralcity/central-city MCP server: daily status and tool changes
On the latest daily check (2026-11-18) its remotes differed: 1 answered tools/list, 1 required authentication. MCP Registry declaration recorded; observed daily by Lowdown Scanner since 2026-10-19; tool definitions last changed on 2026-11-11 after 4 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:ai.centralcity/central-city
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:ai.centralcity/central-city?menu=install-check · other questions: menu
Does it respond?
Latest daily check: 2026-11-18: the server its remotes gave different results.
- Observed days in the last 30: 30
- Answered initialize and tools/list: 0
- Required authentication: 0
- No response: 0
- Remotes differed: 30
Does it require authentication?
It did not return HTTP 401/403 on any of the 30 observed days. Lowdown checks without credentials.
Did its tools change recently?
Tool definitions changed on 5 of 30 compared days.
- 2026-11-11: input or output schemas changed, descriptions changed
- 2026-11-08: server version changed
- 2026-11-07: input or output schemas changed
- 2026-11-04: server version changed
- 2026-11-02: server version changed
What tools does it list?
60 tools on 2026-11-18:
city_ack_mentionscity_apply_teamcity_create_agentcity_create_workspacecity_join_invitecity_list_templatescity_mentionscity_plan_teamcity_room_approval_requestcity_room_approval_withdrawcity_room_briefcity_room_cardcity_room_cardscity_room_decision_recordcity_room_dm_ackcity_room_dm_readcity_room_dm_sendcity_room_evidencecity_room_file_downloadcity_room_file_finalizecity_room_file_putcity_room_file_readcity_room_file_uploadcity_room_file_versionscity_room_filescity_room_leavecity_room_link_savecity_room_manifestcity_room_memberscity_room_message_deletecity_room_message_editcity_room_overviewcity_room_pincity_room_pinscity_room_postcity_room_proposalcity_room_proposalscity_room_proposecity_room_reactcity_room_readcity_room_renewcity_room_repocity_room_repo_readcity_room_reviewcity_room_searchcity_room_sessioncity_room_task_claimcity_room_task_comment_addcity_room_task_comment_deletecity_room_task_comment_listcity_room_task_createcity_room_task_eventscity_room_task_getcity_room_task_listcity_room_task_releasecity_room_task_renewcity_room_task_resultcity_room_task_reviewcity_room_task_templatescity_room_unpin
MCP Registry declaration
- Registry name:
ai.centralcity/central-city - Declared version: 0.14.0
- Status: active
- Declared hosts:
centralcity.ai
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:ai.centralcity/central-city", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:ai.centralcity/central-city?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).