# Latimer Woods Tech Wordis Bond MCP server

Source: https://glimind.com/server/mcp-registry%2Fio.github.latimer-woods-tech%2Fwordis-bond
Registry id: `mcp-registry/io.github.latimer-woods-tech/wordis-bond`
Status: live (checked 2026-10-27T14:14:51.003Z)

## Measurements (30 days)

- Uptime: 100%
- Checks: 5043
- Outages (90 days): 3

## Install

```json
{
  "mcpServers": {
    "latimer-woods-tech-wordis-bond-mcp-serve": {
      "type": "http",
      "url": "https://api.wordis-bond.com/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http latimer-woods-tech-wordis-bond-mcp-serve https://api.wordis-bond.com/mcp
```

## Tools (16)

- `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
- `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" | "hou
- `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 y
- `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, t
- `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 
- `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 
- `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 transc
- `list_monitors`: List your production monitors and their current health (unknown | healthy | degraded | critical). A monitor watches ONE live production line: you stream it comp
- `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 su
- `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 
- `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
- `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 t
- `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
- `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
- `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 f
- `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

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.