Sipflow MCP is a SIP/VoIP/telecom grounding layer and PCAP analyzer: - Hybrid search across a curated VoIP corpus — ~40 vendor stacks, 60+ RFCs, STIR/SHAKEN, ATIS branded-calling specs - Vendor detection from a trace or a config blob (Kamailio, OpenSIPS, FreeSWITCH, Asterisk, SIP.js, JsSIP, ...) - Trace tools — minimize noisy headers, render SIP ladders as Mermaid, lint/diff/parse messages - Config review for Kamailio / OpenSIPS / FreeSWITCH / Asterisk with risk flags - SDP parse + offer/answer compare - STIR/SHAKEN Identity header validation and attestation explainer - E.164 number validation, response-code troubleshooter, DNS NAPTR/SRV + TLS cert diagnostics - One-shot hydration of `sipflow.dev/share/<token>` URLs All tools are read-only. Every result carries a verbatim `source_url` so the agent cites real RFC sections and vendor docs instead of hallucinating directive names or response-code semantics. A skill (`/sip-debugger`) and a file-scoped rule ship with the plugin so the agent reaches for these tools automatically when you're editing SIP material.

MCP readiness

B · 88/100

Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here B, 75.4/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ

Valid MCP handshake	10/10	initialize and tools/list both answered.
Live MCP endpoint	25/25	Endpoint answers the MCP initialize handshake (1648 ms).
Protocol revision	8/10	Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28.
Signed descriptor	n/a	No MCP standard defines a signed server descriptor.
Uptime (30 days)	15/15	31/31 probes succeeded over 30 days (100%).
Tool declaration	10/10	Lists 22 tool(s) with descriptions.
Verified identity	5/10	Publisher declared (repository, package or homepage); claim this listing to verify domain control.
Freshness + modern flags	4/5	seen in a source within 7 days.
Auth declaration	2/5	Declares credential scheme: smithery_api_key.

Applicable criteria total 90 points, scaled to 100.

Responsiveness: Responsive (1648 ms; bands ≤2.5 s, ≤5 s, ≤8 s, slower; penalty only).

Measured 2026-11-11.

Nine criteria, the same as the A2A readiness score, read from our daily MCP probe (initialize + tools/list) and 30-day probe history. No MCP standard defines a signed server descriptor, so that criterion is n/a and the other 90 points are scaled to 100. Grades: A>=90, B>=75, C>=60, D>=40, F<40. Display only: search order uses the quality grade.

Compared with peers

Against 53,039 reachable MCP servers in our daily snapshot (2026-11-12 06:46 UTC). Display only; it does not change search order.

Readiness: Higher than 95% of peers; This listing 88 · peer median 81
Latency: Faster than 27% of peers; This listing 538 ms · peer median 326 ms

Where it loses the most points, and how to win them back

Verified identity −5 — Claim the listing and prove control of its domain.
Now: Publisher declared (repository, package or homepage); claim this listing to verify domain control.
Auth declaration −3 — State how to authenticate (an auth scheme, or that none is needed).
Now: Declares credential scheme: smithery_api_key.
Protocol revision −2 — Support the current protocol revision.
Now: Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28.

How many agent tools actually work · All statistics

Listed in

Directories this entry was found in.

smithery since 2026-06-04 ↗

How to connect

MCP endpoint (streamable-http)

https://server.smithery.ai/sipflow/sipflow/mcp

JSON-RPC initialize probe

curl -X POST https://server.smithery.ai/sipflow/sipflow/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'

Homepage

https://www.sipflow.dev

Listed at (smithery)

https://www.sipflow.dev