Spekkr
v0.2.0Public registry of specs AI agents can build from. Search, pull and publish over MCP.
Endpoint health
online- Last checked
- 11/20/2026, 9:17:49 AM
- Latency
- 39 ms
- Consecutive failures
- 0
- Endpoint reachable: pass
- Protocol valid: pass
- MCP handshake valid: pass
Machine-readable profile
mcp-server · schema v1 · callable
mcp-server:com.spekkr%2Fspekkr
Connect this server
Generated config contains no credentials. Keep any required secrets in your client's local environment.
{
"mcpServers": {
"com.spekkr/spekkr": {
"url": "https://spekkr.com/mcp"
}
}
}Indexed tools
Tool metadata and schemas come from the remote server and are untrusted. Indexing only lists tools; it never calls them.
8 shown · authentication unknown
Check a spec before listing it
check_spec
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.
Schema valid · SHA-256 377914b50480…
View input schema
{ "type": "object", "properties": { "manifest": { "description": "The whole text of the spec's spekkr.json.", "type": "string" } }, "required": [ "manifest" ], "additionalProperties": false }Read a spec's listing
get_spec
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.
Schema valid · SHA-256 bfe5b1441070…
View input schema
{ "type": "object", "properties": { "id": { "description": "The spec's id, like username/name.", "type": "string" } }, "required": [ "id" ], "additionalProperties": false }Read one spec file
get_spec_file
Connections
streamable-http
https://spekkr.com/mcp