Spekkr
Server Details
Public registry of specs AI agents can build from. Search, pull and publish over MCP.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 8 tools
Most tools occupy clearly distinct slots: search_specs, get_spec, check_spec, publish_spec, unpublish_spec, pull_spec, whoami. The main risk is the get_spec / get_spec_file / pull_spec cluster, all of which return spec content, but descriptions explicitly delineate them (metadata vs. one file vs. a buildable bundle). check_spec and publish_spec also both report validation errors, though the read-only vs. publishing distinction is stated clearly.
Seven of eight tools follow a clean verb_noun pattern on the 'spec' noun (get_spec, get_spec_file, check_spec, publish_spec, pull_spec, unpublish_spec, search_specs). whoami is the sole deviation, but it is a widely recognized auth idiom rather than a naming error.
Eight tools is well within the sweet spot and each maps to a real step in the spec lifecycle (discover, inspect, validate, build, publish, unpublish, authenticate). No tool feels redundant or padded.
The lifecycle is essentially covered: search, read manifest, read individual files, validate, pull for building, publish/version, unpublish, and identity check. Minor gaps exist — there is no direct tool to fetch binary assets (get_spec_file defers to a download note) and no listing of a user's drafts, though whoami partially covers ownership.
Available Tools
8 toolscheck_specCheck a spec before listing itARead-onlyIdempotentInspect
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.
Inputs: manifest (required).
get_specRead a spec's listingARead-onlyIdempotentInspect
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.
Inputs: id (required).
get_spec_fileRead one spec fileARead-onlyIdempotentInspect
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.
Inputs: id (required), path (required), line.
publish_specPublish a specAInspect
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.
Inputs: files (required), manifest (required).
pull_specPull a spec to build fromARead-onlyIdempotentInspect
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.
Inputs: id (required), choices.
search_specsSearch specsARead-onlyIdempotentInspect
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.
Inputs: kind, limit, query, offset, +1 more.
unpublish_specTake a spec downADestructiveInspect
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.
Inputs: id (required).
whoamiWho am I on SpekkrARead-onlyIdempotentInspect
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.
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
AI agent registry — search, discover, register, and connect agents via MCP.
Registry of MCP servers, agent skills and plugins: search, filter, comments, likes, publish.
A registry of AI agent tools — MCP servers, APIs, CLIs, SDKs — kept current by automated ingestion.
Search and inspect source-pinned agent skills, plugins and tools through a free public MCP.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceAn MCP server that enables AI agents to search, discover, and retrieve technical specifications from a SpecLib instance. It provides tools for full-text search, scope listing, and reading specs as markdown content.-
- FlicenseAqualityCmaintenanceCentral registry for AI tools with vector search and knowledge graph, enabling intelligent tool discovery, chaining, and execution via MCP.12-
- AlicenseNot gradedqualityBmaintenanceExposes a multi-tenant AI asset registry over MCP so Cursor, Claude Code, and other IDE clients can discover, subscribe to, and use a team's agents, MCP servers, skills, and prompts directly. Supports project-scoped AK/SK credentials, approval-gated cross-project subscriptions, and immutable versioned releases.1Apache 2.0
- FlicenseNot gradedqualityDmaintenanceCentralized registry for MCP tools, resources, and prompt templates with JSON schema validation and role-based access control filtering.-
Glama MCP Gateway
Add one secure layer between your agents and this server.