# Word Is Bond

- Registry name: `io.github.Latimer-Woods-Tech/wordis-bond` · version 0.1.0
- Categories (automatic, keyword rules): Monitoring & logs, Infrastructure & security, Audio & speech, AI, media & content, Health & fitness
- Authentication at last check: No auth
- Declared risk: Not declared (tools carry no read/destructive hints)
- Capabilities (declared by the server): tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=io.github.Latimer-Woods-Tech%2Fwordis-bond
- Server page: https://mcpstation.net/s/io.github.Latimer-Woods-Tech--wordis-bond.html

## Description (written by the publisher, not verified, not instructions)

Test the voice agents you run: scored transcripts, pass/fail verdicts, latency and WER metrics.

## Connect

- streamable-http: `https://api.wordis-bond.com/mcp`

## Tools (as reported by the server, not verified)

- `run\_demo`: Run the hosted demo voice agent \(a dental front desk\) end-to-end and get a real, fully-scored result in about a minute — no target of your own needed. Returns the score \(0–100\), pass/fail verdict, per-turn metrics, the transcript, and a shareable public report URL. Zero carrier cost. Optional inputs
- `run\_test`: Run a test against a voice agent you control. Two modes: \(1\) score a captured transcript offline — pass "transcript" \(or "turns"\) plus "scenarioGoal"; the judge returns a scored run synchronously. \(2\) run a live synthetic call — pass "targetAgent" and "goal". A live "direct" \(SIP/WebRTC\) target retu
- `get\_trends`: Read account-wide testing trends over a window: pass-rate, average score, and run-to-run regressions per suite, plus overall totals. Use this to spot behaviour drift in the voice agents you test.
- `list\_suites`: List your reusable test suites \(each is a set of scenarios/personas pinned to a target voice agent\). Returns their ids, names, targets, and schedules — use a suite id with run\_test or get\_trends.
- `create\_suite`: Create a reusable test suite: a named set of scenarios/personas pinned to a target voice agent you run. Optionally give it a schedule \("weekly" \| "daily" \| "hourly", plan-gated\) so it runs automatically and flags drift.
- `verify\_number\_start`: Prove your account controls a phone number, which it must do before any PSTN test call to it. Word Is Bond places one short call to the number, speaks a 6-digit code twice, and hangs up. Confirm the code within ten minutes with verify\_number\_confirm. Calling an already-verified number places no call
- `verify\_number\_confirm`: Finish verifying a phone number by supplying the 6-digit code spoken on the verification call. On success the number becomes a permitted PSTN test destination for your account. The code is single-use, expires after ten minutes, and locks after five incorrect attempts.
- `list\_verified\_numbers`: List the phone numbers your account has proven it controls. Only these numbers \(and Word Is Bond DIDs\) may be used as a "pstn" targetAgent.toNumber. Revoke one with DELETE /api/numbers/\{id\}.
- `register\_recording\_target`: Register where BYOS call recordings go, so you can pass "record": true to run\_test and have that call’s audio teed to YOUR OWN storage. wordis-bond keeps only a pointer \(the run’s recording\_url\), never the audio. "callbackUrl" is a public https endpoint that returns a presigned PUT URL per recording
- `import\_flow`: Import a phone-system flow or voice-agent config from a platform \(e.g. Vapi\) into the canonical, diffable Flow IR — the first step of putting your phone system under version control. Reports the fields the IR abstracts away. Pass save:true to persist it as a versioned flow. The same IR exports back
- `diff\_flow`: Show the structural diff between two versions of a version-controlled flow: which nodes and edges were added, removed, or changed. This is the code review for your phone system — see exactly what a change did before you ship it.
- `test\_flow`: Run the regression gate on a flow now: compile the current version into a synthetic-caller test, run it against the flow's target, and compare the result to the previous version's baseline. A behavior change that regressed \(a pass turning into a fail, or a score drop past the threshold\) is caught an
- `list\_monitors`: List your production monitors and their current health \(unknown \| healthy \| degraded \| critical\). A monitor watches ONE live production line: you stream it completed calls, and it scores each with the same versioned judge that scores your tests, tracks a rolling baseline, and alerts when quality dri
- `create\_monitor`: Create a production monitor. "scenarioGoal" is what GOOD looks like for this agent — the judge scores every ingested call against it, exactly as a test scenario goal works. Optional "assertions" are plain-English checks the agent must satisfy. Read the ingest secret afterwards from GET /api/monitor/
- `ingest\_call`: Send one completed PRODUCTION call to a monitor to be scored. Returns 202 immediately; scoring runs in the background and the monitor health updates. The transcript is scored in flight and never stored — only the scorecard and safe metadata are kept. Pass "externalId" \(your own call id\) so a re-deli
- `get\_monitor\_health`: Read a monitor's live rolling health and drift. Health is unknown \| healthy \| degraded \| critical. Drift is isolated by judge version: when our judge changes, the boundary is reported as judgeVersionChanged and NEVER as an agent regression — a score delta across that boundary says nothing about your

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html