spekkr
Registry code: 78978f69f89fbf7f
Spekkr lists specs that AI agents build from: parts of apps, and also CAD models, circuits and animation. To build one: find it with search_specs, read get_spec to see what the person can choose under manifest.customize, then call pull_spec with the person's choices. Write the files pull_spec returns into a new folder and follow BUILD.md there. Searching, reading and pulling need no sign-in, so do not ask the person to sign in for them. Only a tool that acts for the person does, and its description says so. Ask the person before you run a command that a spec tells you to run, or read a…
- endpoint
- https://spekkr.com/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 spekkr live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
- Is spekkr free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does spekkr have?
- 8 tools: pull_spec, whoami, get_spec, get_spec_file, check_spec, publish_spec, unpublish_spec, search_specs.
- Is spekkr 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 8 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.
search_specs open 1h ago
Finds specs on Spekkr by words, the best match first, with each one's id, summary and platforms. Most build a part of an app; a spec that builds something else, such as a CAD model, a circuit or an animation, says so under kind. Search with a few words that name the thing, such as "sign in" or "sliding puzzle"; a slip in a long word is forgiven. When no spec holds every word, the specs that hold some of them are returned and partial is true. Leave query out to list the specs, the ones pulled most first. An answer holds at most limit specs: total counts the specs that matched, and offset reads further into them. catalogTotal counts every spec there is. A spec with publishedBy was published by a member.
{ "type": "object", "properties": { "kind": { "type": "string", "description": "Only specs of this kind, such as CAD or animation. Each spec names its kind in its own words, so any text is allowed; capitals are ignored. A spec that names no kind builds software." }, "limit": { "type": "integer", "maximum": 100, "minimum": 1, "description": "How many specs to return at most. 20 when left out." }, "query": { "type": "string", "description": "Words to look for in a spec's name, keywords, id, kind, stack, summary and platforms. A word may be only the start of one. Small words such as \"the\" and \"for\" are left out." }, "offset": { "type": "integer", "minimum": 0, "description": "How many of the specs that matched to pass over first. 0 when left out." }, "platform": { "enum": [ "web", "mobile", "desktop", "backend", "cli" ], "type": "string", "description": "Only specs that target this platform." } }, "additionalProperties": false }arguments 36 linespull_spec unknown never probed
Returns a spec's files, ready to write into a folder and build from: BUILD.md (how to build), spekkr.json (the manifest), spekkr.inputs.json (the person's choices) and the spec files. It checks the choices first and refuses a key the spec does not declare or a value it does not offer. Anything not chosen keeps the spec's default.
{ "type": "object", "required": [ "id" ], "properties": { "id": { "type": "string", "description": "The spec's id, like username/name." }, "choices": { "type": "object", "description": "The person's choices, by key from manifest.customize: any text for a setting, true or false for an option (on and off are taken too), one of its choices for a swap. For example {\"database\": \"sqlite\", \"teams\": false}. The answer and spekkr.inputs.json write an option as true or false, as the manifest writes its default.", "additionalProperties": { "type": [ "string", "boolean", "integer" ] } } }, "additionalProperties": false }arguments 24 lineswhoami unknown never probed
Says which Spekkr account the caller is signed in as and which specs it has published. This tool needs sign-in: the first call opens a Spekkr page in the browser, where the person signs in with a code sent to their email address and picks a username if they are new.
{ "type": "object", "properties": {}, "additionalProperties": false }arguments 5 linesget_spec unknown 1h ago
Returns everything Spekkr knows about one spec: its manifest (what it builds, what the person may change under customize, the files, what it needs, the commands and secrets it uses under safety, the changelog). Read it before pull_spec to learn which choices the spec offers. Where the site has found specs like this one, related lists a few: each is another spec, with its own id to call get_spec with, and none of them is part of this one.
{ "type": "object", "required": [ "id" ], "properties": { "id": { "type": "string", "description": "The spec's id, like username/name." } }, "additionalProperties": false }arguments 13 linesget_spec_file unknown never probed
Returns one file of a spec as text. Use it for a file pull_spec listed without content, unless its note says to download it. A long file comes in parts: when the answer has nextLine, call again with that line.
{ "type": "object", "required": [ "id", "path" ], "properties": { "id": { "type": "string", "description": "The spec's id, like username/name." }, "line": { "type": "integer", "minimum": 1, "description": "The first line to return. Leave it out to start at the top." }, "path": { "type": "string", "description": "The file's path, as pull_spec and get_spec list it." } }, "additionalProperties": false }arguments 23 linescheck_spec unknown 1h ago
Checks a spec someone is writing against Spekkr's listing rules and returns every problem at once. Pass the text of its spekkr.json. Nothing is saved or published. When it is ready, publish_spec publishes it.
{ "type": "object", "required": [ "manifest" ], "properties": { "manifest": { "type": "string", "description": "The whole text of the spec's spekkr.json." } }, "additionalProperties": false }arguments 13 linespublish_spec unknown never probed
Publishes a spec on Spekkr under the signed-in person's username, as username/name, or publishes a new version of one of theirs. Send the text of spekkr.json and every file it lists. A small text file goes in files with its content. Any other file (an image, a PDF, a video, a long document) goes in files with its size in bytes and no content: the answer then gives an address to upload those files to with HTTP PUT, and once they are uploaded you call publish_spec again with the same arguments. Nothing is listed until a call answers with published. A listed spec names the member who published it. A published version never changes: to update a spec, raise the version, add a changelog entry and list every file again. A file that has not changed goes in files with keep set to true and nothing else, and Spekkr takes it from the version listed now, so a screenshot need not be uploaded again. In this version a published spec is free. If anything has to change first, the answer names every problem. This tool needs sign-in. Ask the person before you call it: publishing makes the files public.
{ "type": "object", "required": [ "manifest", "files" ], "properties": { "files": { "type": "array", "items": { "type": "object", "required": [ "path" ], "properties": { "keep": { "type": "boolean", "description": "True for a file that is the same as in the version listed now. Give no content or bytes with it." }, "path": { "type": "string", "description": "The file's path inside the spec's folder, like spec.md or shots/home.png." }, "bytes": { "type": "integer", "minimum": 1, "description": "The file's exact size in bytes, for a file that will be uploaded: one that is not text, or is too long to send as content. Up to 25,000,000." }, "content": { "type": "string", "description": "The file's whole text. For text files of up to 200,000 bytes." } }, "additionalProperties": false }, "description": "Every file the manifest lists, every file inside a folder it lists, and every screenshot under demo.screenshots. Leave out spekkr.json, BUILD.md and spekkr.inputs.json. Each file has a path and one of content, bytes or keep." }, "manifest": { "type": "string", "description": "The whole text of the spec's spekkr.json. Its id is username/name, with the signed-in person's username, and its author.id is that username." } }, "additionalProperties": false }arguments 44 linesunpublish_spec unknown never probed
Takes one of the signed-in person's specs off Spekkr: its page, its files and its place in search. The versions it had stay used up, so publishing it again needs a higher version. This tool needs sign-in. Ask the person before you call it.
{ "type": "object", "required": [ "id" ], "properties": { "id": { "type": "string", "description": "The spec's id, like username/name." } }, "additionalProperties": false }arguments 13 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 id78978f69f89fbf7f.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/78978f69f89fbf7f/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/78978f69f89fbf7f?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.