GeezerKeeper Referral Exit Routes and Deadlines
REMOTE · GEEZERKEEPER.COM
Read-only senior-care exit routes, duplicate-referral deadlines, and templates; no PII or sending.
Available components
Last scanned (20 hours ago)
Scores higher than 98% of remote servers
Reachable. Last reached 5 Nov 2026.
Category CRM and Sales
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
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
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
Checks we ran (14)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
- Capabilities
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 28 Sept 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
- 25 Sept 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 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
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 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
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 5 Nov 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. | DS published | 19718 | 13 | Verified |
| geezerkeeper.com. | No DS | 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 |
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 →
choose_private_workflow Choose the smallest GeezerKeeper workflow ~79
Choose the free, $19 consumer, or $59 professional option using only recipient count and intended use. No personal information is accepted.
| Name | Type | Req | Description |
|---|---|---|---|
| professionalUse | boolean | – | True for a practice, firm, or senior living location sharing handouts or tracking referral chronology and deadlines |
| recipientCount | integer | yes | Number of identifiable organizations to track |
| Name | Type | Req | Description |
|---|---|---|---|
| alternatives | object | yes | – |
| dataHandling | object | yes | – |
| nextActionUrl | string | yes | – |
| reason | string | yes | – |
| recommendation | object | yes | – |
| userFacingSummary | string | yes | – |
No examples provided.
get_info Get canonical GeezerKeeper business information ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| business_type | array | yes | – |
| category | string | yes | – |
| contact | object | yes | – |
| data_boundary | object | yes | – |
| description | string | yes | – |
| logo | string | yes | – |
| name | string | yes | – |
| opening_hours | array | yes | – |
| price_range | string | yes | – |
| publicmcp_version | string | yes | – |
| social_profiles | object | yes | – |
| tagline | string | yes | – |
| website | string | yes | – |
No examples provided.
get_location Get GeezerKeeper delivery coverage ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| geo | null | yes | – |
| geo_radius | null | yes | – |
| headquarters | string | yes | – |
| offices | array | yes | – |
| remote_capable | boolean | yes | – |
| scope_note | string | yes | – |
| service_areas | array | yes | – |
No examples provided.
get_services Get GeezerKeeper services and current prices ~55
Return the current free, $19 consumer, and $59 professional self-serve options. The optional category is enumerated and cannot carry personal information.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Filter: all, free, consumer, or professional |
| Name | Type | Req | Description |
|---|---|---|---|
| services | array | yes | – |
No examples provided.
get_unfilled_request_template Get an unfilled stop-contact 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.
| Name | Type | Req | Description |
|---|---|---|---|
| recipientType | string | yes | Return a template for the referral network or for one identified provider |
| sourceId | string | yes | Used only to return the current source-specific destination and instructions |
| Name | Type | Req | Description |
|---|---|---|---|
| dataBoundary | object | yes | – |
| destination | – | yes | – |
| disclaimer | string | yes | – |
| recipientType | string | yes | – |
| sourceId | string | yes | – |
| template | object | yes | – |
No examples provided.
lookup_duplicate_referral_deadline Look up a senior-living 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.
| Name | Type | Req | Description |
|---|---|---|---|
| network | string | – | Filter: all, caring, or apfm |
| Name | Type | Req | Description |
|---|---|---|---|
| dataBoundary | object | yes | – |
| disclaimer | string | yes | – |
| policies | array | yes | – |
| professionalFit | object | yes | – |
| reviewedAt | string | yes | – |
No examples provided.
lookup_exit_route Look up a senior-care referral 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.
| Name | Type | Req | Description |
|---|---|---|---|
| sourceId | string | yes | Referral network: apfm, caring, seniorly, or seniorhousingnet |
| Name | Type | Req | Description |
|---|---|---|---|
| dataBoundary | object | yes | – |
| disclaimer | string | yes | – |
| guideUrl | string | yes | – |
| nextStep | string | yes | – |
| reviewedAt | string | yes | – |
| route | object | yes | – |
No examples provided.
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
claude mcp add --transport http com-geezerkeeper-referral-exit-routes 'https://geezerkeeper.com/mcp'
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 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the GeezerKeeper Referral Exit Routes and Deadlines MCP server?
VerifyMCP ran 14 checks on GeezerKeeper Referral Exit Routes and Deadlines, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.