# Vigía (remote · vigia.coredls.cloud)

Verified, dated facts on npm/PyPI package versions, deprecations, requirements, and AI model prices.

- Trust score: 70/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-28

## Components

- remote · `vigia.coredls.cloud`: 70/100 (this document), [markdown](https://verifymcp.io/servers/cloud-coredls-vigia-vigia/vigia.md), [page](https://verifymcp.io/servers/cloud-coredls-vigia-vigia/vigia)

## Channel facts

- Endpoint: `https://vigia.coredls.cloud/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-28.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 446 tokens (~89/item across 5 items; 5 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 83/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 50% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**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.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http cloud-coredls-vigia-vigia 'https://vigia.coredls.cloud/mcp'
```

### Cursor

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

### VS Code

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

### Codex

```toml
[mcp_servers.cloud-coredls-vigia-vigia]
url = "https://vigia.coredls.cloud/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cloud-coredls-vigia-vigia": {
      "type": "remote",
      "url": "https://vigia.coredls.cloud/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add cloud-coredls-vigia-vigia --url 'https://vigia.coredls.cloud/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  cloud-coredls-vigia-vigia:
    url: "https://vigia.coredls.cloud/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "cloud-coredls-vigia-vigia": {
      "Transport": "http",
      "Url": "https://vigia.coredls.cloud/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add cloud-coredls-vigia-vigia -t streamable-http -u 'https://vigia.coredls.cloud/mcp'
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-28 (score 70)

First indexed and scored.

## MCP tools (5)

### `package_status` (~87 tokens)

Package status

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.

Input parameters:

- `ecosystem` (string, required): Package ecosystem
- `name` (string, required): Exact package name, e.g. "next", "@types/node", "requests"

### `check_dependencies` (~88 tokens)

Check dependencies

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.

Input parameters:

- `ecosystem` (string, required): Package ecosystem
- `manifest` (string, required): Full content of the manifest file

### `recent_changes` (~69 tokens)

Recent changes

Latest detected changes: new releases, deprecations, removed packages, AI model price changes or retirement announcements. Optionally filtered to one package or model.

Input parameters:

- `ecosystem` (string)
- `limit` (integer)
- `name` (string): If set, history of that package or model

### `model_info` (~95 tokens)

AI model info

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.

Input parameters:

- `model_id` (string): Exact ID in provider/model form, e.g. "anthropic/claude-x"
- `provider` (string)
- `query` (string)

### `find_package` (~42 tokens)

Find package

Finds packages or models by name prefix, ordered by popularity. Use when the exact name is unknown.

Input parameters:

- `ecosystem` (string)
- `query` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/cloud-coredls-vigia-vigia/vigia#diagnostics

## Score history

- 2026-09-28: 70

## Common questions

### 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.

## Links

- Remote endpoint: https://vigia.coredls.cloud/mcp
- Website: https://vigia.coredls.cloud/
- Changelog RSS feed: https://verifymcp.io/servers/cloud-coredls-vigia-vigia/vigia.xml
- Changelog JSON feed: https://verifymcp.io/servers/cloud-coredls-vigia-vigia/vigia.json
- HTML version of this page: https://verifymcp.io/servers/cloud-coredls-vigia-vigia/vigia