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.

io.github.costkits/costkits-mcp

REMOTE · MCP.COSTKITS.COM · 2 COMPONENTS

Free hosted MCP server: US healthcare procedure cost estimates and provider pricing. No API key.

+3 this week 74 Trust /100

Last scanned (1 hour ago)

Scores higher than 66% of remote servers

Reachable. Last reached 24 Oct 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 Security74
Transport & Reachability100
Schema Quality & AI Usability73
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1681 tokens (~129/item across 13 items; 13 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 Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage95
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 86% 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 13 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 13 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
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.

  • 23 Oct 26 +1

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

  • 21 Oct 26 +1

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

  • 20 Oct 26 0
    • Schema quality: 1457 → 1681 ▼ functional
    • New tool “compare_bill_amount” functional
  • 18 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.

  • 17 Oct 26 0
    • Tool “estimate_procedure_cost” rewrote its description, which is the text the model reads security
    • Tool “find_providers” rewrote its description, which is the text the model reads security
    • Tool “resolve_procedure” rewrote its description, which is the text the model reads security
    • Stability: unverified → 0.03 ▲ functional
    • “find_providers” reworded the description of “limit” cosmetic
    • “estimate_procedure_cost” reworded the description of “procedure” cosmetic
    • “estimate_procedure_cost” reworded the description of “state” cosmetic
    • “estimate_procedure_cost” reworded the description of “zip_code” cosmetic
    • “find_providers” reworded the description of “state” cosmetic
    • “find_providers” reworded the description of “procedure” cosmetic
    • “find_providers” dropped the optional parameter “cluster” cosmetic
  • 16 Oct 26 71

    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 24 Oct 2026 · Probed https://mcp.costkits.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.costkits.com CN=Amazon RSA 2048 M04,O=Amazon,C=US 16 Oct 2026 1 May 2027 RSA 2048 SHA256-RSA c2f4b90554777227aa1e6662cb42087
SANs: mcp.costkits.com
CN=Amazon RSA 2048 M04,O=Amazon,C=US (CA) CN=Amazon Root CA 1,O=Amazon,C=US 23 Aug 2022 23 Aug 2030 RSA 2048 SHA256-RSA 773124f2a952e3ed18a58bdb85d1bc0ce5f27
CN=Amazon Root CA 1,O=Amazon,C=US (CA) CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US 25 May 2015 31 Dec 2037 RSA 2048 SHA256-RSA 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.costkits.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
costkits.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

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.costkits.com/mcp Verified 200
http (plaintext) http://mcp.costkits.com/mcp HTTPS enforced 301 https://mcp.costkits.com/mcp
MCP tools · 13 exposed · ~1,681 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
calculate_liability ~202

Stateless insurance math: given an allowed amount and a plan snapshot (deductible, coinsurance, OOP max), returns exact patient responsibility, plan payment, and the breakdown, plus p25/p75 scenarios. Use when you already have a dollar amount (e.g. from an EOB or a prior estimate).

NameTypeReqDescription
allowed_amountnumberyesNegotiated/allowed amount in dollars
coinsurancenumberyesCoinsurance as a fraction, e.g. 0.2 for 20%
copaynumber–Flat copay, if the plan uses one
deductiblenumberyesAnnual deductible in dollars
deductible_metnumber–Deductible already met this year
oop_maxnumberyesAnnual out-of-pocket maximum in dollars
oop_metnumber–Out-of-pocket already met this year
preventive_exceptionboolean–True if ACA preventive $0 cost-sharing applies

No output schema declared.

No examples provided.

check_financial_assistance ~173

Screen a household for hospital financial assistance (charity care): returns income as a percent of the federal poverty guidelines, the typical range hospital policies cover, what federal rules (IRS 501(r)) do and do not guarantee, and next steps. Use when a user asks whether they might qualify for help paying a hospital bill. It is a screening estimate, not an eligibility decision: each hospital sets its own limits. Needs household size and annual household income; do not ask for names, account numbers or bill details.

NameTypeReqDescription
annual_household_incomenumberyesTotal annual household income before taxes, in dollars
household_sizeintegeryesNumber of people in the household, including the patient
statestring–2-letter US state code; only Alaska and Hawaii change the poverty guideline

No output schema declared.

No examples provided.

compare_bill_amount ~224

Compares one dollar amount from a medical bill or explanation of benefits with the typical allowed-amount range (low, median, high) for the same procedure in the same US state, and says whether it is below, within or above that range, with questions worth asking the billing office. Pass amount_type 'billed' for the charge on the bill or 'allowed' for the insurer's allowed amount. Billed charges are usually higher than allowed amounts, so a high billed charge alone is not an error. Needs only the procedure, state and amount; do not send names, dates, account or member numbers.

NameTypeReqDescription
amountnumberyesThe dollar amount from the bill or EOB
amount_typestringyes'billed' = the charge on the bill; 'allowed' = the amount the insurer allowed
procedurestringyesProcedure slug or plain name, e.g. 'colonoscopy'. Resolve plain names with resolve_procedure.
statestringyes2-letter US state code, e.g. 'TX'

No output schema declared.

No examples provided.

demo_estimate ~44

Static sample cost estimate (colonoscopy in Connecticut) from the CostKits API. Works with NO API key — use it to verify connectivity and see the response shape.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

estimate_procedure_cost ~275

Returns the typical allowed-amount range (low, median, high) for one medical procedure in one US state, the usual billing components (facility, physician, anesthesia, pathology), and the data vintage. If the user chooses to give their own deductible, coinsurance and out-of-pocket figures, it also returns an estimated patient share. These are estimates of typical prices from hospital price transparency and Medicare data, not quotes. Only the procedure and state are required; ZIP code and plan figures are optional and are used only for this one calculation.

NameTypeReqDescription
coinsurance_pctnumber–Coinsurance percentage, e.g. 20 for 20%
deductible_remainingnumber–Dollars left on the member's deductible
oop_remainingnumber–Dollars left to the member's out-of-pocket max
plan_typestring–Insurance plan type (default commercial)
procedurestringyesProcedure slug or plain name, e.g. 'colonoscopy' or 'mri-knee'. A plain name that is not an exact slug can be matched with resolve_procedure.
statestringyes2-letter US state code, e.g. 'CT'. Prices are state-level.
zip_codestring–Optional 5-digit ZIP, used only to refine the local estimate

No output schema declared.

No examples provided.

find_providers ~148

Lists up to 5 facilities in one US state that perform a procedure, with name, address and a pricing_status field: 'observed' means a negotiated rate is published in that facility's price transparency data, 'estimated' means only a state-level benchmark applies, 'none' means no price data. Dollar amounts are not returned. The list is partial and is not a ranking or a recommendation.

NameTypeReqDescription
limitinteger–Max results, 1 to 5 (default 5)
procedurestringyesProcedure slug or plain name, e.g. 'colonoscopy'
statestringyes2-letter US state code, e.g. 'CT'

No output schema declared.

No examples provided.

full_estimate ~151

One call chaining procedure ontology + cost + providers + patient liability. Cheapest way (one metered request) to get the complete picture. Use `fields` to request a subset; liability requires the plan_* inputs.

NameTypeReqDescription
fieldsarray–Which services to include (default: all)
plan_coinsurancenumber–Fraction, e.g. 0.2
plan_deductiblenumber––
plan_deductible_metnumber––
plan_oop_maxnumber––
plan_oop_metnumber––
procedurestringyesProcedure slug or plain name
statestringyes2-letter US state code

No output schema declared.

No examples provided.

get_coverage ~156

Insurance coverage rules for a procedure/carrier combination. aspect: 'summary' (status + plain English), 'prior-auth', 'cost-sharing' (deductible/coinsurance/ACA preventive), 'frequency' (how often covered, age rules), or 'triggers' (Pro plan: billing events that flip a $0 preventive claim to diagnostic — the highest-signal aspect).

NameTypeReqDescription
aspectstring–Default 'summary'
carrierstringyesCarrier key, e.g. 'aetna', 'cigna', 'bcbs', 'medicare' — see list_carriers
plan_typestring––
procedurestringyesProcedure slug, e.g. 'colonoscopy'

No output schema declared.

No examples provided.

get_procedure_details ~90

Structured knowledge about one procedure. aspect='facts' returns LLM-ready billing rules and cost drivers (best for grounding an answer); 'bundle' explains which separate bills to expect (facility, physician, anesthesia...); 'full' returns the complete ontology.

NameTypeReqDescription
aspectstring–Default 'facts'
slugstringyesCanonical procedure slug, e.g. 'colonoscopy'

No output schema declared.

No examples provided.

get_provider ~45

Public profile for a single provider by 10-digit NPI number: name, specialty, address, entity type.

NameTypeReqDescription
npistringyes10-digit NPI number

No output schema declared.

No examples provided.

list_carriers ~47

All insurance carrier keys supported by the coverage tools (aetna, cigna, bcbs, medicare, ...). Works on the Free plan — also a good API-key sanity check.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_procedures ~56

The full CostKits catalog: 30 procedures with slugs, display names, categories, and CPT codes (paginated).

NameTypeReqDescription
cursorstring–next_cursor from a previous response
limitinteger––

No output schema declared.

No examples provided.

resolve_procedure ~70

Maps a free-text procedure name ('knee mri', 'gallbladder removal') to a CostKits catalog slug with a confidence score. Returns best_match and alternatives; best_match is null when the procedure is not in the catalog.

NameTypeReqDescription
querystringyesFree-text procedure name

No output schema declared.

No examples provided.

Install

How do I install the io.github.costkits/costkits-mcp server?

io.github.costkits/costkits-mcp is a hosted endpoint at https://mcp.costkits.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.costkits.com

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

What is the io.github.costkits/costkits-mcp server?

io.github.costkits/costkits-mcp is listed in the public MCP registry as io.github.costkits/costkits-mcp. Free hosted MCP server: US healthcare procedure cost estimates and provider pricing. No API key. This page covers its hosted endpoint (https://mcp.costkits.com/mcp).

Is the io.github.costkits/costkits-mcp server safe to use?

io.github.costkits/costkits-mcp scores 74 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 io.github.costkits/costkits-mcp server expose?

io.github.costkits/costkits-mcp exposes 13 tools: demo_estimate, estimate_procedure_cost, calculate_liability, full_estimate, find_providers, and 8 more. Their descriptions and schemas cost roughly 1,681 tokens of context every time the server is loaded.

Does the io.github.costkits/costkits-mcp server require authentication?

No. We connected to io.github.costkits/costkits-mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the io.github.costkits/costkits-mcp server still maintained?

io.github.costkits/costkits-mcp is still listed as active in the MCP registry. We last reached this channel on 24 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.