# Coredls Vigia Vigia MCP server

Source: https://glimind.com/server/mcp-registry%2Fcloud.coredls.vigia%2Fvigia
Registry id: `mcp-registry/cloud.coredls.vigia/vigia`
Status: live (checked 2026-10-27T06:19:13.700Z)

## Verdict

Coredls Vigia Vigia MCP server answered 99.61% of Glimind's liveness checks over 30 days, better than 18% of MCP servers, with 834 ms median handshake and 10 outages in 90 days. Its agent-readiness grade is A (92/100) across 12 tools, costing an agent about 4,235 tokens to load. Checked every few minutes; no tool is ever called.

## Measurements (30 days)

| Metric | Value | Better than |
|---|---|---|
| Uptime, 30 days | 99.61% | 18% of MCP servers |
| Median handshake latency | 834 ms | 25% of MCP servers |
| p95 handshake latency | 3614 ms | — |
| Checks in 30 days | 4,898 | — |
| Outages, 90 days | 10 | — |
| Median recovery | 7 min | — |
| Agent-readiness score | 92/100 (A) | 72% of MCP servers |
| Tools | 12 | — |
| Tool-list size for an agent | ~4,235 tokens | 40% of MCP servers |
| Days observed | 28 | — |

## Install

```json
{
  "mcpServers": {
    "coredls-vigia-vigia-mcp-server": {
      "type": "http",
      "url": "https://vigia.coredls.cloud/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http coredls-vigia-vigia-mcp-server https://vigia.coredls.cloud/mcp
```

## Tools (12)

- `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,
- `check_dependencies`: Audits a whole manifest in one call. For every dependency in a package.json (dependencies and devDependencies) or a requirements.txt it returns the latest versi
- `eol_status`: Tells whether a language, runtime, framework, database or operating-system version is still supported and when it reaches end of life. Covers about 480 products
- `find_compatible_version`: Finds the newest stable, non-withdrawn version of a package whose own declared requirements admit the runtimes you give it: npm engines and peerDependencies, Py
- `find_package`: Searches the catalog of tracked packages and AI models by case-insensitive name prefix and returns up to 15 matches ordered by popularity, each with its ecosyst
- `list_versions`: Lists the published versions of one package, newest first, each with its publish date, a prerelease flag and whether it is withdrawn (npm: deprecated; PyPI and 
- `model_status`: Looks up AI models in the OpenRouter catalog: price per million input and output tokens in USD, context window, maximum output tokens, knowledge cutoff, support
- `package_status`: Returns the current state of one package: latest stable version and its publish date, status (active / deprecated / yanked / not_found_in_registry), the depreca
- `recent_changes`: Lists the changes Vigia detected recently, newest first: new package releases (with old and new version), deprecations, yanks and removals, runtime-requirement 
- `symbol_status`: Checks whether an exported function, class, type or constant (or a Class.member) exists in a specific version of an npm package, using the package's TypeScript 
- `upgrade_impact`: Reports what changes between two versions of an npm package by diffing the public TypeScript API of both releases (only the type declarations are analyzed; pack
- `version_status`: Reports on one exact version of an npm, PyPI, crates.io or Packagist package: whether that version exists, when it was published, whether it is withdrawn (npm d

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.