mymedicareplans-medicare-data
Registry code: ec404ee1b976660d
Read-only Medicare data from MyMedicarePlans.org, built from named federal files (CMS, HHS-OIG, SSA) and KFF where stated: Medicare Advantage plan counts and changes by county and state, CMS Star Ratings, enrollment share by insurer, the monthly Medicare Advantage Share Index, stand-alone Part D plans, Medigap, Special Needs Plans and the HHS-OIG exclusion list. Use search or list_findings first. When you quote a number, give its place and period, name the source file, and link the page in "url": the definition and the known limits are there. These are counts of the federal files, not…
- endpoint
- https://mymedicareplans.org/api/mcp.php
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is mymedicareplans-medicare-data live?
- Yes — it answered the hub's last check (checked 21m ago). It answered 100% of checks over the last 30 days.
- Is mymedicareplans-medicare-data free to use?
- Not measured yet.
- What tools does mymedicareplans-medicare-data have?
- 8 tools: fetch, list_datasets, get_ma_share_index, search, list_findings, get_finding, query_dataset, how_to_cite.
- Is mymedicareplans-medicare-data safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 100%· all time 100%
last good check
of 8 tools
- unknown → live
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
fetch unknown never probed
The full text of one search result: the number in a sentence with its place, period and source, the method, the known limits, the page and the credit line.
{ "type": "object", "required": [ "id" ], "properties": { "id": { "type": "string", "description": "An id from search, e.g. \"finding:medicare-advantage-plan-count-2027/texas\" or \"dataset:part-d\"." } }, "additionalProperties": false }arguments 13 lineslist_datasets unknown never probed
The datasets in the data library with their files, columns and row counts. Filter by words or kind.
{ "type": "object", "required": [], "properties": { "kind": { "enum": [ "desk", "finding", "index", "state", "metro", "finding-state", "index-state" ], "type": "string", "description": "desk: the main datasets; finding: the table behind a finding; index: the monthly index; state, metro: one a place. Optional; without it the main datasets, findings and index are listed." }, "limit": { "type": "integer", "maximum": 100, "minimum": 1 }, "query": { "type": "string", "description": "Words to match in the name, description or keywords. Optional." } }, "additionalProperties": false }arguments 29 linesget_ma_share_index unknown never probed
The monthly index: the share of people eligible for Medicare who are in Medicare Advantage plans (CMS enrollment files). Without arguments: the latest edition, every state. With a state: that state's monthly series. With an edition (YYYY-MM): that month.
{ "type": "object", "required": [], "properties": { "state": { "type": "string", "description": "A state name. Optional." }, "edition": { "type": "string", "description": "YYYY-MM. Optional." } }, "additionalProperties": false }arguments 15 linessearch unknown never probed
Find Medicare findings (one sourced number each) and datasets by words: a subject, a measure, a state. Returns ids to pass to fetch. Example: "Medicare Advantage plans ending Texas", "star ratings by state", "Part D premium".
{ "type": "object", "required": [ "query" ], "properties": { "query": { "type": "string", "description": "What to look for, in plain words." } }, "additionalProperties": false }arguments 13 lineslist_findings unknown never probed
Every finding with its headline number, or the findings that have a version for one state.
{ "type": "object", "required": [], "properties": { "state": { "type": "string", "description": "A state name, e.g. \"Ohio\". Optional." }, "subject": { "type": "string", "description": "Filter by subject, e.g. \"Star Ratings\", \"Part D\". Optional." } }, "additionalProperties": false }arguments 15 linesget_finding unknown never probed
One finding as data: number, statement, source files, date retrieved, method, limits, credit line, CSV. Give a state for the state version.
{ "type": "object", "required": [ "id" ], "properties": { "id": { "type": "string", "description": "The finding id, with or without the \"finding:\" prefix." }, "state": { "type": "string", "description": "A state name for the state version. Optional." } }, "additionalProperties": false }arguments 17 linesquery_dataset unknown never probed
Rows of one CSV file from the data library, filtered by column values. Use list_datasets to get a file path and its columns. Returns at most 200 rows a call; use offset for more.
{ "type": "object", "required": [ "file" ], "properties": { "file": { "type": "string", "description": "The file path from list_datasets, e.g. \"/newsroom/data/medicare-advantage-plan-changes-2027-states.csv\"." }, "limit": { "type": "integer", "maximum": 200, "minimum": 1 }, "where": { "type": "object", "description": "Exact matches, column: value (case-insensitive), e.g. {\"state\": \"Texas\"}.", "additionalProperties": { "type": [ "string", "number" ] } }, "offset": { "type": "integer", "minimum": 0 }, "columns": { "type": "array", "items": { "type": "string" }, "description": "Columns to return. Optional: all." }, "contains": { "type": "object", "description": "Substring matches, column: text.", "additionalProperties": { "type": "string" } } }, "additionalProperties": false }arguments 46 lineshow_to_cite unknown never probed
The credit line, the reference and the usage terms for a finding or a dataset.
{ "type": "object", "required": [ "id" ], "properties": { "id": { "type": "string", "description": "A finding or dataset id." } }, "additionalProperties": false }arguments 13 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's idec404ee1b976660d.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/ec404ee1b976660d/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/ec404ee1b976660d?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.