io.github.Vonage/vonage-documentation-mcp
REMOTE · DOCUMENTATION-MCP.VONAGE.DEV · SCANNED SEP 24
MCP server for Vonage API documentation, code snippets, tutorials, and troubleshooting.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 601 tokens (~85/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the io.github.Vonage/vonage-documentation-mcp server?
io.github.Vonage/vonage-documentation-mcp is a hosted endpoint at https://documentation-mcp.vonage.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · documentation-mcp.vonage.dev
claude mcp add --transport http vonage-vonage-documentation-mcp 'https://documentation-mcp.vonage.dev/mcp'
{
"mcpServers": {
"vonage-vonage-documentation-mcp": {
"url": "https://documentation-mcp.vonage.dev/mcp"
}
}
} {
"servers": {
"vonage-vonage-documentation-mcp": {
"type": "http",
"url": "https://documentation-mcp.vonage.dev/mcp"
}
}
} [mcp_servers.vonage-vonage-documentation-mcp] url = "https://documentation-mcp.vonage.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"vonage-vonage-documentation-mcp": {
"type": "remote",
"url": "https://documentation-mcp.vonage.dev/mcp",
"enabled": true
}
}
} openclaw mcp add vonage-vonage-documentation-mcp --url 'https://documentation-mcp.vonage.dev/mcp' --transport streamable-http
mcp_servers:
vonage-vonage-documentation-mcp:
url: "https://documentation-mcp.vonage.dev/mcp" {
"McpServers": {
"vonage-vonage-documentation-mcp": {
"Transport": "http",
"Url": "https://documentation-mcp.vonage.dev/mcp"
}
}
} assistant mcp add vonage-vonage-documentation-mcp -t streamable-http -u 'https://documentation-mcp.vonage.dev/mcp'
{
"mcpServers": {
"vonage-vonage-documentation-mcp": {
"type": "http",
"url": "https://documentation-mcp.vonage.dev/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 9 Sept 26 0
- Stability: 0.97 → pass security
- 8 Sept 26 0
- Stability: pass → 0.97 functional
- 26 Aug 26 79
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 10 Aug 26 0
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.50 ▲ functional
- 9 Aug 26 0
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.43 → unverified ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 6 Aug 26 0
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- Schema quality: unverified → fail ▼ functional
- Schema quality: unverified → excellent ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → pass ▲ functional
- First check of Tool coverage: 100 functional
- New tool “vonage_api_reference” functional
- New tool “vonage_code_generator” functional
- New tool “vonage_docs_search” functional
- New tool “vonage_sdk_info” functional
- New tool “vonage_troubleshooter” functional
- New tool “vonage_tutorial_finder” functional
- New tool “vonage_use_case_examples” functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 24 Sept 2026 · Probed https://documentation-mcp.vonage.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=documentation-mcp.vonage.dev | CN=YR2,O=Let's Encrypt,C=US | 19 Sept 2026 | 18 Dec 2026 | RSA 2048 | SHA256-RSA | 5a15ae86d1d6ee615628ffd4f0fa3c58015 |
| SANs: documentation-mcp.vonage.dev | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of documentation-mcp.vonage.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| vonage.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://documentation-mcp.vonage.dev/mcp | Verified | 200 | |
| http (plaintext) | http://documentation-mcp.vonage.dev/mcp | HTTPS enforced | 308 | https://documentation-mcp.vonage.dev/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
vonage_api_reference ~86
Provides a direct link or detailed information from the Vonage API reference documentation for a specific API endpoint. Use this when the user's query is highly technical and related to a specific endpoint, like API parameters, request bodies, or response schemas.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | The name of the Vonage API (e.g., 'SMS API', 'Voice API', 'Messages API'). |
No output schema declared.
No examples provided.
vonage_code_generator ~103
Generates a complete, runnable code snippet in a specified programming language for a given Vonage API task. This is the preferred tool when the user explicitly asks for a 'code snippet,' 'example,' or 'code in a specific language' like Node.js, Python, or cURL.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | A clear and concise description of the task for which the code snippet is needed (e.g., 'send an SMS', 'make a voice call'). |
No output schema declared.
No examples provided.
vonage_docs_search ~93
Searches the official Vonage developer documentation for guides, tutorials, and API references. This is the primary tool for general queries about Vonage's products, services, and APIs, and should be used when the user asks for information, documentation, or how-to guides.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | The user's search query, which can be a keyword, phrase, or a question about Vonage's APIs or documentation |
No output schema declared.
No examples provided.
vonage_sdk_info ~72
Retrieves information about a specific Vonage SDK, including installation instructions, supported features, and version numbers. This is for queries focused on the SDKs themselves, not the underlying APIs.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | The programming language of the SDK (e.g., 'Node.js', 'Python', 'PHP'). |
No output schema declared.
No examples provided.
vonage_troubleshooter ~77
Provides troubleshooting steps, common error code explanations, and debugging advice for Vonage API issues. Use this when the user is reporting a problem, error, or something not working as expected.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | A description of the problem or error the user is experiencing, including any error messages, codes, or unexpected behavior. |
No output schema declared.
No examples provided.
vonage_tutorial_finder ~92
Finds and provides a link to a step-by-step tutorial or a blog post on the Vonage Developer blog. This tool is for when the user asks for a 'tutorial' or a 'guide' on a specific topic.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | The topic of the tutorial or guide (e.g., 'building a voice proxy', 'two-factor authentication', 'receiving a delivery receipt'). |
No output schema declared.
No examples provided.
vonage_use_case_examples ~78
Finds and describes real-world use cases or customer stories for a specific Vonage product. Use this when the user asks for examples of how a product is used in a specific industry or for a particular purpose.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | The Vonage product (e.g., 'Video API', 'Voice API', 'Messages API'). |
No output schema declared.
No examples provided.
What is the io.github.Vonage/vonage-documentation-mcp server?
io.github.Vonage/vonage-documentation-mcp is listed in the public MCP registry as io.github.Vonage/vonage-documentation-mcp. MCP server for Vonage API documentation, code snippets, tutorials, and troubleshooting. This page covers its hosted endpoint (https://documentation-mcp.vonage.dev/mcp).
Is the io.github.Vonage/vonage-documentation-mcp server safe to use?
io.github.Vonage/vonage-documentation-mcp scores 79 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.Vonage/vonage-documentation-mcp server expose?
io.github.Vonage/vonage-documentation-mcp exposes 7 tools: vonage_docs_search, vonage_code_generator, vonage_api_reference, vonage_troubleshooter, vonage_tutorial_finder, and 2 more. Their descriptions and schemas cost roughly 601 tokens of context every time the server is loaded.
Does the io.github.Vonage/vonage-documentation-mcp server require authentication?
No. We connected to io.github.Vonage/vonage-documentation-mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.Vonage/vonage-documentation-mcp server still maintained?
io.github.Vonage/vonage-documentation-mcp is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.