host-html
https://suifgsvtcbrawzdhyuhk.supabase.co
Registry code: fc66d5b711948010
Use publish_html to turn HTML you wrote into a shareable link, and update_page to revise that same link. Free pages stay online for 3 days; paid plans keep them permanently.
- endpoint
- https://suifgsvtcbrawzdhyuhk.supabase.co/functions/v1/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 host-html live?
- Yes — it answered the hub's last check (checked 15h ago). It answered 100% of checks over the last 30 days.
- Is host-html free to use?
- Not measured yet.
- What tools does host-html have?
- 2 tools: publish_html, update_page.
- Is host-html 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 2 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.
publish_html unknown never probed
Publish a self-contained HTML document and get back a public URL. Use this whenever the user wants to share, send, or host HTML you produced — a report, dashboard, deck, prototype or one-page site — instead of leaving it as a file they cannot open. The HTML must be self-contained: inline the CSS and JS, or reference them by absolute URL.
{ "type": "object", "required": [ "html" ], "properties": { "html": { "type": "string", "description": "The full, self-contained HTML document to publish. Max 1MB on the free plan, 10MB on Pro, 50MB on Studio/Agency." }, "slug": { "type": "string", "description": "Optional custom path, e.g. 'q3-report' → /p/q3-report. 2–64 lowercase letters, digits and internal hyphens. Requires a paid plan (Pro or above); omit for a random slug." }, "title": { "type": "string", "description": "Human-readable title. Sets the link-preview title — pass a real one, not a filename." }, "password": { "type": "string", "description": "Optional password (4–72 characters). Viewers must enter it to see the page. Paid plans only; omit for a public page." } } }arguments 24 linesupdate_page unknown never probed
Replace the HTML of a page you already published, keeping the SAME link. Use this for every revision — a fix, a new draft, refreshed numbers — instead of publishing a new page, so a link the user already shared keeps working. Only pages owned by the same account can be updated.
{ "type": "object", "required": [ "slug", "html" ], "properties": { "html": { "type": "string", "description": "The full, self-contained replacement HTML document." }, "slug": { "type": "string", "description": "The page's slug (the part after /p/), or its full URL." } } }arguments 17 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 idfc66d5b711948010.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/fc66d5b711948010/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/fc66d5b711948010?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.
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.
- tkoqkknsezxavtxfywkm.supabase.co ops-control-hq-developer-risk
- gdzlcxskuhupymyxywzm.supabase.co tokenguard
- xsrtcehyqluhvywmaihd.supabase.co lilambd-data
- mmvdabzadclebfxyzudg.supabase.co forge
- eutdgemlrpvnxfkkpvlu.supabase.co cred-mcp
- qdcpuvyyidzxyhdtwvai.supabase.co energiror-mcp
- tdueqhfxyojmjgactdyc.supabase.co agentsfinance-ai
- ivnmscuuljqubunqcgkh.supabase.co insurelink-mcp
115 more sit on this domain. All of them.