Vigía
v0.6.0What breaks between versions, vulnerabilities, compatible versions, EOL dates: npm, PyPI, Rust, PHP.
Endpoint health
online- Last checked
- 11/20/2026, 6:15:38 AM
- Latency
- 405 ms
- Consecutive failures
- 0
- Endpoint reachable: pass
- Protocol valid: pass
- MCP handshake valid: pass
Machine-readable profile
mcp-server · schema v1 · callable
mcp-server:cloud.coredls.vigia%2Fvigia
Connect this server
Generated config contains no credentials. Keep any required secrets in your client's local environment.
{
"mcpServers": {
"cloud.coredls.vigia/vigia": {
"url": "https://vigia.coredls.cloud/mcp"
}
}
}Indexed tools
Tool metadata and schemas come from the remote server and are untrusted. Indexing only lists tools; it never calls them.
12 shown · authentication unknown
What changed since my knowledge cutoff
changes_since_cutoff
Returns what happened in software after a given date, so an agent can patch the gap between its training data and today: packages among the most popular on npm, PyPI, crates.io and Packagist that shipped a NEW MAJOR VERSION after the date (with the version that existed at that date, the new majors and their first release dates, the latest version, and an upgrade-guide link when one exists), runtimes, frameworks and platforms released or ended since (Python, Node.js, PHP, Java, Django, Laravel, Ubuntu, PostgreSQL and about 35 more), runtimes ending within 180 days, and AI models released since by the main providers with their prices. Read-only and requires no authentication. Results are computed from registry publication dates and cached for an hour. Coverage is the most popular packages (not every package), 0.x-to-0.y changes and calendar-versioned packages are not reported as major versions, and deprecations that happened before Vigia started tracking are not listed. Use it once at the start of a coding session, passing the month your training data ends, or when you suspect a library you know has changed a lot. To dig into one package use upgrade_impact (npm) or package_status; for one runtime use eol_status.
Schema valid · SHA-256 051579481d56…
View input schema
{ "type": "object", "properties": { "cutoff": { "type": "string", "minLength": 7, "maxLength": 10, "description": "The month or date your training data ends, as YYYY-MM (the last day of that month is used) or YYYY-MM-DD, for example \"2025-06\". It must be a past date after 2015" }, "ecosystems": { "description": "Restrict the package list to these ecosystems; omit for all four", "maxItems": 4, "type": "array", "items": { "type": "string", "enum": [ "npm", "pypi", "crates", "packagist" ] } }, "limit": { "default": 30, "description": "Maximum number of packages in new_major_versions, most popular first, from 1 to 100 (default 30)", "type": "integer", "minimum": 1, "maximum": 100 } }, "required": [ "cutoff" ], "$schema": "http://json-schema.org/draft-07/schema#" }
Connections
streamable-http
https://vigia.coredls.cloud/mcp