MCP QUEEN
bid.scope/claims A
Insurance claims-side vendor procurement (IMEs, IA, surveillance). Preview - V2 launches Q3 2026.
Otherv1.0.5streamable-httpscope.bid repository
Grade evidence — probed 2026-07-12 20:46 UTC
| Criterion | Points | Observed |
|---|---|---|
| reachability | 25 / 25 | HTTP 200, initialize accepted in 1073ms |
| protocol | 15 / 15 | valid JSON-RPC initialize result, protocolVersion 2025-11-25, serverInfo scope-bid-claims@0.0.2 |
| tooling | 35 / 35 | tools/list OK: 14 tools e.g. "scope_claims_status"; 14/14 described, 14/14 fully-typed schemas, median description 144 chars |
| latency | 7 / 10 | initialize round-trip 1073ms |
| provenance | 15 / 15 | description present; repository linked; version 1.0.5; namespace bid.scope matches endpoint/repo |
Score 97/100 · latency 1073ms · 14 tools · auth: open
Connect your agent
Claude Code:
claude mcp add --transport http claims https://scope.bid/api/mcp/claims
Generic MCP client config:
{ "mcpServers": { "claims": { "type": "http", "url": "https://scope.bid/api/mcp/claims" } } }
MCP Queen is a graded index, not a middleman — your agent connects directly to the server above. Check the grade and evidence first; that's the point.
Share this server: permalink https://mcpqueen.com/s/bid.scope/claims · referral link https://mcpqueen.com/go/bid.scope/claims (counts as “routed via the queen”).
Own this server? Embed your grade badge
Live badge, re-probed continuously — put it in your README:
[](https://mcpqueen.com/s/bid.scope/claims)
Think the grade is wrong? Fix the finding the evidence shows, then the next probe cycle picks it up automatically (full cycle ≈ 3 days) — or open a dispute via the MCP endpoint.
Queen Watch
Email alerts when the grade changes or the endpoint stops answering. Double-opt-in, one-click unwatch, free while in beta.
Probe history
| When (UTC) | Grade | Score | Latency |
|---|---|---|---|
| 2026-07-12 20:46 | A | 97 | 1073ms |