_ registry / mcp + a2a streamable-http · checked 2h ago

markedet-package-check

https://package-check-qy40.onrender.com

Registry code: dc21ccf7360b8cd5

api record

Call selftest (free) to verify the check, then check_packages on package names before you install them. $0.002 USDC per package on Base via x402.

endpoint
https://package-check-qy40.onrender.com/mcp
door code
3b7db9de7241eb2a
protocol
streamable-http ·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 markedet-package-check live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is markedet-package-check free to use?
Yes — the hub reached it with no key and no payment.
What tools does markedet-package-check have?
2 tools: check_packages, selftest.
Is markedet-package-check 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
100%

90 days 100%· all time 100%

latency
362ms

last good check

priced tools
0

of 2 tools

_ answered our checks, 90 days 4 checks · signed record
  • unknown → live
  • unknown → live
_ 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
1

through this hub

calls served
1

successful

paid through this hub
0 USDC

what callers paid

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

  • selftest open 29h ago

    Free. Replays the published known-answer set v1 (11 cases) against the live registries and returns score and sha256, so you can verify the check before paying.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "details": {
          "type": "boolean",
          "default": false
        }
      }
    }
    arguments 9 lines
  • check_packages unknown 29h ago

    Before your agent runs pip install or npm install, check a package list or a whole lockfile (requirements.txt, poetry.lock, uv.lock, Pipfile.lock, package-lock.json, pnpm-lock.yaml, yarn.lock; one verdict per unique package, with line numbers where the format has them). Per package: does it exist, age, releases, downloads, known vulnerabilities (OSV) for the given or latest version, typosquat and slopsquat signals, install scripts; verdict ok, caution or block with reasons. PyPI and npm. A clean ok is not a guarantee. Costs $0.002 USDC per package on Base via x402: the first call without payment returns the payment requirements; pay with an x402-capable MCP client (_meta['x402/payment']) or call POST https://package-check-qy40.onrender.com/check over HTTP x402. Free trial: the first 50 packages per payer wallet are free; sign as usual, the server verifies the signature and does not settle; the result shows free_trial_remaining. About 50: the counter is in memory and resets on restart.

    mcp-tool

    {
      "type": "object",
      "anyOf": [
        {
          "required": [
            "packages"
          ]
        },
        {
          "required": [
            "lockfile"
          ]
        }
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "maximum": 500,
          "minimum": 1,
          "description": "lockfile only: check just the first N unique packages (in file order), e.g. 50 for the free trial"
        },
        "lockfile": {
          "type": "string",
          "description": "raw content of requirements.txt, poetry.lock, uv.lock, Pipfile.lock, package-lock.json, pnpm-lock.yaml or yarn.lock; parsed to unique packages"
        },
        "packages": {
          "type": "array",
          "items": {
            "type": "object",
            "required": [
              "ecosystem",
              "name"
            ],
            "properties": {
              "name": {
                "type": "string",
                "maxLength": 214
              },
              "version": {
                "type": "string",
                "description": "exact version; omitted = latest"
              },
              "ecosystem": {
                "enum": [
                  "pypi",
                  "npm"
                ],
                "type": "string"
              }
            }
          },
          "maxItems": 500,
          "minItems": 1
        },
        "include_dev": {
          "type": "boolean",
          "default": true,
          "description": "lockfile only: false drops packages marked dev"
        },
        "lockfile_format": {
          "enum": [
            "requirements.txt",
            "poetry.lock",
            "uv.lock",
            "Pipfile.lock",
            "package-lock.json",
            "pnpm-lock.yaml",
            "yarn.lock"
          ],
          "type": "string",
          "description": "optional; auto-detected from the content"
        }
      },
      "description": "packages (list) or lockfile (raw text), 1 to 500 unique packages. Price: $0.002 per unique package, paid with x402 (USDC on Base). First 50 packages per payer wallet free."
    }
    arguments 75 lines
_ try it over mcp 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 dc21ccf7360b8cd5.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/dc21ccf7360b8cd5/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/dc21ccf7360b8cd5/badge.svg)](https://brick.blue/agent/dc21ccf7360b8cd5?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 knowoff the mcp door
card completeness
60%

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
1
ok
1
failed
0
success rate
100%
median latency
90ms
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
—

1 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.