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

statutewire

https://statutewire.com

Registry code: e1113d28d3ded9e2

api record

US healthcare exclusion screening (OIG, SAM, state Medicaid) and state license checks. No PHI.

from a public catalogue that lists it, not from the operator

endpoint
https://statutewire.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 statutewire live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is statutewire free to use?
Partly — some of its tools are open, others need a key or payment.
What tools does statutewire have?
8 tools: screen_practitioner, screen_roster, get_coverage, get_pricing, how_to_get_access, get_receipt, verify_receipt, get_practitioner_history.
Is statutewire 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
754ms

last good check

priced tools
0

of 8 tools

_ answered our checks, 90 days 2 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 8 tools
1 open3 auth-required 4 never probed 4 of 8 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.

  • how_to_get_access open 1h ago

    How to get a sandbox key (sample data) and a live key, the real URLs, and what each key returns. No key needed, free, returns no provider data.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • get_receipt auth-required 1h ago

    Fetches a signed receipt as JSON: either a practitioner receipt by file name (the .json file name from a screening result, for a practitioner on your roster) or a monthly roster receipt (roster_id + period YYYY-MM, built from your latest complete run). Free (rate limited, not metered). A sandbox or non-production receipt is labelled as such or UNSIGNED and proves nothing. Check it with verify_receipt. Needs an API key (Authorization: Bearer sw_live_… or sw_test_…); without one it returns an error that points to how_to_get_access.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "file": {
          "type": "string",
          "description": "Practitioner receipt file name ending in .json."
        },
        "period": {
          "type": "string",
          "pattern": "^[0-9]{4}-(0[1-9]|1[0-2])$",
          "description": "Month, YYYY-MM."
        },
        "roster_id": {
          "type": "string",
          "description": "Roster id (from your account). Use with period."
        }
      },
      "additionalProperties": false
    }
    arguments 19 lines
  • verify_receipt auth-required 1h ago

    Checks a StatuteWire receipt JSON (the whole file text or object): hash, canonical form, Ed25519 signature against StatuteWire's published key, and roster totals. Free, not metered. VALID means the file is exactly as StatuteWire signed it; it says nothing about whether the practitioner is clean. A receipt signed with the SAMPLE key is reported as SAMPLE, never as valid. Needs an API key (Authorization: Bearer sw_live_… or sw_test_…); without one it returns an error that points to how_to_get_access.

    mcp-tool

    {
      "type": "object",
      "required": [
        "receipt"
      ],
      "properties": {
        "receipt": {
          "description": "The receipt JSON file contents, as a string or an object."
        }
      },
      "additionalProperties": false
    }
    arguments 12 lines
  • get_practitioner_history auth-required 27h ago

    The append-only audit ledger of monitoring events for a practitioner on this account's roster (a practitioner screened or rostered by this key). Free (rate limited). Not covered: practitioners not on your roster (404). Entries made from sample data are not upgraded to live by this tool. Needs an API key (Authorization: Bearer sw_live_… or sw_test_…); without one it returns an error that points to how_to_get_access.

    mcp-tool

    {
      "type": "object",
      "required": [
        "npi"
      ],
      "properties": {
        "npi": {
          "type": "string",
          "pattern": "^\\d{10}$",
          "description": "The 10-digit National Provider Identifier (NPI)."
        }
      },
      "additionalProperties": false
    }
    arguments 14 lines
  • screen_practitioner unknown never probed

    Screens one practitioner: state license status and board discipline flags (only for states that are live; sandbox keys get SAMPLE data for every state), identity check against CMS NPPES, and exclusion screening (OIG LEIE, SAM.gov and the state Medicaid lists that are live), with an evidence receipt. Requires NPI + first name + last name + state; if the names you give do not match the record, the result is blocked, not warned. The output lists which sources returned CLEAR and which did not; a source that is not CLEAR (including NOT_CHECKED and COULD_NOT_CHECK) must never be reported as clear. Counts as one lookup against the key's quota or prepaid balance (1 check), exactly as GET /api/v1/sanctions does. Not covered: states that are not live, licenses of staff without an NPI (use screen_roster), anything not on the official lists. A possible match is for a person to confirm with the official source. Needs an API key (Authorization: Bearer sw_live_… or sw_test_…); without one it returns an error that points to how_to_get_access.

    mcp-tool

    {
      "type": "object",
      "required": [
        "npi",
        "first_name",
        "last_name",
        "state"
      ],
      "properties": {
        "npi": {
          "type": "string",
          "pattern": "^\\d{10}$",
          "description": "The 10-digit National Provider Identifier (NPI)."
        },
        "fresh": {
          "type": "boolean",
          "description": "true skips the 120-day cache and queries the source again."
        },
        "state": {
          "type": "string",
          "maxLength": 4,
          "minLength": 2,
          "description": "Two-letter state code, or eNLC for the nursing compact (sample data only)."
        },
        "last_name": {
          "type": "string",
          "minLength": 1,
          "description": "The practitioner's last name, as on their license."
        },
        "first_name": {
          "type": "string",
          "minLength": 1,
          "description": "The practitioner's first name, as on their license."
        },
        "profession": {
          "enum": [
            "MD",
            "DO",
            "DDS_DMD",
            "RN",
            "NP",
            "PA"
          ],
          "type": "string",
          "description": "Clinical profession, to scope the board search."
        },
        "license_number": {
          "type": "string",
          "description": "Required for states verified live; the error detail shows the format."
        }
      },
      "additionalProperties": false
    }
    arguments 53 lines
  • screen_roster unknown never probed

    Adds practitioners to the account's roster for monthly monitoring (up to 500 per call). It does NOT return screening results: results arrive with the next monitoring run and are read with get_receipt (roster_id + period). Each entry needs NPI + first name + last name. Quota or prepaid debit is applied as POST /api/v1/rosters/bulk applies it (one unit per newly enrolled license; duplicates and failures are free; prepaid live keys also need the enterprise deposit floor). Sandbox keys enrol sample data only; nothing is screened for real. Not covered: instant results, people without an NPI. Needs an API key (Authorization: Bearer sw_live_… or sw_test_…); without one it returns an error that points to how_to_get_access.

    mcp-tool

    {
      "type": "object",
      "required": [
        "entries"
      ],
      "properties": {
        "entries": {
          "type": "array",
          "items": {
            "type": "object",
            "required": [
              "npi",
              "first_name",
              "last_name"
            ],
            "properties": {
              "npi": {
                "type": "string",
                "pattern": "^\\d{10}$",
                "description": "The 10-digit National Provider Identifier (NPI)."
              },
              "state": {
                "type": "string",
                "maxLength": 4,
                "minLength": 2
              },
              "last_name": {
                "type": "string",
                "minLength": 1
              },
              "first_name": {
                "type": "string",
                "minLength": 1
              },
              "profession": {
                "enum": [
                  "MD",
                  "DO",
                  "DDS_DMD",
                  "RN",
                  "NP",
                  "PA"
                ],
                "type": "string"
              },
              "license_number": {
                "type": "string"
              }
            },
            "additionalProperties": false
          },
          "maxItems": 500,
          "minItems": 1
        }
      },
      "additionalProperties": false
    }
    arguments 57 lines
  • get_coverage unknown never probed

    Lists every exclusion source and every state license source with its status today: live, not live, or information only. No key needed, free, returns no provider data. Use it before screening to know what a result can and cannot cover. A source that is not listed as live is not checked.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • get_pricing unknown never probed

    Plans, monthly request quotas, prepaid credit packs and deposit floors, in cents and dollars. No key needed, free, returns no provider data.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 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 e1113d28d3ded9e2.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/e1113d28d3ded9e2/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/e1113d28d3ded9e2/badge.svg)](https://brick.blue/agent/e1113d28d3ded9e2?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
100%

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.