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

deal-radar-x402

https://deal-radar-x402-sfredx-1715.vercel.app

Registry code: b4b6dbd86c5e7d8c

api record
endpoint
https://deal-radar-x402-sfredx-1715.vercel.app/mcp
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 deal-radar-x402 live?
Yes — it answered the hub's last check (checked 3h ago). It answered 100% of checks over the last 30 days.
Is deal-radar-x402 free to use?
Not measured yet.
What tools does deal-radar-x402 have?
3 tools: ping, formd_leads, deal_events_8k.
Is deal-radar-x402 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
280ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 1 checks · signed record
  • 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 3 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
5

last 2026-10-24

received on chain
4.275 USDC

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

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

  • ping unknown never probed

    Free health check. Does not spend USDC.

    mcp-tool

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

    Recent SEC Form D private-placement filings parsed into scored leads (0-100 with reasons): issuer, raise size, amount sold, % sold, investors, exemptions, executives, placement agent / broker-dealer with CRD, fund vs operating company, and the sec.gov filing link. Up to 25 leads per call. Optional date-range backfill of up to 31 days. Costs $0.015 USDC.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "scan": {
          "type": "string",
          "description": "Filings scanned before filtering, 5-60, default 40."
        },
        "limit": {
          "type": "string",
          "description": "Leads returned, 1-25, default 10."
        },
        "states": {
          "type": "string",
          "description": "Comma-separated issuer state codes, e.g. NY,CA."
        },
        "endDate": {
          "type": "string",
          "description": "YYYY-MM-DD, default today when startDate is set."
        },
        "minScore": {
          "type": "string",
          "description": "Minimum lead score 0-100."
        },
        "minAmount": {
          "type": "string",
          "description": "Minimum raise in USD (amount sold, else offering size)."
        },
        "startDate": {
          "type": "string",
          "description": "YYYY-MM-DD. With endDate, backfills that filing-date window via EDGAR full-text search (max 31 days). Omit both for the newest filings."
        },
        "industries": {
          "type": "string",
          "description": "Comma-separated exact Form D industry groups, e.g. Biotechnology."
        },
        "excludeFunds": {
          "type": "string",
          "description": "true to drop pooled investment funds."
        },
        "excludeAmendments": {
          "type": "string",
          "description": "true to drop D/A amendments."
        },
        "placementAgentOnly": {
          "type": "string",
          "description": "true to keep only raises with a placement agent."
        }
      },
      "additionalProperties": false
    }
    arguments 51 lines
  • deal_events_8k unknown never probed

    Public-company 8-K filings filtered to deal items: 1.01 material agreement, 2.01 completed acquisition/disposition, 2.03 new debt, 3.02 unregistered equity sale, 5.01 change in control (or any items you pass). Company, filing date, all item labels, location, SIC and the sec.gov link. Up to 50 events per call, date windows up to 31 days. Costs $0.01 USDC.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "items": {
          "type": "string",
          "description": "Comma-separated 8-K item codes, default 1.01,2.01,2.03,3.02,5.01."
        },
        "limit": {
          "type": "string",
          "description": "Events returned, 1-50, default 25."
        },
        "endDate": {
          "type": "string",
          "description": "YYYY-MM-DD, default today."
        },
        "startDate": {
          "type": "string",
          "description": "YYYY-MM-DD, default yesterday."
        }
      },
      "additionalProperties": false
    }
    arguments 23 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 b4b6dbd86c5e7d8c.

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