Nopaque | Customer Perspective Voice Testing for Agentic IVR
Nopaque | Customer Perspective Voice Testing for Agentic IVR
Map, test, and load-test agentic voice bots from the customer
This listing identifies a third-party MCP server. MCPBundles is not affiliated with, sponsored by, or endorsed by the service or its operator unless stated on this page.
This server may ask you to sign in when your AI client connects.
Last probed Nov 3, 2026 · mcp.nopaque.co.uk
26tools discovered
For AI agents — MCPBundles Directory API
For MCP client apps (human connect):
MCP connect URL: https://mcp.nopaque.co.uk/mcp
Skill page: https://www.mcpbundles.com/skills/nopaque-mcp-0e023802a5
Explore capabilities (26)
read 18
write 7
Showing 25 of 26
Showing 25 of 26 tools from the public preview. Connect the server to inspect the full live tool list.
Get8
List7
Draft Mission Test Config2
Run2
Other capabilities6
Create IVR Mapping Job
write
createMapping
Create an IVR mapping job that will call the specified phone number, navigate the menu tree via DTMF and/or voice prompts, transcribe audio, and analyse with AI to discover all branches. Returns a job resource immediately with status="idle". To start the actual mapping, call the startMapping REST endpoint (not yet exposed via MCP — use the REST API or wait for follow-up phases). Mapping completion typically takes 2-15 minutes depending on tree depth.
Create IVR Mapping Job — Create an IVR mapping job that will call the specified phone number, navigate the menu tree via DTMF and/or voice prompts, transcribe audio, and analyse with AI to discover all branches. Returns a job resource immediately with status="idle". To start the actual mapping, call the startMapping REST endpoint (not yet exposed via MCP — use the REST API or wait for follow-up phases). Mapping completion typically takes 2-15 minutes depending on tree depth.
Get Mapping Job — Get the current state and run metadata for a specific IVR mapping job.
USE WHEN:
- User asks about a specific mapping job by ID
- User wants to know if a mapping run has finished
- User wants run-level metadata (stats, in-flight calls, start/completion times)
- You need a job's currentRun.id to feed into getMappingTree or REST /mapping/{id}/runs
QUERY PARAMS (optional):
- version: Run number (1-indexed) — fetches that specific historical run. Default: latest run.
List Mapping Jobs — List IVR mapping jobs in your workspace. Supports filtering and cursor pagination.
FILTERS (all optional):
- status: Filter by the latest run's status. Values: idle | running | completed | failed | limited.
IMPORTANT: Mapping JOBS cycle between status `running` (active mapping) and `idle` (between runs)
and NEVER reach `completed`. Only RUNS reach `completed`/`failed`/`limited`. The `status` filter
compares against the latest run's status — so `status=completed` return
Cancel Mapping Job — Cancel an in-progress IVR mapping job. Returns the updated job resource. No effect if the job is already idle/cancelled. Use this when you need to stop a long-running mapping early (e.g., the agent realised the wrong number was supplied).
Get Discovered IVR Tree — Get the discovered IVR tree structure for a mapping job — every node visited, the DTMF/voice paths between them, audio recordings, and (if enrichment ran) IVR menu transcripts and probe classifications.
USE WHEN:
- User asks for the discovered tree / map / structure of an IVR
- User wants leaf-node count, depth, or aggregate tree statistics (use `format=flat`)
- User wants to inspect specific tree-node fields (voice prompts, probe classifications, audio URLs)
- User wants to
Get your MCP into directories
A working endpoint is step one. Directory coverage is the coordinated launch across ChatGPT, Claude, Cursor, the MCP Registry, and community indexes.
What is the Nopaque | Customer Perspective Voice Testing for Agentic IVR MCP server?
Map, test, and load-test agentic voice bots from the customer
How do I connect Nopaque | Customer Perspective Voice Testing for Agentic IVR to my AI agent?
Use the MCP endpoint listed on this page in your MCP client configuration. One-click install pills support Claude, Cursor, VS Code, and other hosts. Copy the remote MCP URL if your client needs a manual entry.
Operate this server?
Request removal if you do not want Nopaque | Customer Perspective Voice Testing for Agentic IVR listed here, or claim the listing if you want to manage it on MCPBundles.
Operate Nopaque | Customer Perspective Voice Testing for Agentic IVR?
This server appears in the MCPBundles directory. Verify you operate it to take over the listing — name, description, logo, contact email, and skill content. We email a 6-digit code to a maintainer address your server publishes in /.well-known/security.txt or /.well-known/mcpbundles.json. Free, takes about a minute.
MCPBundles publishes this directory for MCP discovery. Except where we host or operate an offering, third-party services run under their own terms. Product and company names on this page are used in a descriptive, identifying way (including under nominative fair use where applicable); they remain the property of their owners. Nothing here grants you rights in those marks, and nothing here is an offer to sell a third party's services. Terms · Request removal
More in developer tools
Other MCP servers in this category from the directory index
Run Mission Test — Launch a mission test run from an existing saved mission-test-config. A mission test calls a number, executes a scripted persona+goal+acceptance flow, and the LLM self-reports pass/fail against the acceptance criterion at end-of-call. Returns the run resource immediately; poll getMissionTestRun for verdict.
Get Mission Test Run — Use when you have a mission-test run id and want the full AI-judged result: verdict (pass/fail/inconclusive/error), passReasoning, passEvidence, transcript, and compliance fields. Returns 404 for non-mission runs (compliance, standard, param) — use getRunResults for those. For listing across runs use listTestRuns; for counts and percentages use aggregateTestRuns. Returns 404 cross-workspace (D-02 strict type-gate).
List Mission Test Configs — List saved mission-test configs in your workspace with rich filters. Each saved config is a reusable mission-test definition (name, phone, sector, persona/mission, acceptance criterion, profile, optional tags). Filter by: `name` (substring), `phoneNumber` (E.164 exact), `sector` (e.g. `financial-services`), `profileId`, `tag` (lowercase exact, single tag), `createdAfter` / `createdBefore` (ISO8601). Sort by `createdAt` or `name`, asc/desc (default `createdAt desc`). Paginate via `cursor` + `limi
Draft Mission Test Config — Check a NEW mission-test config without saving it. Takes the same fields as creating one (name, phoneNumber in E.164, sector, mission, acceptance, profileId, optional description, tags, maxDurationSecs, voiceId, advancedParams) and returns the config as it would be stored plus `problems`: every failed check at once (invalid fields, a phone number the dial policy blocks, a caller persona that no longer exists). Nothing is saved or changed, so it is safe to call repeatedly. Use when: the user want
Draft Mission Test Config Change — Check a CHANGE to a saved mission-test config without saving it. Takes the config `id` and only the fields to change (same as the update body; `null` clears description, tags, maxDurationSecs or advancedParams). Returns the full config as it would be after the change, `changes` (only fields whose value would differ, with before and after), `problems` (every failed check at once) and `version` (the config's current updatedAt). Nothing is saved or changed, so it is safe to call repeatedly. Use whe
Get Mission Test Config — Get a single saved mission-test config by ID. Returns the full row: name, description, phoneNumber, sector, mission, acceptance, profileId, tags, createdAt, updatedAt. Use when: you have a config ID (typically from listMissionTestConfigs or from a run.configId field) and want to inspect the persona / mission / acceptance criterion text — for example before launching a new run or to explain to the user how a previous run was configured. Cross-tool: for run history launched from this config, use l
List Test Configs — List the saved standard (scripted) test configs in your workspace: the step-by-step tests that dial a number, send keypresses or speech, and compare what is heard against an expected transcript. Returns every config with its name, description, phoneNumber, language, type and steps. Use when: the user names a test and you need its id, wants to know what standard tests exist, or you need to turn a configId from listTestRuns / aggregateTestRuns into a name. These are NOT mission-test configs: for t
Get Test Config — Get a single saved standard (scripted) test config by ID: name, description, phoneNumber, language, type and its steps (each step has a name, the action taken, the expected transcript and the pass threshold). Use when: you have a config ID (from listTestConfigs, or the configId key of an aggregateTestRuns group, or testConfigId on a run) and want its name or to explain what the test checks. For mission-test configs use getMissionTestConfig. Cross-workspace returns 404.
Get Run Results — Get any test run (standard/param/mission/compliance) by id, including per-step results: outcome, transcript, similarity scores, words. Use when you need per-step breakdowns OR when you do not know if the run is mission or standard. For mission-specific shape (verdict, evidence, judgeReasoning) prefer getMissionTestRun. For listing across runs use listTestRuns; for counts use aggregateTestRuns. Returns 404 cross-workspace.
List Test Runs — List test runs (mission/compliance/standard/param) with rich filters: runType, outcome (PASS/FAIL/ERROR/INCONCLUSIVE), phoneNumber, configId, catalogueTestId, configName / configPhoneNumber (standard and param runs only: case-insensitive substring of the test name, substring of the number it dials), date range (startedAfter/startedBefore), sort (startedAt/completedAt asc/desc), and cursor pagination. Use cases: "last 3 mission failures", "runs against phone +44… this week", "compliance fails in
Aggregate Test Runs — Aggregate test-run counts; groupBy outcome | runType | configId | catalogueTestId | phoneNumber; optional timeBucket day/week/month with UTC ISO8601 bucket keys ("2026-05-12" day, "2026-W19" week, "2026-05" month). Use cases: "% pass/fail this week", "which compliance test fails most", "day-by-day pass count last 2 weeks". ALWAYS use this for "how many", "what share" and "which fails most": counting by paging through listTestRuns gives wrong totals. Filters: runType, outcome, phoneNumber, config
List Load Tests — List all load-test runs in your workspace. Each load test fans out N concurrent test runs against a target number and produces aggregate statistics. Returns a paginated array.
List Compliance Catalogue — List the available compliance tests in the regulatory catalogue (e.g., GDPR consent capture, EU AI Act disclosure, PCI-DSS DTMF masking). Each entry has an ID + sector + description. Use the IDs as input to runComplianceTest.
Run Compliance Test — Run a compliance test against a phone number. The test calls the number, executes a regulatory probe script (e.g., requests data deletion, asks about AI disclosure), and returns pass/fail per probe. Returns the run resource; poll getRunResults for completion.
Get Workspace Usage — Get the current usage and entitlement snapshot for your workspace: subscription tier, free-minute pool balances (testing/loadTesting/mapping/s2s/s2stest), purchased-pack balances, current-period consumption, and remaining LLM-enrichment tokens. Use this to check whether you have enough capacity before kicking off an expensive job. Returns 404 cross-workspace.
List UI Guides — List the step-by-step guides to the nopaque web app, and the reference pages (pricing, FAQ). Each entry has a slug, a kind (guide or reference), a group, a title and a one-line summary. Use when: someone asks how to do, set up or configure something in the web app, or what something costs, and you need to know whether a guide covers it. Pass a slug to getGuide for the full text. If no entry covers the question, there is no guide for it: say so rather than guessing at screens. The same for every
Get a UI Guide — Get the full text of one guide or reference page by its slug from listGuides. For a guide, sections holds the steps in order: each names the page, menu, button or field to use in the web app, with extra detail about what it does. Use when: listGuides shows an entry that covers what the person wants to do. The steps are for a person using the web app to follow; this tool does none of them. An unknown slug returns 404.
Register a Workspace and Get an API Key — Create a new TotalPath workspace and receive an API key for it. No account, key or human is needed to call this. It is the first step for an agent that has no TotalPath credential yet.
USE WHEN:
- You have no TotalPath API key and want to start using this server
- You have been asked to set up TotalPath from scratch
DO NOT USE WHEN:
- You already hold a TotalPath API key. Calling this again creates a second, separate, empty workspace. It does not add anything to the one you
Send a Verification Code to a Human's Mobile — Send a one-time code by SMS to a human's mobile phone, to verify that a real person stands behind this workspace. This is what unlocks calling capacity. The code goes to the PHONE, not to you. You then need to ask that person what the code says and pass it to verifyAnchorCode.
USE WHEN:
- You have just called registerWorkspace and the workspace has no capacity yet
- A person has agreed to be the accountable human for this workspace and has given you their mobile number
THE HUMA
Verify the Code and Unlock Calling Capacity — Submit the code the human read to you from their text message. On success the number is permanently recorded as this workspace's accountable human, and the workspace receives its free calling capacity, so it can now run createMapping, runMissionTest and runComplianceTest.
USE WHEN:
- You called requestAnchorCode and the person has told you the code
ARGUMENTS:
- phoneNumber: the SAME number you passed to requestAnchorCode, in the same E.164 format
- code: the digits from the
Showing the first 25 tools — full list and schemas: Directory API.
How many tools does Nopaque | Customer Perspective Voice Testing for Agentic IVR provide?
MCPBundles probed 26 tools on the live server. The tool list on this page reflects what was discovered at the last refresh — connect your client to see the full set available to your session.
What authentication does Nopaque | Customer Perspective Voice Testing for Agentic IVR require?
Nopaque | Customer Perspective Voice Testing for Agentic IVR may require signing in to the provider before tools can run. Connect through MCPBundles or your MCP client and complete any provider login when prompted.
Don't want this listed?
Request removal from the MCPBundles directory. We stop publishing this listing on mcpbundles.com.
MCPBundles is an independent platform built on the open Model Context Protocol standard. MCPBundles is not affiliated with, sponsored by, or endorsed by Anthropic PBC.