tolla-network
Registry code: 96d020c09eef84cf
Read-only data from TOLLA Network, an x402 and MPP toll network for AI agents on Robinhood Chain (USDG). Search paid x402 APIs (lanes), read market numbers from the public x402 Bazaar index, list TOLLA booths and their prices, open receipts, and read TOLLA's own stats and uptime. This server cannot pay. To pay a booth, run TOLLA Pass (a local wallet with spend caps) on your own machine. Stats split team activity from outside activity: report them that way.
- endpoint
- https://tolla.network/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 tolla-network live?
- Yes — it answered the hub's last check (checked 13h ago). It answered 100% of checks over the last 30 days.
- Is tolla-network free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does tolla-network have?
- 8 tools: search_lanes, get_receipt, x402_market_scan, lane_report_host, lookup_agent, list_booths, network_stats, network_status.
- Is tolla-network 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.
90 days 100%· all time 100%
last good check
of 8 tools
- unknown → live
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.
through this hub
successful
what callers paid
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.
list_booths open 13h ago
Every open TOLLA booth: name, what it returns, price in USDG, method, payee and the URL to call (x402 or MPP on Robinhood Chain). Booths run by TOLLA say so.
{ "type": "object", "properties": {}, "additionalProperties": false }arguments 5 linesnetwork_stats open 13h ago
TOLLA's own counts: open booths, settled and not-charged tolls, paying wallets. Team activity (wallets TOLLA lists) is kept apart from outside activity; always report the two separately.
{ "type": "object", "properties": {}, "additionalProperties": false }arguments 5 linesnetwork_status open 13h ago
Live health of TOLLA: the API, the booth gateway, both x402 facilitators, the Robinhood Chain RPC and the x402 index, checked every 5 minutes, with 24 h and 7 day uptime.
{ "type": "object", "properties": {}, "additionalProperties": false }arguments 5 linessearch_lanes unknown never probed
Search paid x402 APIs (lanes) by keyword: TOLLA booths first, then the public x402 Bazaar index. Returns URL, price in USD, networks, paying wallets and calls over 30 days, and whether TOLLA Pass can pay it (Robinhood Chain only). Leave query empty for the most-paid lanes.
{ "type": "object", "properties": { "limit": { "type": "integer", "default": 15, "maximum": 50, "minimum": 1 }, "query": { "type": "string", "description": "Keyword, 2+ characters, e.g. weather, search, price feed." } }, "additionalProperties": false }arguments 16 linesget_receipt unknown never probed
One TOLLA toll receipt by id (24 hex characters): booth, payer and payee, amount in USDG, the API's status code, settlement transaction and explorer link. Status not_charged means nothing settled.
{ "type": "object", "required": [ "receipt" ], "properties": { "receipt": { "type": "string", "description": "Receipt id, or a tolla.network/r/<id> link." } }, "additionalProperties": false }arguments 13 linesx402_market_scan unknown never probed
Numbers for the 500 most active x402 APIs in the public Bazaar index: total listings, paid calls and payer/API pairs over 30 days, median price, how many lanes are concentrated (few wallets, many calls each) and lanes per network.
{ "type": "object", "properties": {}, "additionalProperties": false }arguments 5 lineslane_report_host unknown never probed
Free check of one host against the public x402 Bazaar index: its listings with price, networks, paying wallets and calls over 30 days. Pass a host (api.example.com) or a full URL.
{ "type": "object", "required": [ "host" ], "properties": { "host": { "type": "string", "description": "Host or URL, e.g. api.example.com" } }, "additionalProperties": false }arguments 13 lineslookup_agent unknown never probed
Look up AI agents in the ERC-8004 identity registry on Robinhood Chain by agent id, owner address or name.
{ "type": "object", "required": [ "query" ], "properties": { "query": { "type": "string", "description": "Agent id (number), owner 0x address, or part of a name or host." } }, "additionalProperties": false }arguments 13 lines
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.
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.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - 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. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id96d020c09eef84cf.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/96d020c09eef84cf/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/96d020c09eef84cf?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.
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.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- 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.