spaicely-public
Registry code: 0a0c2dc823eb3586
Spaicely hosts static websites on the customer's own domain in the EU.
This public server needs no account. Use it to find a free domain name:
- endpoint
- https://mcp.spaicely.com/mcp/public
- 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 spaicely-public live?
- Yes — it answered the hub's last check (checked 17h ago). It answered 100% of checks over the last 30 days.
- Is spaicely-public free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does spaicely-public have?
- 3 tools: domains.search, blocks.get, blocks.list.
- Is spaicely-public 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 3 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.
blocks.list open 17h ago
Lists ready-made building blocks for a site on Spaicely: a cookie notice that holds back analytics until the visitor agrees, forms that send to Spaicely without leaving the page, videos and maps that load only after a click, a mobile menu, an FAQ with structured data, a language switch, opening hours that say whether the place is open now, a progress bar for a donation form and a cart for the shop. Prefer a block to writing the same thing yourself. blocks.get gives a block's files, the HTML snippet for the pages and notes. Needs no account.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "properties": {} }arguments 5 linesdomains.search unknown 17h ago
Checks whether domain names are free to register. Pass full domains (bakkerijjansen.nl) and/or bare names (bakkerijjansen); a bare name is tried with every extension in `extensions`, or by default with the ones people ask for most: nl, com, eu, be, de, net, org, shop, online, site, store, tech, app, dev, io, ai, co.uk, uk, fr, at, ch, it, es, nu, se, co, me, info, biz, xyz, cloud. We sell 718 extensions in all (.amsterdam, .restaurant, .photography and so on); pass them in `extensions` when they fit the name. At most 50 domains per call. The first check is quick and asks DNS only: taken means the domain has nameservers (certain); likely_available means it has none, so it is probably free (reason dns_only, or no_rdap where the registry has no RDAP and verifying adds nothing). Once the person has favourites, call again with verify: true for the dns_only ones (at most 10 domains): that asks our registrar (or else the registry over RDAP) and turns them into available or taken; otherwise reason says why (rdap_rate_limited, rdap_unavailable). A premium name (premium: true) costs what its registry asks: price is our price for it in euro cents before VAT, often far above the usual price, so tell the person. unknown means no answer at all. Each free domain has a register_url: a page where the person signs in and registers it in their own name. Registration itself checks again. Each taken domain has a transfer_url: if the domain is the person's own, they move it to Spaicely there.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "names" ], "properties": { "names": { "type": "array", "items": { "type": "string" }, "minItems": 1, "description": "Domains or bare names, such as bakkerijjansen.nl or bakkerijjansen" }, "verify": { "type": "boolean", "description": "Deep check for a shortlist: also ask the registries. At most 10 domains." }, "extensions": { "type": "array", "items": { "type": "string" }, "description": "Extensions to try bare names with, such as nl, com, eu. Default: the ones people ask for most." } } }arguments 28 linesblocks.get unknown 17h ago
Gives one building block from blocks.list: its files, the HTML snippet to put in the pages, and notes on using it. Copy the files into the site by passing deploy_files along in sites.deploy (each is { path, source_url }; Spaicely fetches them, so you do not retype the code), then put the snippet in every page that needs it, with its texts in the language of the page. Without version you get the newest; a version never changes. Needs no account.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "name" ], "properties": { "name": { "type": "string", "description": "The block's name from blocks.list, such as consent" }, "version": { "type": "integer", "minimum": 1, "description": "A version; default the newest" } } }arguments 18 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 id0a0c2dc823eb3586.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/0a0c2dc823eb3586/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/0a0c2dc823eb3586?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.