MCP servercloud.coredls.vigia/vigia

What breaks between versions, per-version vulnerabilities, compatible versions: npm/PyPI facts.

UNRATEDActivestreamable-httpvigia.coredls.cloud

Overview

Score?

UNRATED 0.106

of what a free look can see, on 7 looks

Looks

last 8 hr ago

Tools

changed 2 days ago

More info

URL

vigia.coredls.cloud/mcp

streamable-http

Says it is

vigia 0.3.0

protocol 2025-06-18

In the record since

5 days ago

Among servers18,413 with a card

0median 0.606 · this server 0.106 · highest on record 0.8561

Toolsfrom sha256:b9a493f3a9…ad5c1c · +3 −0 2 days ago

The tools this server lists, read out of the definition it returned
Tool	Schema
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 / outd	input · no output
find_compatible_version added Finds the newest stable version of an npm or PyPI package that works with the given runtime/peer versions, using the engines, peerDependencies or Requires-Python declared by EACH v	input · no output
find_package Finds packages or models by name prefix, ordered by popularity. Use when the exact name is unknown.	input · no output
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	input · no output
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	input · no output
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 · no output
symbol_status added Checks whether an exported function/class/type (or Class.member) exists in a specific version of an npm package, its exact signature, which module path to import it from, and wheth	input · no output
upgrade_impact added What changes when upgrading an npm package from one version to another: removed exports and modules, changed function signatures and class members, newly deprecated APIs, changed e	input · no output
version_status For one exact version of an npm or PyPI package: whether it exists, when it was published, whether it was deprecated/yanked, how far behind latest it is, its known vulnerabilities	input · no output

Verify it yourselfnpx teppi-check https://vigia.coredls.cloud/mcpcurl -s https://api.teppi.xyz/v1/trust/mcp/mcs_01M3NW5D4E91VE3KCZHQ7N843T