Vigía
REMOTE · VIGIA.COREDLS.CLOUD · SCANNED SEP 28
Verified, dated facts on npm/PyPI package versions, deprecations, requirements, and AI model prices.
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 Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 446 tokens (~89/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage83
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 50% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
How do I install the Vigía MCP server?
Vigía is a hosted endpoint at https://vigia.coredls.cloud/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 · vigia.coredls.cloud
claude mcp add --transport http cloud-coredls-vigia-vigia 'https://vigia.coredls.cloud/mcp'
{
"mcpServers": {
"cloud-coredls-vigia-vigia": {
"url": "https://vigia.coredls.cloud/mcp"
}
}
} {
"servers": {
"cloud-coredls-vigia-vigia": {
"type": "http",
"url": "https://vigia.coredls.cloud/mcp"
}
}
} [mcp_servers.cloud-coredls-vigia-vigia] url = "https://vigia.coredls.cloud/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"cloud-coredls-vigia-vigia": {
"type": "remote",
"url": "https://vigia.coredls.cloud/mcp",
"enabled": true
}
}
} openclaw mcp add cloud-coredls-vigia-vigia --url 'https://vigia.coredls.cloud/mcp' --transport streamable-http
mcp_servers:
cloud-coredls-vigia-vigia:
url: "https://vigia.coredls.cloud/mcp" {
"McpServers": {
"cloud-coredls-vigia-vigia": {
"Transport": "http",
"Url": "https://vigia.coredls.cloud/mcp"
}
}
} assistant mcp add cloud-coredls-vigia-vigia -t streamable-http -u 'https://vigia.coredls.cloud/mcp'
{
"mcpServers": {
"cloud-coredls-vigia-vigia": {
"type": "http",
"url": "https://vigia.coredls.cloud/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.
- 28 Sept 26 70
First indexed and scored.
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 28 Sept 2026 · Probed https://vigia.coredls.cloud/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=vigia.coredls.cloud | CN=YR2,O=Let's Encrypt,C=US | 28 Sept 2026 | 27 Dec 2026 | RSA 2048 | SHA256-RSA | 5febcba77646008de1df27d5deff9cbad89 |
| SANs: vigia.coredls.cloud | ||||||
| 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 vigia.coredls.cloud. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| cloud. | present | 7041 | 13 | Verified |
| coredls.cloud. | 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 |
|---|---|
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://vigia.coredls.cloud/mcp | Verified | 200 | |
| http (plaintext) | http://vigia.coredls.cloud/mcp | HTTPS enforced | 301 | https://vigia.coredls.cloud/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 →
check_dependencies Check dependencies ~88
Evaluates a full package.json (npm) or requirements.txt (pypi): for each dependency returns the latest version, whether the declared range includes it (up_to_date / outdated / outdated_major) and whether the package is deprecated. Use when opening a project or before upgrading dependencies.
| Name | Type | Req | Description |
|---|---|---|---|
| ecosystem | string | yes | Package ecosystem |
| manifest | string | yes | Full content of the manifest file |
No output schema declared.
No examples provided.
find_package Find package ~42
Finds packages or models by name prefix, ordered by popularity. Use when the exact name is unknown.
| Name | Type | Req | Description |
|---|---|---|---|
| ecosystem | string | – | – |
| query | string | yes | – |
No output schema declared.
No examples provided.
model_info AI model info ~95
Price per million tokens, context window, max output and retirement date of AI models (OpenRouter catalog). Use before writing a model ID in code or estimating costs. With model_id returns one model; with provider or query returns a list.
| Name | Type | Req | Description |
|---|---|---|---|
| model_id | string | – | Exact ID in provider/model form, e.g. "anthropic/claude-x" |
| provider | string | – | – |
| query | string | – | – |
No output schema declared.
No examples provided.
package_status Package status ~87
Latest stable version, publish date, deprecation/yank status, runtime requirements (engines/python), peer dependencies, license and advisories of an npm or PyPI package. Use before recommending, installing or pinning a package version.
| Name | Type | Req | Description |
|---|---|---|---|
| ecosystem | string | yes | Package ecosystem |
| name | string | yes | Exact package name, e.g. "next", "@types/node", "requests" |
No output schema declared.
No examples provided.
recent_changes Recent changes ~69
Latest detected changes: new releases, deprecations, removed packages, AI model price changes or retirement announcements. Optionally filtered to one package or model.
| Name | Type | Req | Description |
|---|---|---|---|
| ecosystem | string | – | – |
| limit | integer | – | – |
| name | string | – | If set, history of that package or model |
No output schema declared.
No examples provided.
What is the Vigía MCP server?
Vigía is an MCP server listed in the public MCP registry as cloud.coredls.vigia/vigia. Verified, dated facts on npm/PyPI package versions, deprecations, requirements, and AI model prices. This page covers its hosted endpoint (https://vigia.coredls.cloud/mcp).
Is the Vigía MCP server safe to use?
Vigía scores 70 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 Vigía MCP server expose?
Vigía exposes 5 tools: package_status, check_dependencies, recent_changes, model_info, find_package. Their descriptions and schemas cost roughly 381 tokens of context every time the server is loaded.
Does the Vigía MCP server require authentication?
No. We connected to Vigía without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Vigía MCP server still maintained?
Vigía is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.