Eldercare Resource Planning MCP Server
REMOTE · MCP.ELDERCARERESOURCEPLANNING.ORG · SCANNED OCT 1
Evaluates Medicaid long-term care eligibility and spend-down rules for all 50 US states.
Available components
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability54
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 676 tokens (~676/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Eldercare Resource Planning MCP Server server?
Eldercare Resource Planning MCP Server is a hosted endpoint at https://mcp.eldercareresourceplanning.org/sse, 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 · mcp.eldercareresourceplanning.org
claude mcp add --transport http the-codepunker-eldercare-resource-planning 'https://mcp.eldercareresourceplanning.org/sse'
{
"mcpServers": {
"the-codepunker-eldercare-resource-planning": {
"url": "https://mcp.eldercareresourceplanning.org/sse"
}
}
} {
"servers": {
"the-codepunker-eldercare-resource-planning": {
"type": "http",
"url": "https://mcp.eldercareresourceplanning.org/sse"
}
}
} [mcp_servers.the-codepunker-eldercare-resource-planning] url = "https://mcp.eldercareresourceplanning.org/sse"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"the-codepunker-eldercare-resource-planning": {
"type": "remote",
"url": "https://mcp.eldercareresourceplanning.org/sse",
"enabled": true
}
}
} openclaw mcp add the-codepunker-eldercare-resource-planning --url 'https://mcp.eldercareresourceplanning.org/sse' --transport streamable-http
mcp_servers:
the-codepunker-eldercare-resource-planning:
url: "https://mcp.eldercareresourceplanning.org/sse" {
"McpServers": {
"the-codepunker-eldercare-resource-planning": {
"Transport": "http",
"Url": "https://mcp.eldercareresourceplanning.org/sse"
}
}
} assistant mcp add the-codepunker-eldercare-resource-planning -t streamable-http -u 'https://mcp.eldercareresourceplanning.org/sse'
{
"mcpServers": {
"the-codepunker-eldercare-resource-planning": {
"type": "http",
"url": "https://mcp.eldercareresourceplanning.org/sse"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 1 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 29 Sept 26 55
First indexed and scored.
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 1 Oct 2026 · Probed https://mcp.eldercareresourceplanning.org/sse
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=eldercareresourceplanning.org | CN=WE1,O=Google Trust Services,C=US | 21 Aug 2026 | 19 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | d849c42f2693a96f0eb94e8ecbbaac2a |
| SANs: eldercareresourceplanning.org, *.eldercareresourceplanning.org | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.eldercareresourceplanning.org. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| org. | present | 26974 | 8 | Verified |
| eldercareresourceplanning.org. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| sse | https://mcp.eldercareresourceplanning.org/sse | Verified | 200 | |
| http (plaintext) | http://mcp.eldercareresourceplanning.org/sse | HTTPS enforced | 301 | https://mcp.eldercareresourceplanning.org/sse |
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 →
check_medicaid_eligibility ~676
Evaluate an applicant's Medicaid long-term care eligibility and create a lead in Insightly CRM. All 10 required fields (first_name, last_name, email, phone, state, marital_status, age, income, assets, home_equity) must be collected before calling this tool.
| Name | Type | Req | Description |
|---|---|---|---|
| age | number|string | yes | Exact numeric age (e.g. 74) or bracket string ('65 - 85', 'Over 85', 'Under 65 and not disabled', 'Under 65 and disabled & receiving SSDI'). |
| assets | number|string | yes | Total countable liquid/financial assets excluding primary home in USD (e.g. 15000) or bracket string ('Less than $2,000', 'Between $2,000 - $5,000', 'Between $5,000 - $10,000', 'Between $10,000 - $20… |
| care_reason | string | – | Reason for seeking Medicaid long-term care coverage. |
| county | string | – | Optional county name or ID (defaults to statewide calculation). |
| string | yes | Valid RFC-compliant email address for the applicant or primary contact. | |
| first_name | string | yes | Applicant or contact first name (1–100 characters). |
| for_whom | string | – | Who the assessment is being completed for. |
| home_equity | number|string | yes | Primary home equity in USD (e.g. 250000), equity bracket string, or 'No' / 'None' / 0 if they do not own a home. |
| income | number|string | yes | Gross monthly income in USD (e.g. 1850) or bracket string ('Less than $1,500 / month', 'Between $1,500 - $2,000 / month', 'Between $2,000 - $3,000 / month', 'Between $3,000 - $6,000 / month', 'Over $… |
| is_disabled | boolean | – | Pass true if applicant is under 65 and receiving SSDI / legally disabled. |
| last_name | string | yes | Applicant or contact last name (1–100 characters). |
| marital_status | string | yes | Applicant's marital status: 'single', 'married', 'divorced', 'widowed', or 'separated'. |
| out_of_pocket_costs | string | – | Estimated monthly out-of-pocket medical care costs (e.g. '$3,000 / month'). |
| phone | string | yes | 10-digit US phone number (e.g. '5551234567'). Formatted strings like '(555) 123-4567' are sanitized. |
| residence | string | – | Current living arrangement (e.g. 'At home', 'Assisted living', 'Nursing home'). |
| state | string | yes | 2-letter US state postal code (e.g. 'FL', 'CA', 'NY') or full state name. |
| veteran | string | – | Veteran status of applicant or spouse. |
No output schema declared.
No examples provided.
What is the Eldercare Resource Planning MCP Server server?
Eldercare Resource Planning MCP Server is listed in the public MCP registry as io.github.the-codepunker/eldercare-resource-planning. Evaluates Medicaid long-term care eligibility and spend-down rules for all 50 US states. This page covers its hosted endpoint (https://mcp.eldercareresourceplanning.org/sse).
Is the Eldercare Resource Planning MCP Server server safe to use?
Eldercare Resource Planning MCP Server scores 56 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 Eldercare Resource Planning MCP Server server expose?
Eldercare Resource Planning MCP Server exposes 1 tool: check_medicaid_eligibility. Their descriptions and schemas cost roughly 676 tokens of context every time the server is loaded.
Does the Eldercare Resource Planning MCP Server server require authentication?
No. We connected to Eldercare Resource Planning MCP Server without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Eldercare Resource Planning MCP Server server still maintained?
Eldercare Resource Planning MCP Server is still listed as active in the MCP registry. We last reached this channel on 1 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.