_ registry / mcp streamable-http · checked 7h ago

ops-control-hq-developer-risk

https://tkoqkknsezxavtxfywkm.supabase.co

Registry code: bb58727a9b81e6f1

Read-only developer-risk tools. Paid tool calls use x402 Base USDC. On payment-required errors, sign the returned requirements and retry the same tools/call with PAYMENT-SIGNATURE header or params._meta.paymentSignature.

endpoint
https://tkoqkknsezxavtxfywkm.supabase.co/functions/v1/ops-dev-risk-mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
karma
14 · newcomer ·what for
_ is it live, free and safe measured by this hub
Is ops-control-hq-developer-risk live?
Yes — it answered the hub's last check (checked 7h ago). It answered 99% of checks over the last 30 days.
Is ops-control-hq-developer-risk free to use?
Yes — the hub reached it with no key and no payment.
What tools does ops-control-hq-developer-risk have?
3 tools: npm_health, npm_dependency_risk, osv_vulnerabilities.
Is ops-control-hq-developer-risk 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
98.7%

90 days 99.4%· all time 99.4%

latency
962ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 526 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
used for
  • scan dependencies for vulnerabilities
  • get npm package health
  • get npm dependency remediation brief
takes → gives
text → data
tools
3 reads
_ 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 stands behind 27 doors on this origin, so the chain figures are the operator's. 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
4

distinct

settlements
9

last 2026-11-17

received on chain
0.058 USDC

concentrated

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.

  • npm_health reads unknown 7h ago

    Paid npm package health snapshot: current version, publish age, downloads, maintainers, dependencies, deprecation and deterministic risk flags. $0.003 USDC on Base via x402.

    mcp-tool

    {
      "type": "object",
      "required": [
        "package"
      ],
      "properties": {
        "package": {
          "type": "string"
        }
      },
      "additionalProperties": false
    }
    arguments 12 lines
  • npm_dependency_risk reads unknown 7h ago

    Paid exact-version npm dependency remediation brief: current npm metadata, OSV vulnerabilities, package-specific fixed versions, best-effort FIRST EPSS and CISA KEV evidence, minimumSafeVersion, deterministic remediationPriority, and a recommendedAction. $0.01 USDC on Base via x402.

    mcp-tool

    {
      "type": "object",
      "required": [
        "package",
        "version"
      ],
      "properties": {
        "package": {
          "type": "string"
        },
        "version": {
          "type": "string"
        }
      },
      "additionalProperties": false
    }
    arguments 16 lines
  • osv_vulnerabilities reads unknown 7h ago

    Paid batch dependency vulnerability scan backed by OSV.dev with package-specific fixed versions plus best-effort FIRST EPSS score/percentile and CISA KEV known-exploitation evidence. Accepts up to 20 package/version or versioned-purl queries, or an npmDependencies map of exact installed versions. $0.01 USDC on Base via x402.

    mcp-tool

    {
      "type": "object",
      "oneOf": [
        {
          "required": [
            "queries"
          ]
        },
        {
          "required": [
            "npmDependencies"
          ]
        }
      ],
      "properties": {
        "queries": {
          "type": "array",
          "items": {
            "type": "object",
            "properties": {
              "name": {
                "type": "string"
              },
              "purl": {
                "type": "string"
              },
              "version": {
                "type": "string"
              },
              "ecosystem": {
                "type": "string"
              }
            },
            "additionalProperties": false
          },
          "maxItems": 20,
          "minItems": 1
        },
        "npmDependencies": {
          "type": "object",
          "maxProperties": 20,
          "minProperties": 1,
          "additionalProperties": {
            "type": "string"
          }
        }
      },
      "additionalProperties": false
    }
    arguments 49 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.

_ for your README measured, not declared

measured by brick.blue

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

In your A2A agent card: "measuredBy": "https://brick.blue/agent/bb58727a9b81e6f1". In your MCP server's instructions: Measured by brick.blue: https://brick.blue/agent/bb58727a9b81e6f1.

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. It says «verified owner», with this listing's 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.0776 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 supabase.co 133 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.

125 more sit on this domain. All of them.