linkheft-api
https://linkheft-api.cybermax-tools.workers.dev
Registry code: e5670126216edbfd
Linkheft scores how authoritative websites are from open web-graph data. domain_authority takes up to 50 domains, URLs or emails and returns a 0-100 authority score, web-graph rank, trend and Majestic Million links per domain, with found true/false. dataset_info says which data release answers come from.
- endpoint
- https://linkheft-api.cybermax-tools.workers.dev/mcp?via=mcp-registry
- door code
- d9c4033afa84e0e3
- 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 linkheft-api live?
- Yes — it answered the hub's last check (checked 5h ago). It answered 100% of checks over the last 30 days.
- Is linkheft-api free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does linkheft-api have?
- 2 tools: dataset_info, domain_authority.
- Is linkheft-api 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 99.5%· all time 99.4%
last good check
of 2 tools
- degraded → live
- degraded → live
- live → degraded· timeout after 20000ms
- live → degraded· timeout after 20000ms
- down → live
- used for
- get authority score for a domain
- rank domains by web-graph authority
- takes → gives
- text → data
- tools
- 2 reads
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 36 other origins: the chain figures are the gateway's, not this listing's alone. How it is counted.
through this hub
successful
what callers paid
distinct
last 2026-11-13
counted from three payers (thin, concentrated, shared-payto)
Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run
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.
dataset_info reads unknown never probed
The Common Crawl web-graph release, Majestic Million date, as-of date and size of the data behind domain_authority.
{ "type": "object", "properties": {} }arguments 4 linesdomain_authority reads unknown 13h ago
Authority score (0-100), Common Crawl web-graph rank (harmonic + PageRank), hosts, previous rank and trend, Majestic Million rank, referring subnets and IPs for 1-50 domains, URLs or emails. found=false when a domain is outside the top 10M and the Majestic Million.
{ "type": "object", "required": [ "domains" ], "properties": { "sortBy": { "enum": [ "input", "score" ], "type": "string", "default": "input" }, "domains": { "type": "array", "items": { "type": "string" }, "maxItems": 50, "minItems": 1, "description": "Domains, URLs or emails, e.g. stripe.com" }, "minScore": { "type": "integer", "maximum": 100, "minimum": 0 } } }arguments 30 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 ide5670126216edbfd.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/e5670126216edbfd/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/e5670126216edbfd?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.