Geo-Parity
https://geo-parity.com/api/mcpGeo-Parity answers the questions that come up when work, pay or life crosses a border. Give it an income and a destination and it returns what you would actually keep after rent, everyday prices, out-of-pocket healthcare and income tax; the local wage ladder from the survival floor to the top 1%, so the answer can be checked against what people there really earn; which digital-nomad visas that income qualifies for and which of them lead to residency; how far a passport reaches visa-free; Schengen 90/180 and per-country tax-residency day limits; the working days a distributed team genuinely shares once public holidays are counted, not just the overlapping hours; measured internet latency and jitter rather than headline megabits, because a video call fails on delay long before it fails on throughput; monthly climate normals; and country risk. 25 tools over published data — World Bank, IMF, OECD, Penn World Table, Eurostat, WHO, HUD, Open-Meteo (ERA5) and Cloudflare Radar. Every result carries its own citation: which dataset, which provider, which reference year, and a permalink to the page that answers the same question. Where a figure is modelled rather than measured, the response says so. Estimates for orientation, not tax, legal or financial advice. Free and key-less. No account, no API key, no sign-up — connect the URL and every tool works. Generous anonymous limits per IP; an optional key raises them without changing any response.
MCP readiness
Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here B, 79.8/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ
| Valid MCP handshake | 10/10 | initialize and tools/list both answered. |
| Live MCP endpoint | 25/25 | Endpoint answers the MCP initialize handshake (1100 ms). |
| Protocol revision | 10/10 | Speaks the current MCP revision 2026-07-28. |
| Signed descriptor | n/a | No MCP standard defines a signed server descriptor. |
| Uptime (30 days) | 15/15 | 30/30 probes succeeded over 30 days (100%). |
| Tool declaration | 10/10 | Lists 60 tool(s) with descriptions. |
| Verified identity | 7/10 | Namespace verified by the official MCP Registry (GitHub or DNS proof at publish time). |
| Freshness + modern flags | 0/5 | not seen in a source for over 30 days. |
| Auth declaration | 0/5 | How to authenticate is not stated. |
Compared with peers
Against 53,039 reachable MCP servers in our daily snapshot (2026-11-12 06:46 UTC). Display only; it does not change search order.
- Readiness
- Higher than 80% of peers
- This listing 86 · peer median 81
- Latency
- Faster than 21% of peers
- This listing 615 ms · peer median 326 ms
Where it loses the most points, and how to win them back
- Freshness + modern flags −5
— Keep the listing current in the registry or source it comes from.
Now: not seen in a source for over 30 days.
- Auth declaration −5
— State how to authenticate (an auth scheme, or that none is needed).
Now: How to authenticate is not stated.
- Verified identity −3
— Claim the listing and prove control of its domain.
Now: Namespace verified by the official MCP Registry (GitHub or DNS proof at publish time).
Listed in
Directories this entry was found in.
How to connect
https://geo-parity.com/api/mcpcurl -X POST https://geo-parity.com/api/mcp \
-H 'Content-Type: application/json' \
-H 'Accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'