Data · Remote MCP server
Nvoip MCP Server
Secure Nvoip MCP server for reports, call analytics, service quality, and business insights.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
br.com.nvoip/mcp-server- Version
- 0.2.3
- Status
- Active
- Category
- data
- Transport
- Streamable HTTP
- Published
- 2026-05-04
- Updated
- 2026-05-04
- Publisher
- br.com.nvoip
- Namespace
- Namespace verified by the MCP Registry via the domain nvoip.com.br or a parent domain of it · how
- Repository
- github.com/Nvoip/nvoip-mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.nvoip.com.br/mcp | Authorization (required, secret) |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
How to connect Nvoip MCP Server
Nvoip MCP Server is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.nvoip.com.br/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The registry entry declares an HTTP header for the connection: Authorization (required, secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More data servers
| Server | Runs |
|---|---|
| Nve MCPNorwegian flood & landslide hazard data from NVE, by WGS84 coordinate. | Local · stdio |
| NVEILData processing and visualization toolkit - 50+ chart types, raw data stays local. | Local · stdio |
| NVIDIA AI CKGNVIDIA AI knowledge graphs - 20 domains. 4x F1, 11x fewer tokens, SHA-256 provenance. MCP-native. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| NVIDIA NemoClaw CKGNVIDIA NemoClaw knowledge graph - 55 nodes, F1 0.576 (+269% vs RAG), 11x fewer tokens. MCP-native. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| NwsNWS MCP - US National Weather Service (no auth) | Remote · HTTPLive check: ✓ handshake |
| NWS Surface Wind Observations MCP ServerNWS surface wind observations (ASOS/AWOS) via Weather.gov and Iowa Environmental Mesonet APIs. | Local · stdio |
| Nws Weather MCP ServerGet US weather forecasts, active alerts, and current observations. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| Ny ProcurementNew York State Procurement MCP - State contract awards & procurement (keyless). | Remote · HTTPLive check: ✓ handshake |