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

x402-package-advisories

https://x402-package-advisories.microtools-x402.workers.dev

Registry code: 3260b42fbfab728f

api record

Package vuln advisories from OSV.dev: CVEs, severity, fixes, manifest audit. Pay per call via x402.

from a public catalogue that lists it, not from the operator

endpoint
https://x402-package-advisories.microtools-x402.workers.dev/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 x402-package-advisories live?
Partly — its last checks failed now and then (checked 7m ago). It answered 50% of checks over the last 30 days.
Is x402-package-advisories free to use?
Yes — the hub reached it with no key and no payment.
What tools does x402-package-advisories have?
5 tools: manifest_audit, package_advisories, vuln_details, health, ping.
Is x402-package-advisories 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
degraded
uptime, 30 days
50%

90 days 50%· all time 50%

latency
1,069ms

last good check

priced tools
1

of 5 tools

_ answered our checks, 90 days 4 checks · signed record
  • live → degraded· HTTP 500
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts, and USDC settlements on base into the address this listing's priced doors name, read off the chain. Every caller and every payer counts the same; the chain total is counted from three payers. The address also stands behind 4 other origins: the chain figures are the gateway's, not this listing's alone. How it is counted.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

payers on base
1

distinct

settlements
8

last 2026-11-08

received on chain
0.02 USDC

counted from three payers (thin, concentrated, shared-payto)

_ what it can do 5 tools
1 paid1 open 3 never probed 2 of 5 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.

  • ping 0.001 USDC paid never probed

    Paid connectivity test: returns ok and a server timestamp. Use it to check that your x402 payment flow works end to end. Costs $0.001 USDC per call via x402.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 lines
  • health open 32h ago

    Free health check. Returns service status, version, tool prices, network and the plain-HTTP x402 endpoints.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 lines
  • manifest_audit unknown never probed

    Audit up to 50 dependencies in one call (OSV.dev querybatch). Input: items [{ecosystem,name,version}], or packages "npm:[email protected],PyPI:[email protected]", or a manifest: package.json text (dependencies, devDependencies, optionalDependencies; range minimum used) or requirements.txt text (name==version lines). You can also POST the raw package.json or requirements.txt as the body. Returns per-package vulnerable flag, vuln count, max severity, max CVSS v3, recommended upgrade and advisory list (id, CVE, severity, score, summary, fix), plus totals by severity, unique vulns and skipped entries. Vulnerability data from OSV.dev (CC-BY 4.0); package metadata from deps.dev. Bad input and upstream errors are not charged. Costs $0.01 USDC per call via x402.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "items": {
          "type": "array",
          "items": {
            "type": "object",
            "required": [
              "ecosystem",
              "name"
            ],
            "properties": {
              "name": {
                "type": "string",
                "pattern": "^[^\\s]+$",
                "maxLength": 214,
                "minLength": 1
              },
              "version": {
                "type": "string",
                "pattern": "^[^\\s]+$",
                "maxLength": 100,
                "minLength": 1
              },
              "ecosystem": {
                "type": "string",
                "maxLength": 30,
                "minLength": 1,
                "description": "Package ecosystem: npm, PyPI, Go, Maven, crates.io, NuGet, RubyGems, Packagist, Pub, Hex, CRAN, Hackage, SwiftURL, ConanCenter (aliases like pip, cargo, gem, composer accepted)"
              }
            },
            "additionalProperties": false
          },
          "maxItems": 50,
          "minItems": 1,
          "description": "Array of {ecosystem, name, version} (max 50)"
        },
        "manifest": {
          "type": "string",
          "maxLength": 60000,
          "minLength": 2,
          "description": "package.json or requirements.txt text"
        },
        "packages": {
          "type": "string",
          "maxLength": 8000,
          "minLength": 3,
          "description": "Comma list Ecosystem:name@version, e.g. npm:[email protected],PyPI:[email protected]"
        }
      }
    }
    arguments 52 lines
  • package_advisories unknown never probed

    Security advisories for one open-source package version (npm, PyPI, Go, Maven, crates.io, NuGet, RubyGems, Packagist, Pub, Hex...). Returns a verdict (vulnerable yes/no, vuln count, max severity, max CVSS v3 score, counts by severity, recommended upgrade version re-checked against OSV, latest stable version and whether it is affected) plus every advisory: OSV/GHSA id, CVE aliases, summary, severity label, CVSS v3 score (computed from the vector) and v4 vector, affected ranges, fixed versions, the fix for this version, published/modified dates and references. Duplicate records (GHSA vs PYSEC/GO ids with the same CVE) are merged. Also returns the version's licenses, publish date, deprecation and dependency counts from deps.dev. Omit version to check the latest stable release. Vulnerability data from OSV.dev (CC-BY 4.0); package metadata from deps.dev. Unknown packages/versions, bad input and upstream errors are not charged. Costs $0.003 USDC per call via x402.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "ecosystem",
        "name"
      ],
      "properties": {
        "name": {
          "type": "string",
          "pattern": "^[^\\s]+$",
          "maxLength": 214,
          "minLength": 1,
          "description": "Package name, e.g. lodash, django, golang.org/x/net, org.apache.logging.log4j:log4j-core"
        },
        "version": {
          "type": "string",
          "pattern": "^[^\\s]+$",
          "maxLength": 100,
          "minLength": 1,
          "description": "Exact version, e.g. 4.17.15 (default: latest stable)"
        },
        "ecosystem": {
          "type": "string",
          "maxLength": 30,
          "minLength": 1,
          "description": "Package ecosystem: npm, PyPI, Go, Maven, crates.io, NuGet, RubyGems, Packagist, Pub, Hex, CRAN, Hackage, SwiftURL, ConanCenter (aliases like pip, cargo, gem, composer accepted)"
        },
        "include_withdrawn": {
          "type": "boolean",
          "description": "Include withdrawn advisories (default false)"
        }
      }
    }
    arguments 34 lines
  • vuln_details unknown never probed

    Full OSV record for one vulnerability id (GHSA-..., CVE-..., PYSEC-..., GO-..., RUSTSEC-..., OSV-...): details, aliases, related ids, every affected package with ranges and versions, references, credits, database_specific fields, plus a normalized severity label and computed CVSS v3 score. Vulnerability data from OSV.dev (CC-BY 4.0); package metadata from deps.dev. Unknown ids and upstream errors are not charged. Costs $0.001 USDC per call via x402.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "type": "string",
          "pattern": "^[A-Za-z][A-Za-z0-9._:-]{2,80}$",
          "description": "OSV id or CVE alias"
        }
      }
    }
    arguments 14 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 3260b42fbfab728f.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/3260b42fbfab728f/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/3260b42fbfab728f/badge.svg)](https://brick.blue/agent/3260b42fbfab728f?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
90%

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.