Developer · Remote MCP server
Vigía
What breaks between versions, per-version vulnerabilities, compatible versions: npm/PyPI facts.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
cloud.coredls.vigia/vigia- Version
- 0.3.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-10-01
- Updated
- 2026-10-01
- Publisher
- cloud.coredls.vigia
- Namespace
- Namespace verified by the MCP Registry via the domain vigia.coredls.cloud or a parent domain of it · how
- Website
- vigia.coredls.cloud
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://vigia.coredls.cloud/mcp | None |
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 200)
- Handshake
- vigia 0.3.0 · protocol 2025-06-18
- Tools discovered
- 9:
package_status,upgrade_impact,symbol_status,find_compatible_version,version_status,check_dependencies,recent_changes,model_info,find_package - Checked on
- 2026-10-05
How to connect Vigía
Vigía is a remote MCP server: there is nothing to install. Its endpoint is https://vigia.coredls.cloud/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.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
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 developer servers
| Server | Runs |
|---|---|
| vibgrate.comQuery your team's drift, vulnerability, and upgrade data from any AI assistant. OAuth 2.1, 51 tools. | Remote · HTTPLive check: sign-in required |
| Vibie MCPDeploy HTML folders to vibie.page from Claude / Cursor - one-line install, OAuth, auto-update. | Local · stdio |
| VidinTurn a screen recording into agent-readable annotated keyframes. MCP server + CLI on ffmpeg. | Local · stdio |
| ViewportWitness by Apex LabsAgent website testing: browser QA, visual regression, Markdown extraction, and security checks. | Remote · HTTPLive check: ✓ handshake |
| VigilisGate AI-written tests: heal safe drift, refuse to hide real bugs, sign a verifiable receipt. | Local · stdio |
| Vim MCPConnect Claude Code to Vim/Neovim - query state, execute commands, search help, record macros. | Local · stdio |
| VinktarProduct analytics and error tracking your coding agent can use. | Remote · HTTPLive check: sign-in required |
| VinvVinv runs, tests, and finds issues in your services - with zero code changes. | Local · stdio |