Is com.medigami/mcp up? Live MCP status
Not checked just now. The live check did not run for this request (more than 120 status pages asked for a fresh check in the last minute). Reload in a minute; the monthly census result is below.
| Endpoint | https://mcp.medigami.com/public/mcp |
|---|---|
| Page built |
One MCP handshake with the listed endpoint (server/discover at 2026-07-28, then initialize for a server on the older revision), with no credential and no retry, identifying itself as agentwares-mcp-liveness/0.1 (+https://agentwares-agentcheck.vercel.app/bot). It runs when this page is requested and the result is reused for 10 minutes, so the time above is when it was taken.
Live status every few hours: Wellknown
Email me when this server changes
That was one look. To hear when it stops answering or its tools change, leave an address.
Free, no password or GitHub: one confirmation email first, then a check every hour and an email when it stops answering or its tools change. Every email has a link to stop. More about it.
Monthly census, 6 October 2026
The census sends the same request to every remote listing in the official registry once a month. On 6 October 2026 this one answered a stock client with no credential. Every listing’s result: index.ndjson (what the files hold: index.meta.json).
Agent discovery documents at this origin
| A2A agent card | Not published (HTTP 200 with an HTML page, not JSON)./.well-known/agent-card.json |
|---|---|
| MCP server card (SEP-2127) | Not published (HTTP 406).https://mcp.medigami.com/chatgpt/mcp/server-card (the one endpoint per origin the census asks, not this listing’s) |
| MCP server card (SEP-1649 location) | Published, does not validate: `$schema` is required (and 4 more). SEP-1649 shape; Medigami 0.1.8./.well-known/mcp/server-card.json — SEP-1649, a draft superseded by SEP-2127 on 21 January 2026 |
| Web Bot Auth key directory | Not published (HTTP 301 to https://medigami.com/mcp; a verifier must not follow a redirect (draft-00 ยง5.5))./.well-known/http-message-signatures-directory |
Read at https://mcp.medigami.com with the monthly census on 9 October 2026: one GET each, no credential, never a signed request. A2A against v1.0.1, the server card against the MCP Server Card schema (SEP-2127), the card at SEP-1649’s location against the shape it has, the key directory against the Web Bot Auth draft of 1 September 2026. Who publishes them.
Tool changes between snapshots
In the 2026-10 snapshot it listed 87 tools: analyze_glp1_pathways, appeal_argument_generator, appeal_escalation_path_finder, appeal_success_predictor, batch_scan_bills, bill_shock_predictor, billing_charge_vs_allowed_delta, bundling_violation_detector, cash_price_estimator, cash_vs_insurance_optimizer, claim_consistency_checker, claim_duplicate_line_detector, claim_rebuttal_generator, claim_reconsideration_builder, code_bundle_validator, code_conflict_detector, coinsurance_simulator, copay_model, cpt_to_icd_mapper, decode_denial, deductible_impact_calculator, denial_code_explainer, denial_reason_classifier, denial_response_builder, dispute_case_builder, estimate_appeal_success, evidence_pack_generator, explain_appeal_success, fair_price_estimator, financial_assistance_finder, financial_exposure_model, financial_risk_exposure_model, format_citation, format_medigami_citation, generate_appeal_letter, generate_appeal_letter_v2, get_appeal_deadline, get_venue, healthcare_budget_forecaster, icd_to_cpt_mapper, inflation_adjusted_price_model, insurance_plan_optimizer, insurance_response_interpreter, insurance_value_optimizer, lookup_cpt, lookup_icd10, lookup_npi, lookup_provider_taxonomy, market_price_distribution_model, maximize_recovery, medical_spending_analyzer, medigami_deadline, medigami_odds, medigami_rate, medigami_roast, negotiate_bill_script, negotiation_strategy_generator, optimize_prescription, out_of_pocket_optimizer, overpriced_service_detector, patient_cost_explainer, patient_cost_forecaster, patient_financial_risk_score, payer_specific_appeal_templates, payment_plan_optimizer, price_anomaly_detector, price_outlier_detector, price_recommendation_engine, price_variance_analyzer, procedure_affordability_ranker, procedure_cost_decomposition, regional_price_benchmark, resolve_codes, resolve_denial, scan_bill_for_errors, settlement_optimizer, specialty_price_benchmark, submit_denial_letter, supporting_document_selector, treatment_cost_comparator, unbundling_detector, verify_attestation, verify_dea_authorization, verify_mcp_response, watch_appeal_outcome, watch_claim_denial, zip_based_price_variance.
Its tools changed between 2026-09 and 2026-10:
resolve_denial: input schema changed
Which tools were added or removed, and whose description or schemas changed, from content hashes in the monthly snapshots. Per tool, as JSON: /v1/drift.
The listing
| Registry name | com.medigami/mcp |
|---|---|
| Endpoint | https://mcp.medigami.com/public/mcp |
| Publisher repository | not known: the registry did not return this listing within 4 seconds |
Also
The full check by name, as JSON (on a 401 it also follows the OAuth discovery chain) · Watch it · Check another server · llms.txt