MCP servers observed by Lowdown
dev.geocodeai/geocode 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); 43 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:dev.geocodeai/geocode
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:dev.geocodeai/geocode?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: descriptions changed, server version changed
What tools does it list?
43 tools on 2026-11-16:
comment_on_feedbackcontains_pointscreate_api_keycreate_areacreate_checkout_linkdelete_fileexport_boundaryget_accountget_billing_linkget_boundaryget_email_preferencesget_feedbackget_fileget_my_reviewget_pricingget_subscriptionget_usagelist_api_keyslist_audit_loglist_childrenlist_feedbacklist_fileslist_inviteslist_memberslist_my_feedbacklist_orgslist_reviewslist_teamsremove_feedback_votereport_issuerequest_featurereverse_boundariesrevoke_api_keysave_filesearch_boundariesshare_filesubmit_reviewunion_boundariesunshare_fileupdate_email_preferencesupdate_fileupdate_profileupvote_feedback
MCP Registry declaration
- Registry name:
dev.geocodeai/geocode - Declared version: 1.0.2
- Status: active
- Declared hosts:
geocodeai.dev
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:dev.geocodeai/geocode", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:dev.geocodeai/geocode?menu=install-check
When running its declared package, wrap it with the stdio proxy. Since lowdown-proxy 0.1.22 the proxy adds this record (install-check) to the server's initialize response; it changes no tool result and blocks nothing:
npx -y lowdown-proxy --target mcp:dev.geocodeai/geocode -- npx -y @meterapp/geocode
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).