Index / MCP servers / Vigía

Vigía MCP server

Connect Vigía and your agent gets 12 tools, among them changes_since_cutoff, check_dependencies, eol_status. It answers at https://vigia.coredls.cloud/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 4 of 4 times since 28 September 2026; the last check, on 14 November 2026, succeeded.

Status
Answering
Tools
12
Official
yes, served from coredls.cloud
Reliability
4 of 4 checks
Response time
791 ms
Transport
streamable HTTP
Last checked
14 November 2026

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

Description as the publisher wrote it.

The 12 tools Vigía offers

ToolWhat it does
changes_since_cutoffReturns 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 (
Inputs: cutoff, ecosystems, limit
check_dependenciesAudits a whole manifest in one call. For every dependency in a package.json (dependencies and devDependencies) or a requirements.txt it returns the latest version, whether the declared range includes it (up_to_date / outdated / outdated_maj
Inputs: ecosystem, manifest
eol_statusTells whether a language, runtime, framework, database or operating-system version is still supported and when it reaches end of life. Covers about 480 products (Python, Node.js, PHP, Java, Ruby, Go, Rust, Django, Laravel, Rails, React, Ang
Inputs: product, version
find_compatible_versionFinds the newest stable, non-withdrawn version of a package whose own declared requirements admit the runtimes you give it: npm engines and peerDependencies, PyPI Requires-Python, Rust rust-version (minimum Rust), PHP require.php and requir
Inputs: ecosystem, name, with
find_packageSearches 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 ecosystem, name and popularity rank. Read-only and requires no authentication. It match
Inputs: query, ecosystem
list_versionsLists 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 crates.io: yanked; Packagist: abandoned), plus a maintenance summary: last relea
Inputs: ecosystem, name, limit, stable_only
model_statusLooks up AI models in the OpenRouter catalog: price per million input and output tokens in USD, context window, maximum output tokens, knowledge cutoff, supported modalities and announced retirement date, with a status of available / retiri
Inputs: model_id, provider, query
package_statusReturns the current state of one package: latest stable version and its publish date, status (active / deprecated / yanked / not_found_in_registry), the deprecation message if any, runtime requirements (npm engines and peerDependencies, PyP
Inputs: ecosystem, name
recent_changesLists the changes Vigia detected recently, newest first: new package releases (with old and new version), deprecations, yanks and removals, runtime-requirement changes, AI model price changes and model retirement announcements. Each item ha
Inputs: ecosystem, name, limit
symbol_statusChecks 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 declarations. Returns whether it was found, its kind, its exact signature, the m
Inputs: name, symbol, version, module
upgrade_impactReports what changes between two versions of an npm package by diffing the public TypeScript API of both releases (only the type declarations are analyzed; package code is never executed): removed exports and import paths, changed function
Inputs: name, from, to
version_statusReports 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 deprecated, PyPI and crates.io yanked, Packagist abandoned), how many stable rele
Inputs: ecosystem, name, version

Add Vigía to your AI client

Every block below points at https://vigia.coredls.cloud/mcp. Pick your client and copy.

Claude Code: one command in your terminal
claude mcp add --transport http vig-a https://vigia.coredls.cloud/mcp
Claude Desktop: claude_desktop_config.json
{
  "mcpServers": {
    "vig-a": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://vigia.coredls.cloud/mcp"]
    }
  }
}
Cursor: ~/.cursor/mcp.json, or .cursor/mcp.json in a project
{
  "mcpServers": {
    "vig-a": {
      "url": "https://vigia.coredls.cloud/mcp"
    }
  }
}
VS Code and GitHub Copilot: .vscode/mcp.json
{
  "servers": {
    "vig-a": {
      "type": "http",
      "url": "https://vigia.coredls.cloud/mcp"
    }
  }
}
Zed: Zed settings.json
{
  "context_servers": {
    "vig-a": {
      "url": "https://vigia.coredls.cloud/mcp"
    }
  }
}
Windsurf: ~/.codeium/mcp_config.json
{
  "mcpServers": {
    "vig-a": {
      "serverUrl": "https://vigia.coredls.cloud/mcp"
    }
  }
}
JetBrains AI Assistant: Settings, Tools, AI Assistant, MCP, New MCP Server, as JSON
{
  "mcpServers": {
    "vig-a": {
      "url": "https://vigia.coredls.cloud/mcp"
    }
  }
}
Continue: .continue/mcpServers/neuronto.yaml
name: Vigía
version: 0.0.1
schema: v1
mcpServers:
  - name: Vigía
    type: streamable-http
    url: https://vigia.coredls.cloud/mcp
Gemini CLI: ~/.gemini/settings.json
{
  "mcpServers": {
    "vig-a": {
      "httpUrl": "https://vigia.coredls.cloud/mcp"
    }
  }
}
Codex CLI: MCP server config
{
  "mcpServers": {
    "vig-a": {
      "type": "http",
      "url": "https://vigia.coredls.cloud/mcp"
    }
  }
}
Warp: MCP servers, + Add, paste JSON
{
  "mcpServers": {
    "vig-a": {
      "url": "https://vigia.coredls.cloud/mcp"
    }
  }
}
Goose: a one-click extension link
goose://extension?url=https%3A%2F%2Fvigia.coredls.cloud%2Fmcp&type=streamable_http&id=vig-a&name=Vig%C3%ADa

Is Vigía up right now?

It answered our last check on 14 November 2026 in 791 ms. Over 4 checks since 28 September 2026 it answered 4. Status here comes from Neuronto's own probes, not from the publisher.

MCP servers similar to Vigía

Questions about Vigía

Is there an official Vigía MCP server?

Yes. It is published by coredls.cloud and served from vigia.coredls.cloud, the vendor's own domain: https://vigia.coredls.cloud/mcp.

How many tools does Vigía have?

12, as returned by the server's own tools/list on 17 November 2026: changes_since_cutoff, check_dependencies, eol_status, find_compatible_version, find_package, list_versions, model_status, package_status, and 4 more.

Is Vigía down?

It answered our last check on 14 November 2026 in 791 ms. Over 4 checks since 28 September 2026 it answered 4.

How do I add Vigía to Cursor?

Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://vigia.coredls.cloud/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.

Does Vigía need an API key?

It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.

Where this comes from

Publisher: cloud.coredls.vigia. Endpoint host: vigia.coredls.cloud. ARD identifier: urn:air:cloud.coredls.vigia:mcp:vigia. First indexed 28 September 2026. The tools are exactly what the server returned; nothing on this page is inferred from its name. Ranking in Neuronto search is never for sale.

Is this your server? Get a message the day it stops answering or its tools change: monitoring, 14 days free. Or claim the domain to manage how it is listed.