Is the Geo Parity MCP server down?

mcp-registry/com.geo-parity/geo-parity · v0.2.0

unknown
Last checked 2026-10-26 18:33 UTC · handshake 1.5s

As of 2026-10-26 18:33 UTC, the Geo Parity MCP server is unknown with a Glimind reliability score of 76/100 (grade B). Over the last 30 days it answered 99.2% of Glimind's liveness checks. It had 7 outages in 90 days, with a median recovery of 8 minutes.

uptime (30d checks)
99.2%
checks observed
1,008
outages (90d)
7
tools
62

Cost of living, fair global pay, healthcare costs, nomad visas and tax residency. Free, no key.

Point your MCP client at this streamable-http endpoint: https://geo-parity.com/api/mcp

Agent-readiness: C (71/100)

C (71/100): 1 error(s), 3 warning(s) across 62 tool(s); ~21,413 tokens of tool definitions.
Scores higher than 5% of 15,781 MCP servers Glimind has audited.
Its tool list costs an agent ~21,413 tokens per session — more than 95% of servers.
77 → 81 since 2026-10-24
no tool-poisoning patterns
Schemas100
Descriptions74
Safety hints100
Token cost35
Client compatibility100
Protocol100
Reliability0
Stability20

What to fix (5)

The endpoint did not complete an MCP handshake.

Check the URL, TLS certificate and that the server answers a JSON-RPC "initialize" POST. How to fix →

62 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.

Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →

24 parameter(s) across 14 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: check_residency, check_travel_residency, compare_business_entry, compare_childcare_cost, compare_effective_tax and 9 more

Loading this server's tool list costs an agent ~21,413 tokens before any work — more than 95% of MCP servers.

Split rarely-used tools into a separate server or a toolset the client can enable, or expose one "search tools" entry point. Many agents load every connected server's tools into every request. How to fix →

In the last 30 days: 0 tool(s) removed and 37 schema change(s).

Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.geo-parity/geo-parity"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/com.geo-parity/geo-parity"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.geo-parity%2Fgeo-parity.svg)](https://glimind.com/server/mcp-registry%2Fcom.geo-parity%2Fgeo-parity?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fcom.geo-parity%2Fgeo-parity?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.geo-parity%2Fgeo-parity.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.geo-parity%2Fgeo-parity.svg
   :target: https://glimind.com/server/mcp-registry%2Fcom.geo-parity%2Fgeo-parity?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:d7aff2706d3d685c…, first seen 2026-10-17, included at leaf 11693 of 75,760. Version history · verify what your client received.

Tools (62)

Compare: most reliable finance servers · most reliable knowledge servers · most reliable data servers · most reliable search servers · most reliable productivity servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Geo Parity MCP server down right now?

As of 2026-10-26 18:33 UTC, the Geo Parity MCP server is unknown with a Glimind reliability score of 76/100 (grade B). Over the last 30 days it answered 99.2% of Glimind's liveness checks. It had 7 outages in 90 days, with a median recovery of 8 minutes.

How many tools does Geo Parity MCP server provide?

Geo Parity MCP server advertises 62 tools, including arrival_cost, banking_access, build_pay_range, calculate_ppp, calculate_runway.

How do I install Geo Parity MCP server?

Point your MCP client at this streamable-http endpoint: https://geo-parity.com/api/mcp

Is the Geo Parity MCP server safe to connect to an AI agent?

Glimind scanned all 62 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Geo Parity MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve