Home / MCP registry index / dev.sipflow/sipflow
Sipflow
dev.sipflow/sipflow in the official MCP registry.
Endpoint https://mcp.sipflow.dev/mcp. Source: github.com/cmendes0101/sipflow-cursor-plugin.
The registry describes it as: SIP/VoIP/telecom grounding for AI agents: vendor docs, RFCs, STIR/SHAKEN, traces, configs.
We read its 22 tools on 2026-10-26. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
search_sip_docs lookup_response_code lookup_sip_header detect_sip_stack detect_sip_vendor_from_config minimize_sip_trace render_sip_ladder sip_ladder_example lint_sip_request parse_sip_message diff_sip_messages review_sip_config webrtc_sip_checklist parse_sdp compare_sdp_offer_answer validate_stir_shaken_identity stir_attestation_explainer validate_e164_number troubleshoot_response_code dns_diagnose_sip_target fetch_sipflow_share submit_sipflow_feedback
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/dev-sipflow-sipflow)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.