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

orbit-web

https://orbit-web.orbit-builder.workers.dev

Registry code: 5ececb542b1bef31

api record

Web utilities for agents, computed live at call time: URL health/redirect/x402 check, web page to Markdown (robots.txt honoured), DNS lookup with SPF/DMARC, email address validation (MX, disposable, role, typo), HTTP security-header audit and AI-agent readiness audit (llms.txt, AI crawler rules, x402, MCP, OpenAPI). $0.001 per call.

endpoint
https://orbit-web.orbit-builder.workers.dev/mcp
door code
d7e47ca600a1ed01
protocol
JSONRPC ·0.3
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 orbit-web live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is orbit-web free to use?
Yes — the hub reached it with no key and no payment.
What tools does orbit-web have?
6 tools: Web page to Markdown ($0.001 via x402), DNS lookup ($0.001 via x402), Email address check ($0.001 via x402), HTTP security headers audit ($0.001 via x402), AI-agent readiness audit ($0.001 via x402), URL health check ($0.001 via x402).
Is orbit-web 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
116ms

last good check

priced tools
1

of 6 tools

_ answered our checks, 90 days 2 checks · signed record
  • unknown → live
  • 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 2 other origins: the chain figures are the gateway's, not this listing's alone. How it is counted.

accounts
1

through this hub

calls served
1

successful

paid through this hub
0 USDC

what callers paid

payers on base
2

distinct

settlements
2

last 2026-10-23

received on chain
0.0018 USDC

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

_ what it can do 6 tools
1 paid 5 never probed 1 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.

  • url_check 0.001 USDC paid never probed

    Is a URL up? Live GET from Cloudflare's edge: final HTTP status, every redirect hop with status and latency, total ms, content-type/length, server, TLS, and if it answers 402 the decoded x402 payment terms (version, network, amount, payTo, bazaar). Unreachable host is still a delivered verdict (up:false).

    uptimeurlhttp statuslatencyx402

  • page_markdown unknown never probed

    Fetch a public web page and return LLM-ready Markdown: title, meta description, canonical, language, main content (scripts/nav/footer stripped, headings/lists/links kept), first 50 absolute links, word count. Honours robots.txt (disallowed → 403, not charged). No JS rendering; non-HTML → 415. max_chars 500-50000 (default 20000).

    scrapemarkdownweb pagereaderllm-ready

  • dns_lookup unknown never probed

    Live DNS records for a domain via DNS-over-HTTPS (1.1.1.1): A, AAAA, CNAME, MX, NS, TXT, CAA, SOA, or type=ALL for all of them plus parsed SPF and DMARC policy. Returns rcode (NOERROR/NXDOMAIN), records with TTL, DNSSEC AD flag.

    dnsmxtxtspfdmarcdomain

  • email_check unknown never probed

    Validate an email address without sending mail: RFC syntax, domain MX (falls back to A), null-MX, disposable-domain list, role account (info@, support@…), free provider, typo suggestion (gmial.com → gmail.com), SPF/DMARC presence, and a verdict valid/risky/invalid with reasons. Does not probe the mailbox.

    emailvalidationmxdisposabledeliverability

  • security_headers unknown never probed

    Audit a site's HTTP security headers live: HSTS (max-age, preload), CSP (unsafe-inline/eval flags), X-Frame-Options/frame-ancestors, X-Content-Type-Options, Referrer-Policy, Permissions-Policy, COOP/CORP, cookie Secure/HttpOnly/SameSite flags, server/version leaks, HTTPS redirect. Score 0-100, grade A+-F, list of fixes.

    security headerscsphstsauditwebsite

  • agent_readiness unknown never probed

    How ready is a website for AI agents? Live checks of /llms.txt, robots.txt rules for 12 AI crawlers (GPTBot, ClaudeBot, PerplexityBot, Google-Extended, CCBot…), sitemap.xml, /.well-known/x402 and x402 402 answer, /openapi.json, MCP (/mcp, /.well-known/mcp.json), A2A agent card, security.txt. Score 0-100 with findings.

    llms.txtrobots.txtai crawlersx402mcpopenapi

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

Every step, filled in for this listing: https://brick.blue/api/v1/agents/5ececb542b1bef31/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/5ececb542b1bef31/badge.svg)](https://brick.blue/agent/5ececb542b1bef31?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
3
ok
1
failed
2
success rate
33%
median latency
92ms
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
—

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