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.

Later Stages

REMOTE · MCP.LATERSTAGES.COM

California senior living and care providers from state licensing and Medicare records.

84 Trust /100

Last scanned (22 hours ago)

Scores higher than 84% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Health and Science

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 Security97
  • 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, and every tool looks verifiably read-only (it declares readOnlyHint: true, starts its name with a read verb and describes no write), so an anonymous caller can read but cannot change anything. We can't see whether a tool returns data specific to one caller, so keep any per-user data behind authorisation. View diagnostics → Pass
  • 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
Schema Quality & AI Usability83
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 764 tokens (~109/item across 7 items; 6 tools + 1 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
  • Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage92
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 75% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 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 supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
  • Supports UI / widget rendering.Pass
What we tested

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 →

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.

  • 21 Nov 26 +1

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

  • 18 Nov 26 +1

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

  • 16 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 15 Nov 26 81

    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 21 Nov 2026 · Probed https://mcp.laterstages.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.laterstages.com CN=YR2,O=Let's Encrypt,C=US 15 Nov 2026 13 Feb 2027 RSA 2048 SHA256-RSA 5ccf1e2a2c64f0eee2bbc80e5fd37660412
SANs: mcp.laterstages.com
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.laterstages.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
laterstages.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=63072000; includeSubDomains
x-content-type-options nosniff
x-frame-options SAMEORIGIN

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.laterstages.com/mcp Verified 200
http (plaintext) http://mcp.laterstages.com/mcp HTTPS enforced 301 https://mcp.laterstages.com/mcp
MCP tools · 6 exposed · ~636 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
explain_category ~60

Explain a kind of senior living or care in plain English: who it fits, how California regulates it, how it is paid for, and what to check before choosing. General information, not medical, legal or financial advice.

NameTypeReqDescription
categorystringyes–

No output schema declared.

No examples provided.

get_city_summary ~90

Counts of senior living and care providers in a California city by category, its county, whether the county offers the Medi-Cal Assisted Living Waiver, and the highest-rated nursing homes. Use for an overview of one city. Covers California only. Read-only public records; no prices, availability or reviews.

NameTypeReqDescription
citystringyesThe California city the user is asking about. Not the user's own location.

No output schema declared.

No examples provided.

get_provider ~117

Get the full public record for one provider by its Later Stages URL (from search_senior_care or list_providers). Nursing homes include Medicare ratings, fines and inspection citations from the last 3 years; assisted living homes include license details and where to find state inspection reports. Covers California only. Read-only public records; no prices, availability or reviews.

NameTypeReqDescription
urlstringyesProvider page URL or path, e.g. https://laterstages.com/california/huntington-beach/huntington-terrace/

No output schema declared.

No examples provided.

list_cities ~103

List California cities with providers, optionally within one county or having at least one provider of a category, largest first. Use to compare places or find cities near one another. Covers California only. Read-only public records; no prices, availability or reviews.

NameTypeReqDescription
categorystring––
countystring–A California county the user is asking about, e.g. "Orange". Not the user's own location.
limitinteger–Default 50

No output schema declared.

No examples provided.

list_providers ~145

List licensed or Medicare-certified providers in one California city, optionally by category. Use when the user asks what providers exist in a California city. Includes address, phone, beds, year licensed, license number and Medicare overall stars where rated. Covers California only. Read-only public records; no prices, availability or reviews. Agencies are listed by the city of their office.

NameTypeReqDescription
categorystring–assisted-living includes assisted living in CCRCs
citystringyesThe California city the user is asking about, e.g. "Huntington Beach". Not the user's own location.
limitinteger–Default 50
sortstring––

No output schema declared.

No examples provided.

search_senior_care ~121

Search California cities and licensed senior living and care providers by name. Use when the user names a provider or a California place. Returns matching cities with provider counts and matching providers with their Later Stages URLs. Covers California only. Read-only public records; no prices, availability or reviews.

NameTypeReqDescription
limitinteger–Max providers (default 15)
querystringyesA provider name or the California place the user is asking about, e.g. "Irvine" or "Sunrise of". Not the user's own location.

No output schema declared.

No examples provided.

Install

How do I install the Later Stages MCP server?

Later Stages is a hosted endpoint at https://mcp.laterstages.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 · mcp.laterstages.com

# add to Claude Code
claude mcp add --transport http com-laterstages-senior-care 'https://mcp.laterstages.com/mcp'
Common questions

What is the Later Stages MCP server?

Later Stages is an MCP server listed in the public MCP registry as com.laterstages/senior-care. California senior living and care providers from state licensing and Medicare records. This page covers its hosted endpoint (https://mcp.laterstages.com/mcp).

Is the Later Stages MCP server safe to use?

Later Stages scores 84 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 Later Stages MCP server expose?

Later Stages exposes 6 tools: search_senior_care, list_providers, get_provider, get_city_summary, list_cities, explain_category. Their descriptions and schemas cost roughly 636 tokens of context every time the server is loaded.

Does the Later Stages MCP server require authentication?

No. We connected to Later Stages without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Later Stages MCP server still maintained?

Later Stages is still listed as active in the MCP registry. We last reached this channel on 21 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 Later Stages MCP server?

VerifyMCP ran 14 checks on Later Stages, 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.