
Vocenya MCP server
Which MCP servers are Vocenya's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-25
- Registry namecom.vocenya/docsverified in the MCP registry
The registry name sits under vocenya.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-25
- Tools4
- Server calls itselfVocenya Docs
- Server version1.0.0
- Protocol version2025-06-18
On 2026-10-25 the server answered initialize and tools/list without a sign-in. First answer in 277 ms.
- Its tools do none of the product's use cases we checked: answer incoming business calls around the clock; book appointments into a calendar during calls; send polite reminders about unpaid invoices.
- Checked on 3 of the 7 days it takes to judge reliability.
Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.
- INITE MCP scoreafter a weeka score needs 7 daily checks: 3 so far
- What an agent can do with it0 of 3 use cases
- Answeredmeasuring3 of the 7 daily checks it takes to print a share
- Median first answer316 ms
- Space in an agent's context≈ 531 tokensthe definitions of all its tools (4), which an agent carries on every turn
- Tool definitionsA · 100 of 100
- Typed results0 of 4 toolsdeclared outputSchema: results come typed, read once
- Every tool passes all six checks.
What an agent can do with it
- cannot · answer incoming business calls around the clock
- cannot · book appointments into a calendar during calls
- cannot · send polite reminders about unpaid invoices
Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?
Worth a look
None of the five warning signs in these definitions.
A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →
search_docsSearch the Vocenya developer docs: guides (authentication, webhooks, pagination, outbound calling rules, live chat, MCP) and every API endpoint. Returns the best matches with their page URL; read one with get_doc_page or get_endpoint.
get_doc_pageGet one page of the Vocenya developer docs as Markdown, exactly as published. Slugs: "index", a guide like "quickstart", "authentication", "webhooks", "webhook-events", "outbound-calls", "live-chat" or "mcp", "reference" for the API…
list_endpointsList the endpoints of the Vocenya REST API with their method, path, summary and required scope, grouped by resource. Pass a tag (resource) like "Leads" or "Webhooks" to list one resource. Get the details of one with get_endpoint.
get_endpointGet one Vocenya API endpoint in full, as Markdown: its scope, path and query parameters, request body, responses, response attributes and code samples in cURL, Node, PHP and Python. Example: method "POST", path "/leads".
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"docs": {
"type": "http",
"url": "https://vocenya.com/mcp/docs"
}
}
}Add it
Claude Code, in a terminal
claude mcp add --transport http vocenya https://vocenya.com/mcp/docsclaude.ai, ChatGPT and other clients: add https://vocenya.com/mcp/docs as a custom connector in the settings.
- com.vocenya/platformanswers, requires sign-inverified in the MCP registry
- com.vocenya/siteanswers, 7 toolsverified in the MCP registry
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Cookies
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.