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

com.mcpscores/x402-market-intelligence

https://mcpfax-intel.bowling-anthony.workers.dev

Registry code: 124cf627d0c37f9d

api record

You want to know who is actually earning in the x402 economy, and sellers' own claims are all anyone publishes. These figures are read off Base. TOOL CALLS ARE x402-PAID in USDC on Base: send the base64 X-PAYMENT header on this POST /mcp request, or params._meta['x402/payment']. An unpaid call answers with a valid x402 accepts array and settles nothing, and initialize, ping, tools/list and GET /health are free. WHERE THE NUMBERS COME FROM: USDC revenue figures are read off Base directly, not claimed by the sellers being ranked, and every figure carries the observation window it was computed…

endpoint
https://mcpfax-intel.bowling-anthony.workers.dev/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 com.mcpscores/x402-market-intelligence live?
Yes — it answered the hub's last check (checked 3h ago). It answered 100% of checks over the last 30 days.
Is com.mcpscores/x402-market-intelligence free to use?
No — it charges per call, from 0.005 USDC, quoted in its own 402 answers.
What tools does com.mcpscores/x402-market-intelligence have?
6 tools: x402_seller_rank, x402_category_demand, x402_trending_services, x402_top_movers, x402_market_report, x402_new_entrants.
Is com.mcpscores/x402-market-intelligence 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.7%

90 days 99.4%· all time 99.5%

latency
178ms

last good check

priced tools
6

of 6 tools

_ answered our checks, 90 days 688 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
topic
crypto & onchain onchain analytics
used for
  • rank x402 sellers by on-chain revenue
  • find trending x402 services
  • see demand by service category
takes → gives
text → data
tools
6 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 also stands behind 12 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
15

distinct

settlements
39

last 2026-11-05

received on chain
0.228 USDC

shared-payto

_ what it can do 6 tools
6 paid 6 of 6 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.

  • x402_seller_rank reads paid never probed

    Which x402 sellers actually earn, ranked by USDC read off Base — not by their own claims. Price: $0.01 USDC per successful call.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "default": 25,
      "maximum": 100,
      "minimum": 1,
      "examples": [
        25
      ],
      "description": "Maximum rows to return, 1-100. Defaults to 25."
    },
    "category": {
      "enum": [
        "crypto-defi",
        "market-data",
        "search-research",
        "ai-inference",
        "developer-infrastructure",
        "risk-identity",
        "commerce",
        "automation",
        "communications",
        "other"
      ],
      "type": "string",
      "examples": [
        "crypto-defi"
      ],
      "description": "Optional deterministic category filter."
    }
  },
  "additionalProperties": false
}
    arguments 35 lines
  • x402_category_demand reads 0.005 USDC paid 14h ago

    Where agents are spending and almost nobody is selling — demand against classified supply. Price: $0.005 USDC per successful call.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "category": {
      "enum": [
        "crypto-defi",
        "market-data",
        "search-research",
        "ai-inference",
        "developer-infrastructure",
        "risk-identity",
        "commerce",
        "automation",
        "communications",
        "other"
      ],
      "type": "string",
      "examples": [
        "crypto-defi"
      ],
      "description": "Optional deterministic category filter."
    }
  },
  "additionalProperties": false
}
    arguments 25 lines
  • x402_trending_services reads 0.01 USDC paid 14h ago

    Which x402 services are growing right now, by observed inflow across comparable windows. Price: $0.01 USDC per successful call.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "default": 25,
      "maximum": 100,
      "minimum": 1,
      "examples": [
        25
      ],
      "description": "Maximum rows to return, 1-100. Defaults to 25."
    }
  },
  "additionalProperties": false
}
    arguments 16 lines
  • x402_top_movers reads paid never probed

    Sudden inflow spikes and first-seen large payers, before they show up in a ranking. Price: $0.01 USDC per successful call.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "default": 25,
      "maximum": 100,
      "minimum": 1,
      "examples": [
        25
      ],
      "description": "Maximum rows to return, 1-100. Defaults to 25."
    }
  },
  "additionalProperties": false
}
    arguments 16 lines
  • x402_market_report reads 0.01 USDC paid 14h ago

    Daily state of the x402 agent economy: observed USDC inflow, seller ranking, category demand, growth, and coverage. Reports its real observation window; concentration adjustment applied only when scan coverage supports it. A FREE register-wide change digest covering the same domain is market_digest on the x402-observatory gateway; buy this for the derived figures, not for what merely changed. Price: $0.01 USDC per successful call.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • x402_new_entrants reads 0.01 USDC paid 3h ago

    x402 services first listed since a given date, with first archive observation and early-traction evidence from observed inflow. Entrants MCPFax can attribute — a declared payTo, an observed title, or observed inflow — rank first, and each row says which it carries. A window identifying nobody is refused 422 and charges nothing. Requests before the archive's first date are partially covered. Price: $0.01 USDC per successful call.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "default": 25,
      "maximum": 100,
      "minimum": 1,
      "examples": [
        25
      ],
      "description": "Maximum rows to return, 1-100. Defaults to 25."
    },
    "since": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "examples": [
        "2026-08-28"
      ],
      "description": "UTC date, YYYY-MM-DD; defaults to 7 days ago."
    }
  },
  "additionalProperties": false
}
    arguments 24 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 124cf627d0c37f9d.

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

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.