# io.github.Vonage/vonage-documentation-mcp

> MCP server for Vonage API documentation, code snippets, tutorials, and troubleshooting.

- name: io.github.Vonage/vonage-documentation-mcp
- version: 1.0.0
- connection class: R0 (autonomous)
- trust: 83/100
- quality: 79/100 (good)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/io.github.Vonage%2Fvonage-documentation-mcp
- tools: https://api.protogrid.dev/v1/servers/io.github.Vonage%2Fvonage-documentation-mcp/tools

**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.

## Connection (mcpServers)

```json
{
  "mcpServers": {
    "vonage-documentation-mcp": {
      "type": "http",
      "url": "https://documentation-mcp.vonage.dev/mcp"
    }
  }
}
```


## Trust

- hygiene: 100
- liveness: 100
- freshness: 45
- provenance: 80
- drivers: +repository +namespace-matches-repo +reachable +uptime-100% -stale-310d
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 79/100 (good)

### protocol: 75 (weight 25)

- warn `protocol.modern`: newest supported version is 2025-06-18; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
- n/a `protocol.stateless`: only applies to 2026-07-28 servers
- pass `protocol.transport`: streamable HTTP
- n/a `protocol.list_ttl`: only applies to 2026-07-28 servers

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 71 (weight 30)

- pass `tools.descriptions`: every tool has a description
- pass `tools.description_length`: descriptions are concise
- pass `tools.schemas`: every tool has an object input schema
- fail `tools.annotations`: no tool declares readOnlyHint or destructiveHint, so clients cannot tell safe calls from risky ones
- fail `tools.directory_hints`: no tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: vonage_api_reference (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); vonage_code_generator (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); vonage_tutorial_finder (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); …
- pass `tools.token_cost`: about 926 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump

### stability: 100 (weight 15)

- pass `stability.changes`: no tool changes in 30 days
- pass `stability.rug_pull`: no tool changed its meaning under the same name

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 7, about 926 tokens to load them all
- tool set hash: 8622b96d5e674294245c3fad3592618f
- badge: [![protogrid quality](https://protogrid.dev/badge/io.github.Vonage/vonage-documentation-mcp.svg)](https://protogrid.dev/servers/io.github.Vonage/vonage-documentation-mcp)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

_No tool definition changes recorded._

## Remotes

- https://documentation-mcp.vonage.dev/mcp (streamable-http, auth none, reachable true, uptime30d 1)

## Packages

_none_

## Tools (7)

- `vonage_api_reference`: 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.
- `vonage_code_generator`: 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.
- `vonage_docs_search`: 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.
- `vonage_sdk_info`: 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.
- `vonage_troubleshooter`: 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.
- `vonage_tutorial_finder`: 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.
- `vonage_use_case_examples`: 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.