MCP server health, State of MCP census
Scope (Claims) - Preview
bid.scope/claims
Insurance claims-side vendor procurement (IMEs, IA, surveillance). Preview - V2 launches Q3 2026.
Checks
The exact rows akashi check bid.scope/claims prints, from the 2026-07-02 census.
| Check | Status | Detail |
|---|---|---|
| registry status | pass | active |
| server.json valid | pass | validates against its declared JSON Schema |
| repo reachable | pass | exists |
| repo freshness | pass | pushed 21d ago |
| package npm | pass | published (1.0.5) |
| remote reachable | pass | HTTP 200 via initialize |
| MCP conformance | pass | initialize handshake ok |
| tools/list | pass | 14 tools: scope_claims_status, scope_claims_join_waitlist, scope_briefing, scope_roster_audit, scope_spend_rollup, scope_vendor_health, scope_credential_alerts, scope_conflict_log, ... |
| at least one live entrypoint | pass | 3 alive |
| license present | pass | Apache-2.0 |
Evidence
Packages
- npm @scope-bid/scope-claims-mcp · published(1.0.5)
Remote endpoints
- https://scope.bid/api/mcp/claims
streamable-http · reachable· HTTP 200· initialize_ok
14 tools: scope_claims_status, scope_claims_join_waitlist, scope_briefing, scope_roster_audit, scope_spend_rollup, scope_vendor_health, scope_credential_alerts, scope_conflict_log, ...
server.json
validagainst its declared schema
One of 14559 servers in the 2026-07-02 State of MCP census: 11582 healthy (79.6%), 2212 degraded (15.2%), 596 dead (4.1%), 169 unknown (1.2%).
Verify it yourself
This page is a static read of one dated probe. Run the same check locally, any time, with no key:
$ akashi check bid.scope/claimsInstall Akashi - single Go binary, zero keys, MIT licensed.
Is this your server?
Claiming a server (an auto-refreshing badge and a verified publisher profile) is coming soon. Until then, embed the verified-on-date badge yourself with akashi check bid.scope/claims --badge.
Open data, CC BY 4.0. How this census works - denominator, tiers, and what each check does.