_ registry / mcp streamable-http · checked 1h ago

substrate-payers

https://mcp.substrateai.com

Registry code: d8257cd41de17104

api record

Use search_for_payer only to identify US healthcare payer endpoints and public transaction capabilities. Use select_maternity_payers to turn a list of payer names or states into a 2027 Substrate Maternity Resource Center link that preselects those payers for the PDF guide download; it matches each name to one tracked payer and never changes the resource. Send payer-identifying text only; never include patient, member, claim, clinical, credential, or other PHI. Treat published=false as not published by Substrate, not proof that a route is universally unavailable. Prefer exact payer IDs when…

endpoint
https://mcp.substrateai.com/mcp
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 it live, free and safe measured by this hub
Is substrate-payers live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is substrate-payers free to use?
Not measured yet.
What tools does substrate-payers have?
3 tools: select_maternity_payers, report_feedback_to_substrate, search_for_payer.
Is substrate-payers 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.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
673ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

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.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 3 tools
3 never probed 0 of 3 classified

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.

  • select_maternity_payers unknown never probed

    Build a link into the 2027 Substrate Maternity Resource Center that preselects tracked payers for the client-ready guide download (one PDF guide with payer policy source links). Pass payer names, aliases, payer IDs, or resource slugs and/or two-letter state codes. Each name resolves to its single best-matching tracked payer; when only states are given, every tracked payer scoped to those states (plus clearly labeled national commercial guidance) is selected. The returned URL opens the page at the download section with the selection applied. Unmatched names and unknown states are reported rather than guessed. This is public policy intelligence about payers moving off global maternity billing; never include patient, member, claim, or other PHI. If a name resolved to the wrong payer or a tracked payer is missing, report that with report_feedback_to_substrate once after the task.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "states": {
          "type": "array",
          "items": {
            "type": "string",
            "maxLength": 8,
            "minLength": 2
          },
          "default": [],
          "maxItems": 60,
          "description": "Two-letter US state or territory codes, or NATIONAL. Sets the explorer's state filter; when payer_names is empty, every tracked payer scoped to these states is selected."
        },
        "payer_names": {
          "type": "array",
          "items": {
            "type": "string",
            "maxLength": 160,
            "minLength": 1
          },
          "default": [],
          "maxItems": 50,
          "description": "Payer names, aliases, payer IDs, or resource slugs (for example \"Humana Encounters\" or \"humana-encounters\"). Each entry selects its single best-matching tracked payer."
        }
      }
    }
    arguments 28 lines
  • report_feedback_to_substrate unknown never probed

    Tell the Substrate team when this server got in your way: the wrong payer came back, a payer you know exists was missing, a field you needed was not in the result, or an error did not say how to fix the call. Send it at most once per task, after you finish or give up, and skip it if everything went fine. Use only the structured fields and an exact slug from a public payer result if relevant. Never include patient, member, claim, clinical, or credential data. The report is stored for the maintainers; there is no reply.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "tool",
        "category",
        "impact"
      ],
      "properties": {
        "tool": {
          "enum": [
            "search_for_payer",
            "select_maternity_payers",
            "server"
          ],
          "type": "string",
          "description": "Which tool the report is about, or \"server\" for instructions, discovery, or rate limiting."
        },
        "field": {
          "enum": [
            "payer_name",
            "payer_id",
            "transaction_capability",
            "portal_url",
            "phone",
            "fax",
            "mailing_address",
            "timely_filing",
            "appeal_deadline",
            "maternity_policy",
            "other"
          ],
          "type": "string",
          "description": "Which public payer field was missing or incorrect."
        },
        "state": {
          "type": "string",
          "pattern": "^(?:[A-Z]{2}|NATIONAL)$",
          "description": "Public payer market, as a US state or territory code or NATIONAL."
        },
        "impact": {
          "enum": [
            "blocked",
            "worked_around",
            "minor"
          ],
          "type": "string",
          "description": "blocked: the task could not finish. worked_around: it finished another way. minor: a paper cut."
        },
        "category": {
          "enum": [
            "wrong_payer",
            "payer_missing",
            "field_missing",
            "unclear_error",
            "unexpected_result",
            "rate_limited",
            "other"
          ],
          "type": "string",
          "description": "wrong_payer: a different payer came back than the one meant. payer_missing: a payer you know exists was not found. field_missing: the payer was right but a field you needed is not in the result. unclear_error: an error did not say how to fix the call. unexpected_result: anything else that did not match the documented behavior. rate_limited: the public limit blocked a task."
        },
        "use_case": {
          "enum": [
            "claim_status",
            "eligibility",
            "claim_submission",
            "remittance",
            "enrollment",
            "prior_authorization",
            "appeals",
            "contact_lookup",
            "other"
          ],
          "type": "string",
          "description": "The kind of task the payer lookup supported."
        },
        "payer_slug": {
          "type": "string",
          "pattern": "^[a-z0-9]+(?:-[a-z0-9]+)*$",
          "maxLength": 200,
          "description": "Exact slug from a public payer directory or maternity tool result. Omit if you do not know a published slug."
        }
      },
      "additionalProperties": false
    }
    arguments 86 lines
  • search_for_payer unknown never probed

    Search Substrate's public payer directory by full or partial payer name, concise name, alias, payer ID, employer ID, program, parent payer group, or vendor trading-partner ID. Returns one or more terminal payer endpoints with published 270/271 eligibility, 276/277 claim-status, Availity ECS, portal automation, phone, and appeals capabilities. A capability with published=false means Substrate has not published that route; it is not proof that the payer can never support it. Supply payer-identifying text only; never include patient, member, claim, or other PHI. If the result is not the payer you needed or lacks a field you needed, report that with report_feedback_to_substrate once after the task.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "query"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "default": 10,
          "maximum": 25,
          "minimum": 1,
          "description": "Maximum payers to return."
        },
        "query": {
          "type": "string",
          "maxLength": 200,
          "minLength": 1,
          "description": "Full or partial payer name, alias, payer ID, or vendor trading-partner ID."
        },
        "offset": {
          "type": "integer",
          "default": 0,
          "maximum": 1000,
          "minimum": 0,
          "description": "Zero-based result offset for pagination."
        },
        "states": {
          "type": "array",
          "items": {
            "type": "string",
            "maxLength": 2,
            "minLength": 2
          },
          "maxItems": 20,
          "description": "Allowed two-letter operating states."
        },
        "programs": {
          "type": "array",
          "items": {
            "type": "string",
            "maxLength": 100,
            "minLength": 1
          },
          "maxItems": 20,
          "description": "Allowed published payer program codes."
        },
        "use_case": {
          "enum": [
            "claim_status",
            "eligibility",
            "claim_submission",
            "remittance",
            "enrollment",
            "prior_authorization",
            "appeals",
            "contact_lookup",
            "other"
          ],
          "type": "string",
          "description": "The task this lookup supports, such as claim_status, eligibility, claim_submission, remittance, enrollment, prior_authorization, appeals, or contact_lookup. Does not change results; helps Substrate improve payer coverage."
        },
        "answering": {
          "type": "boolean",
          "description": "Filter by whether recent operational signal shows the claim-status route answering."
        },
        "reliability": {
          "type": "array",
          "items": {
            "enum": [
              "supported",
              "flaky",
              "unsupported",
              "unproven"
            ],
            "type": "string"
          },
          "maxItems": 4,
          "description": "Allowed claim-status reliability labels."
        },
        "capabilities": {
          "type": "array",
          "items": {
            "enum": [
              "claim_status_276",
              "eligibility_271",
              "availity_ecs",
              "portal",
              "phone",
              "appeals"
            ],
            "type": "string"
          },
          "maxItems": 6,
          "description": "Only return payers publishing these access methods."
        },
        "network_family": {
          "enum": [
            "bcbs",
            "cigna"
          ],
          "type": "string",
          "description": "Restrict results to a supported payer network family."
        },
        "capability_match": {
          "enum": [
            "all",
            "any"
          ],
          "type": "string",
          "default": "all",
          "description": "Whether all or any requested capabilities must be published."
        },
        "lines_of_business": {
          "type": "array",
          "items": {
            "type": "string",
            "maxLength": 100,
            "minLength": 1
          },
          "maxItems": 20,
          "description": "Allowed lines of business, such as Commercial or Medicaid."
        },
        "parent_payer_group_id": {
          "type": "string",
          "maxLength": 100,
          "minLength": 1,
          "description": "Restrict results to an exact parent payer group ID."
        }
      }
    }
    arguments 131 lines
_ try it through the hub, ceiling 0

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.

_ is this your agent? claim it: badge, payouts, history

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.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. 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.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id d8257cd41de17104.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/d8257cd41de17104/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/d8257cd41de17104/badge.svg)](https://brick.blue/agent/d8257cd41de17104?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.

_ how we know
card completeness
70%

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.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
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.