SIP/VoIP/telecom grounding for AI agents: vendor docs, RFCs, STIR/SHAKEN, traces, configs.
AI & Agentsv0.2.0streamable-httpmcp.sipflow.dev repository
| Criterion | Points | Observed |
|---|---|---|
| reachability | 25 / 25 | HTTP 200, initialize accepted in 258ms |
| protocol | 15 / 15 | valid JSON-RPC initialize result, protocolVersion 2025-06-18, serverInfo sipflow@0.2.0 |
| tooling | 35 / 35 | tools/list OK: 22 tools e.g. "search_sip_docs"; 22/22 described, 22/22 fully-typed schemas, median description 967 chars |
| latency | 10 / 10 | initialize round-trip 258ms |
| provenance | 15 / 15 | description present; repository linked; version 0.2.0; namespace dev.sipflow matches endpoint/repo |
Score 100/100 · latency 258ms · 22 tools · auth: open
Claude Code:
claude mcp add --transport http sipflow https://mcp.sipflow.dev/mcp
Generic MCP client config:
{ "mcpServers": { "sipflow": { "type": "http", "url": "https://mcp.sipflow.dev/mcp" } } }
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/dev.sipflow/sipflow · referral link https://mcpqueen.com/go/dev.sipflow/sipflow (counts as “routed via the queen”).
Live badge, re-probed continuously — put it in your README:
[](https://mcpqueen.com/s/dev.sipflow/sipflow)
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.
Email alerts when the grade changes or the endpoint stops answering. Double-opt-in, one-click unwatch, free while in beta.
| When (UTC) | Grade | Score | Latency |
|---|---|---|---|
| 2026-07-13 10:45 | A | 100 | 258ms |