Fraud verdicts, route checks and caller-ID verification for every SIP call, operated by your AI: connect your switch, request test calls you confirm in the portal, read verdicts and transcripts, verify caller ID.
https://ovs.telecomsxchange.com/api/mcpOpen Voice Shield: voice call fraud analysis on a SIP trunk, operated by an agent.
The path from nothing to a verdict:
any account tool -> the first call answers 401 and your client opens the Open Voice Shield sign-in (or sign-up) page; the person signs in there, never in the chat
-> where calls should go on to (your switch / a carrier), host+port+transport. Credentials a destination needs are entered in the portal, not here
-> (optional) admit INVITEs from your switch's IP; not needed for test calls
/ -> (optional) a signed POST of every analysed call; alerts by e-mail or to a Slack channel connected in the portal
-> REQUESTS a test call. Nothing rings until the person opens the returned confirm_url and confirms number, caller ID, mode and duration in the portal. Poll until status is done, then /. Every test call opens with a recorded announcement that it is an automated test call placed on behalf of an Open Voice Shield account holder, and that it is recorded. The caller ID is the platform's own number unless you give one of the account's verified numbers (; numbers are verified by the person in the portal). Speech: "route_test" (a neutral announcement, any number), "scam_sample" (a known card-services scam recording, only to a verified number, to confirm a block verdict comes back) or "agent" (one of the account's own voice-agent destinations speaks on the call, only to a verified number). Synthesized speech exists only there: from the account's own agent, on a confirmed call to a verified number, inside the call; no tool returns audio. Everything is per-second billing plus a per-call analysis fee.
Calls through the hop are recorded and transcribed, and transcripts are returned to the assistant. Recording consent and any announcement the law requires on the customer's own traffic are the account holder's responsibility. Retention and deletion: https://ovs.telecomsxchange.com/privacy
4 in the Claude listing