Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

GeezerKeeper Referral Exit Routes and Deadlines

REMOTE · GEEZERKEEPER.COM · SCANNED SEP 20

Read-only senior-care exit routes, duplicate-referral deadlines, and templates; no PII or sending.

Available components

0 this week 90 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security80
Transport & Reachability100
Schema Quality & AI Usability87
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 468 tokens (~52/item across 9 items; 7 tools + 2 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
  • Supports UI / widget rendering.Pass
Install

How do I install the GeezerKeeper Referral Exit Routes and Deadlines MCP server?

GeezerKeeper Referral Exit Routes and Deadlines is a hosted endpoint at https://geezerkeeper.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · geezerkeeper.com

# add to Claude Code
claude mcp add --transport http com-geezerkeeper-referral-exit-routes 'https://geezerkeeper.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-geezerkeeper-referral-exit-routes": {
      "url": "https://geezerkeeper.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-geezerkeeper-referral-exit-routes": {
      "type": "http",
      "url": "https://geezerkeeper.com/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.com-geezerkeeper-referral-exit-routes]
url = "https://geezerkeeper.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-geezerkeeper-referral-exit-routes": {
      "type": "remote",
      "url": "https://geezerkeeper.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-geezerkeeper-referral-exit-routes --url 'https://geezerkeeper.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-geezerkeeper-referral-exit-routes:
    url: "https://geezerkeeper.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-geezerkeeper-referral-exit-routes": {
      "Transport": "http",
      "Url": "https://geezerkeeper.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add com-geezerkeeper-referral-exit-routes -t streamable-http -u 'https://geezerkeeper.com/mcp'
// mcp.json
{
  "mcpServers": {
    "com-geezerkeeper-referral-exit-routes": {
      "type": "http",
      "url": "https://geezerkeeper.com/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 26 Aug 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 26 0
    • Stability: 0.97 → pass security
  • 24 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 31 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Jul 26 0

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Probed https://geezerkeeper.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=geezerkeeper.com CN=YE2,O=Let's Encrypt,C=US 19 Sept 2026 18 Dec 2026 ECDSA 256 ECDSA-SHA384 673c35dbb6234d0412faa211274563c9cd2
SANs: geezerkeeper.ai, geezerkeeper.com, geezerkeepers.ai, geezerkeepers.com, www.geezerkeeper.ai, www.geezerkeeper.com, www.geezerkeepers.ai, www.geezerkeepers.com
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of geezerkeeper.com. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
geezerkeeper.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000
x-content-type-options nosniff
x-frame-options DENY
referrer-policy no-referrer
permissions-policy camera=(), microphone=(), geolocation=(), payment=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://geezerkeeper.com/mcp Verified 200
http (plaintext) http://geezerkeeper.com/mcp HTTPS enforced 301 https://geezerkeeper.com/mcp
MCP tools · 7 exposed · ~415 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
choose_private_workflow ~79

Choose the free, $19 consumer, or $59 professional option using only recipient count and intended use. No personal information is accepted.

NameTypeReqDescription
professionalUsebooleanTrue for a practice, firm, or senior living location sharing handouts or tracking referral chronology and deadlines
recipientCountintegeryesNumber of identifiable organizations to track
NameTypeReqDescription
alternativesobjectyes
dataHandlingobjectyes
nextActionUrlstringyes
reasonstringyes
recommendationobjectyes
userFacingSummarystringyes

No examples provided.

get_info ~38

Return canonical public business identity, contact, pricing range, and privacy-boundary information (PUBLICMCP v0.3). Accepts no inputs.

Input schema present but exposes no named parameters.

NameTypeReqDescription
business_typearrayyes
categorystringyes
contactobjectyes
data_boundaryobjectyes
descriptionstringyes
logostringyes
namestringyes
opening_hoursarrayyes
price_rangestringyes
publicmcp_versionstringyes
social_profilesobjectyes
taglinestringyes
websitestringyes

No examples provided.

get_location ~29

Return online delivery and U.S. service coverage without exposing a private street address or accepting a location input.

Input schema present but exposes no named parameters.

NameTypeReqDescription
geonullyes
geo_radiusnullyes
headquartersstringyes
officesarrayyes
remote_capablebooleanyes
scope_notestringyes
service_areasarrayyes

No examples provided.

get_services ~55

Return the current free, $19 consumer, and $59 professional self-serve options. The optional category is enumerated and cannot carry personal information.

NameTypeReqDescription
categorystringFilter: all, free, consumer, or professional
NameTypeReqDescription
servicesarrayyes

No examples provided.

get_unfilled_request_template ~82

Return 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.

NameTypeReqDescription
recipientTypestringyesReturn a template for the referral network or for one identified provider
sourceIdstringyesUsed only to return the current source-specific destination and instructions
NameTypeReqDescription
dataBoundaryobjectyes
destinationyes
disclaimerstringyes
recipientTypestringyes
sourceIdstringyes
templateobjectyes

No examples provided.

lookup_duplicate_referral_deadline ~72

Return 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 information.

NameTypeReqDescription
networkstringFilter: all, caring, or apfm
NameTypeReqDescription
dataBoundaryobjectyes
disclaimerstringyes
policiesarrayyes
professionalFitobjectyes
reviewedAtstringyes

No examples provided.

lookup_exit_route ~60

Return a maintained stop-contact and privacy route for one supported senior-care referral network. Input is only a network identifier; never provide personal information.

NameTypeReqDescription
sourceIdstringyesReferral network: apfm, caring, seniorly, or seniorhousingnet
NameTypeReqDescription
dataBoundaryobjectyes
disclaimerstringyes
guideUrlstringyes
nextStepstringyes
reviewedAtstringyes
routeobjectyes

No examples provided.

Common questions

What is the GeezerKeeper Referral Exit Routes and Deadlines MCP server?

GeezerKeeper Referral Exit Routes and Deadlines is an MCP server listed in the public MCP registry as com.geezerkeeper/referral-exit-routes. Read-only senior-care exit routes, duplicate-referral deadlines, and templates; no PII or sending. This page covers its hosted endpoint (https://geezerkeeper.com/mcp).

Is the GeezerKeeper Referral Exit Routes and Deadlines MCP server safe to use?

GeezerKeeper Referral Exit Routes and Deadlines scores 90 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the GeezerKeeper Referral Exit Routes and Deadlines MCP server expose?

GeezerKeeper Referral Exit Routes and Deadlines exposes 7 tools: get_info, get_services, get_location, lookup_duplicate_referral_deadline, lookup_exit_route, and 2 more. Their descriptions and schemas cost roughly 415 tokens of context every time the server is loaded.

Does the GeezerKeeper Referral Exit Routes and Deadlines MCP server require authentication?

No. We connected to GeezerKeeper Referral Exit Routes and Deadlines without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the GeezerKeeper Referral Exit Routes and Deadlines MCP server still maintained?

GeezerKeeper Referral Exit Routes and Deadlines is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.