mcp-registry/dev.kaneky/depcheck · v0.2.1
As of 2026-10-27 03:38 UTC, the Kaneky Depcheck MCP server is up with a Glimind reliability score of 83/100 (grade B). Over the last 30 days it answered 99.8% of Glimind's liveness checks. It had 6 outages in 90 days, with a median recovery of 8 minutes.
Known vulnerabilities for exact package versions from OSV, with fixes. Paid per call, x402.
Point your MCP client at this streamable-http endpoint: https://depcheck.kaneky.dev/mcp
1 parameter(s) across 1 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
1 of 1 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 1 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fdev.kaneky%2Fdepcheck/fixes
{
"name": "check_packages",
"description": "Look up the known vulnerabilities affecting exact package versions in the public OSV database (npm, PyPI, Go, Maven, crates.io, RubyGems, NuGet, Packagist, Pub, Hex), 1 to 50 packages per call. Per package: every OSV advisory for that version with its id, CVE/GHSA aliases, summary, severity (database label, CVSS vectors, v3 base scores), the versions that fix it or \"no fix published\", published/modified dates and a link. Plus a summary: packages checked, packages vulnerable, total advisories and",
"inputSchema": {
"type": "object",
"required": [
"packages"
],
"properties": {
"packages": {
"type": "array",
"items": {
"type": "object",
"required": [
"ecosystem",
"name",
"version"
],
"properties": {
"name": {
"type": "string",
"maxLength": 214,
"minLength": 1,
"description": "As the ecosystem names it: lodash, requests, github.com/gin-gonic/gin, org.apache.logging.log4j:log4j-core."
},
"version": {
"type": "string",
"maxLength": 128,
"minLength": 1,
"description": "The exact version, not a range."
},
"ecosystem": {
"enum": [
"npm",
"PyPI",
"Go",
"Maven",
"crates.io",
"RubyGems",
"NuGet",
"Packagist",
"Pub",
"Hex"
],
"type": "string",
"description": "OSV's ecosystem name, case-sensitive."
}
}
},
"maxItems": 50,
"minItems": 1
}
}
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/dev.kaneky/depcheck"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/dev.kaneky/depcheck"}) over MCP.
check_packages ~337 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fdev.kaneky%2Fdepcheck?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fdev.kaneky%2Fdepcheck?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fdev.kaneky%2Fdepcheck.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fdev.kaneky%2Fdepcheck.svg :target: https://glimind.com/server/mcp-registry%2Fdev.kaneky%2Fdepcheck?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:a777f96e602c2496…, first seen 2026-10-17, included at leaf 7757 of 77,130. Version history · verify what your client received.
Compare: most reliable security servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-27 03:38 UTC, the Kaneky Depcheck MCP server is up with a Glimind reliability score of 83/100 (grade B). Over the last 30 days it answered 99.8% of Glimind's liveness checks. It had 6 outages in 90 days, with a median recovery of 8 minutes.
Kaneky Depcheck MCP server advertises 1 tool, including check_packages.
Point your MCP client at this streamable-http endpoint: https://depcheck.kaneky.dev/mcp
Glimind scanned all 1 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.