Should my agent depend on the MCP server dev.sipflow/sipflow?

Verdict: allow — mid-solo — safe to depend on As of 2026-08-15T11:28:18Z: a dated observation with receipts, not a warranty.

Sipflow

dev.sipflow/sipflow

SIP/VoIP/telecom grounding for AI agents: vendor docs, RFCs, STIR/SHAKEN, traces, configs.

— the operator's own registry description reported

Publisher dev.sipflow · first seen 2026-08-12 · endpoint https://mcp.sipflow.dev/mcp

allow

verdict

mid-solo

cluster

ok_tools

answers

tools served

Dependency rating derived

allow — mid-solo — safe to depend on

Cluster mid-solo · distinctiveness 0.447 (moderate). Every figure is a percentile or class within the 11,094-server census — see the whole spectrum.

Reach — can an agent get to it?

answersalive_tools

latency285 ms

vs populationtypical

protocolcurrent

authopen

Use — can it use it?

tools22

vs populationmid

capabilities3

harnessA

Trust — can it rely on it?

identitysolo

servers on its host1

verifiabilityunassessed

duplicate inventoryno

drift events0

answers trueno primary

🔏 Signed receipt rr_0893a9f8f24152e407a0fd47 · ed25519 · key rs-rcpt-2026-08 — this rating is tamper-evident; an agent gets the full signature from check_server and can verify it against the published key.

Tools last seen

compare_sdp_offer_answer detect_sip_stack detect_sip_vendor_from_config diff_sip_messages dns_diagnose_sip_target fetch_sipflow_share lint_sip_request lookup_response_code lookup_sip_header minimize_sip_trace parse_sdp parse_sip_message render_sip_ladder review_sip_config search_sip_docs sip_ladder_example stir_attestation_explainer submit_sipflow_feedback troubleshoot_response_code validate_e164_number validate_stir_shaken_identity webrtc_sip_checklist

Harness readiness observed

Can an agent's harness pick this tool and call it correctly? Graded on the three things an agent reads — name, description, typed parameters. Band A — an agent can pick and call these reliably.

legibility check	tools passing	ok
name is clear & specific	22/22	✓
has a description	22/22	✓
description is substantive	22/22	✓
parameters are typed	22/22	✓
parameters are described	22/22	✓

22 of 22 tools graded · 22 with a captured input schema. RS-008, Tier-1 — no domain knowledge, applies to any tool. “Alive” is not the same as “usable”.

Truth checks observed

Not in the Tier-2 trade lane, or not yet checked. Tier-2 re-derives a server's answers against published primary sources — see truth checks.

Protocol conformance observed

2025-06-18

protocol version

—

session model

0.2.0

server version sipflow

Capabilities: completions resources tools

Drift

No confirmed drift on record. Baseline set 2026-08-14; changes appear here after human review.

History observed

Every probe we made, oldest → newest (2 shown, 2026-08-12 → 2026-08-14). Green answered · amber answered-but-walled · red no useful answer. A gap in our cadence is a gap in coverage, not evidence about the server.

changelog (1 events)

date	type	what changed
2026-08-12	outcome	first probe: ok_tools

raw probe records

probed (UTC)	outcome	http	ms	protocol
2026-08-14T19:58:45Z	ok_tools	200	285	2025-06-18
2026-08-12T05:33:59Z	ok_tools	200	439	2025-06-18

Watch or embed this verdict

Operators: put the live verdict in your README — it updates with every census, links back here, and is a dated observation, never a warranty:

[![Robin Saige verdict](https://robinsaige.com/badge/dev.sipflow/sipflow.svg)](https://robinsaige.com/s/dev.sipflow/sipflow)

Depend on it? Subscribe to its change feed — outcome changes and confirmed drift, no account needed. Building on it? The full dossier as JSON — verdict, rating, truth checks, history — stable enough to gate CI on.

← overview