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

mgo-gas-optimizer

https://api.mgo.chain-ops.xyz

Registry code: 4bedf7af7692f82a

api record

Compare live gas across up to 9 EVM chains and get the cheapest one. x402 pay-per-call on Base.

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

endpoint
https://api.mgo.chain-ops.xyz/
door code
b8472572a3c00428
protocol
JSONRPC ·0.2
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 mgo-gas-optimizer live?
Yes — it answered the hub's last check (checked 21h ago). It answered 99% of checks over the last 30 days.
Is mgo-gas-optimizer free to use?
Yes — the hub reached it with no key and no payment.
What tools does mgo-gas-optimizer have?
1 tool: EVM Gas Price Comparison.
Is mgo-gas-optimizer 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.3%

90 days 99.2%· all time 98.9%

latency
227ms

last good check

priced tools
0

of 1 tools

_ answered our checks, 90 days 1221 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
topic
crypto & onchain prices & market data
used for
  • compare gas prices across evm chains
  • find the cheapest evm chain to transact
takes → gives
data → data
_ 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 2 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
6

distinct

settlements
11

last 2026-11-04

received on chain
0.011 USDC

no flags

inferred, not observed

Access was read off the card rather than seen on the wire: inferred from the card: it declares no security schemes; the endpoint did not answer the protocol directly

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

  • gas-comparison unknown never probed

    Compare gas prices across EVM chains and find the cheapest option

    gasevmoptimizationdefitrading

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

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

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
1
ok
0
failed
1
success rate
0%
median latency
203ms
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
—

1 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 chain-ops.xyz 1 entry

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.