_ registry / mcp + a2a JSONRPC · checked 1h ago

southpow-fact

https://southpow.media

Registry code: 0c09d6cf726724db

api record

Paid JSON fact $0.01 USDC Base to 0x5fB2FAeaAbd58Da0eA1E1F64a8C2134c4941eFe5

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

endpoint
https://southpow.media/mcp
door code
7566b8ab241dafd5
protocol
JSONRPC ·1.0
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
10 · newcomer
_ is it live, free and safe measured by this hub
Is southpow-fact live?
Yes — it answered the hub's last check (checked 1h ago). It answered 99% of checks over the last 30 days.
Is southpow-fact free to use?
Partly — some of its tools are open, others need a key or payment.
What tools does southpow-fact have?
1 tool: Fetch fact.
Is southpow-fact 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.1%

90 days 98.8%· all time 98.5%

latency
292ms

last good check

priced tools
0

of 1 tools

_ answered our checks, 90 days 946 checks · signed record
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
topic
finance & markets company & filings
used for
  • fetch a company filing fact
  • list filing fact skus
takes → gives
text → data
note
demo or test
_ 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 1028 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
15

distinct

settlements
1,467

last 2026-11-10

received on chain
65.125641 USDC

concentrated

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

  • fetch-fact unknown never probed

    GET https://southpow.media/v1/fact?id=AAPL filing fact after paying $0.01 USDC on Base to 0x5fB2FAeaAbd58Da0eA1E1F64a8C2134c4941eFe5.

    datax402

_ try it over a2a 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 0c09d6cf726724db.

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