
GeezerKeeper MCP server
Which MCP servers are GeezerKeeper's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-24
- Registry namecom.geezerkeeper/referral-exit-routesverified in the MCP registry
The registry name sits under geezerkeeper.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-24
- Tools7
- Server calls itselfgeezerkeeper-referral-exit-routes
- Server version1.2.0
- Protocol version2025-06-18
On 2026-10-24 the server answered initialize and tools/list without a sign-in. First answer in 328 ms.
- Whether its tools do the product's job has not been judged yet.
Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.
- INITE MCP score100 of 100answers 100 · definitions 100 · context 100 · connects 100
- Answered100% of days11 of 11 daily checks
- Median first answer377 ms
- Space in an agent's context≈ 905 tokensthe definitions of all its tools (7), which an agent carries on every turn
- Tool definitionsA · 100 of 100
- Typed results7 of 7 toolsdeclared outputSchema: results come typed, read once
- Every tool passes all six checks.
What an agent can do with it
- not sure · map stop-contact jobs for each provider that called
- not sure · draft opt-out requests to referral sources
- cannot · track replies and reminders for each provider request
Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?
Worth a look
None of the five warning signs in these definitions.
A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →
get_infoReturn canonical public business identity, contact, pricing range, and privacy-boundary information (PUBLICMCP v0.3). Accepts no inputs.
get_servicesReturn the current free, $19 consumer, and $59 professional self-serve options. The optional category is enumerated and cannot carry personal information.
get_locationReturn online delivery and U.S. service coverage without exposing a private street address or accepting a location input.
lookup_duplicate_referral_deadlineReturn source-maintained public duplicate-referral deadline and reporting-route facts for Caring.com or A Place for Mom, plus the current professional tracking fit. Input is only an enumerated network; never provide lead or prospect…
lookup_exit_routeReturn a maintained stop-contact and privacy route for one supported senior-care referral network. Input is only a network identifier; never provide personal information.
get_unfilled_request_templateReturn an unfilled template for a referral network or an identifiable provider. The server accepts no personal fields and never sends the request. Replace bracketed placeholders locally.
choose_private_workflowChoose the free, $19 consumer, or $59 professional option using only recipient count and intended use. No personal information is accepted.
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"referral-exit-routes": {
"type": "http",
"url": "https://geezerkeeper.com/mcp"
}
}
}Add it
Claude Code, in a terminal
claude mcp add --transport http geezerkeeper https://geezerkeeper.com/mcpclaude.ai, ChatGPT and other clients: add https://geezerkeeper.com/mcp as a custom connector in the settings.
OpenAPI spec
8 paths, read 2026-10-24. Open the spec ↗
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.