_ registry / mcp http-sse · checked 17m ago

dephealth

https://dephealth.dsh.sh

Registry code: f7e2f6c4f21a8541

api record

Package alive? Verdict with evidence: deprecated, archived, stale or active; plus runtime EOL dates. Use when: Before pinning, upgrading or auditing a dependency: package_health returns whether it is deprecated, archived, stale or active with the raw registry evidence, advisories for the version you use and the replacement if there is one; deps_audit does the same for a whole manifest; runtime_eol says whether a Node, Python, OS or database version is still supported and when it dies. Not for: Not a vulnerability scanner (advisory ids only, no CVSS triage or reachability), not license…

endpoint
https://dephealth.dsh.sh/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is dephealth live?
Yes — it answered the hub's last check (checked 17m ago). It answered 99% of checks over the last 30 days.
Is dephealth free to use?
Yes — the hub reached it with no key and no payment.
What tools does dephealth have?
3 tools: package_health, runtime_eol, deps_audit.
Is dephealth safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.4%

90 days 99.3%· all time 99.3%

latency
1,013ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 278 checks · signed record
  • degraded → live
  • live → degraded· HTTP 502
  • down → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
used for
  • check if a package is deprecated or stale
  • audit all dependencies in a manifest
  • check runtime end-of-life dates
takes → gives
text, code → data
tools
3 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 3 tools
3 never probed 0 of 3 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • package_health reads unknown 17m ago

    Is this package alive? One verdict — deprecated, archived, stale, active or unknown — with the evidence: per-version deprecation from the native registry, yanked/retracted latest release, repository archived and last-push dates, maintainer and dependent counts, advisory ids for the exact version, and what replaced it. Use when choosing, pinning or upgrading a dependency in npm, PyPI, crates.io, RubyGems, Go, Maven, NuGet or Packagist.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "ecosystem",
        "name",
        "task_context"
      ],
      "properties": {
        "name": {
          "type": "string",
          "maxLength": 200,
          "minLength": 1,
          "description": "Package name as the registry spells it: \"@scope/name\", \"requests\", \"serde\", \"rails\", \"github.com/gorilla/mux\", \"org.apache.commons:commons-lang3\", \"Newtonsoft.Json\", \"monolog/monolog\""
        },
        "version": {
          "type": "string",
          "maxLength": 80,
          "description": "The exact version you use or intend to pin; enables per-version advisories and deprecation. Omit for the latest."
        },
        "ecosystem": {
          "enum": [
            "npm",
            "pypi",
            "cargo",
            "rubygems",
            "go",
            "maven",
            "nuget",
            "packagist"
          ],
          "type": "string",
          "description": "npm | pypi | cargo (crates.io) | rubygems | go (module path) | maven (group:artifact) | nuget | packagist (vendor/package)"
        },
        "task_context": {
          "type": "string",
          "maxLength": 500,
          "minLength": 1,
          "description": "One sentence on what the user is ultimately trying to do (the task this call serves). Required; it tunes the result and is how this free service learns what agents need."
        }
      }
    }
    arguments 42 lines
  • runtime_eol reads unknown never probed

    Support and end-of-life dates for a runtime, OS, database or framework version from endoflife.date (470+ products): each cycle with a verdict — supported, security-only or eol — the latest patch, LTS flag and days to EOL. Use when deciding which Node, Python, Ubuntu, PostgreSQL, Java, Django… version to target or whether a deployed one is still safe.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "product",
        "task_context"
      ],
      "properties": {
        "cycle": {
          "type": "string",
          "maxLength": 30,
          "description": "One release cycle to report, e.g. \"22\" for Node 22, \"3.12\" for Python, \"24.04\" for Ubuntu. Omit for every cycle."
        },
        "product": {
          "type": "string",
          "maxLength": 60,
          "minLength": 1,
          "description": "endoflife.date product name or alias: \"nodejs\" (or \"node\"), \"python\", \"ubuntu\", \"postgresql\", \"django\", \"java\", \"rails\", \"go\", \"php\", \"redis\""
        },
        "task_context": {
          "type": "string",
          "maxLength": 500,
          "minLength": 1,
          "description": "One sentence on what the user is ultimately trying to do (the task this call serves). Required; it tunes the result and is how this free service learns what agents need."
        }
      }
    }
    arguments 27 lines
  • deps_audit reads unknown 17m ago

    Health verdict for every package in a manifest or a list, in one call (≤25 packages): deprecated / archived / stale / active / unknown per package with the latest version, release and push ages, advisory counts and replacements, plus a summary. Use when reviewing a repository's package.json or requirements.txt before an upgrade, an audit or a fork decision.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "task_context"
      ],
      "properties": {
        "manifest": {
          "type": "string",
          "maxLength": 60000,
          "description": "Raw package.json (dependencies, devDependencies, peer, optional) or requirements.txt text; other formats are reported as unparsed."
        },
        "packages": {
          "type": "array",
          "items": {
            "type": "object",
            "required": [
              "ecosystem",
              "name"
            ],
            "properties": {
              "name": {
                "type": "string",
                "maxLength": 200,
                "minLength": 1,
                "description": "Package name as the registry spells it: \"@scope/name\", \"requests\", \"serde\", \"rails\", \"github.com/gorilla/mux\", \"org.apache.commons:commons-lang3\", \"Newtonsoft.Json\", \"monolog/monolog\""
              },
              "version": {
                "type": "string",
                "maxLength": 80
              },
              "ecosystem": {
                "enum": [
                  "npm",
                  "pypi",
                  "cargo",
                  "rubygems",
                  "go",
                  "maven",
                  "nuget",
                  "packagist"
                ],
                "type": "string",
                "description": "npm | pypi | cargo (crates.io) | rubygems | go (module path) | maven (group:artifact) | nuget | packagist (vendor/package)"
              }
            }
          },
          "maxItems": 25,
          "description": "Explicit list of packages; combine with or instead of `manifest`."
        },
        "task_context": {
          "type": "string",
          "maxLength": 500,
          "minLength": 1,
          "description": "One sentence on what the user is ultimately trying to do (the task this call serves). Required; it tunes the result and is how this free service learns what agents need."
        },
        "manifest_kind": {
          "enum": [
            "auto",
            "package.json",
            "requirements.txt"
          ],
          "type": "string",
          "default": "auto"
        }
      }
    }
    arguments 67 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id f7e2f6c4f21a8541.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/f7e2f6c4f21a8541/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/f7e2f6c4f21a8541/badge.svg)](https://brick.blue/agent/f7e2f6c4f21a8541?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
70%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.

_ also on dsh.sh 4 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.