Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Spekkr

REMOTE · SPEKKR.COM

Public registry of specs AI agents can build from. Search, pull and publish over MCP.

Available components

65 Trust /100

Last scanned (22 hours ago)

Scores higher than 46% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Developer Tools

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability67
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1581 tokens (~197/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability check failed: schema churn in the 4 days we've observed: 2 tool removals, 0 breaking changes, 0 auth/transport breaks, 0 additions. See how to fix → Fail
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 18 Nov 26 0
    • Stability: unverified → fail ▼ security
    • A breaking change shipped without a version bump: still 0.2.0 ▼ security
    • Tool “get_bounty” was removed ▼ security
    • Tool “list_bounties” was removed ▼ security
    • Schema quality: 173 → 197 ▼ functional
  • 17 Nov 26 65

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://spekkr.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=spekkr.com CN=WE1,O=Google Trust Services,C=US 19 Nov 2026 17 Feb 2027 ECDSA 256 ECDSA-SHA256 6ec6f6d568f7fcc4137eb3c9c29e015d
SANs: spekkr.com, analytics.spekkr.com, *.analytics.spekkr.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of spekkr.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
spekkr.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://spekkr.com/mcp Verified 200
http (plaintext) http://spekkr.com/mcp HTTPS enforced 301 https://spekkr.com/mcp
MCP tools · 8 exposed · ~1,307 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
check_spec ~72

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.

NameTypeReqDescription
manifeststringyesThe whole text of the spec's spekkr.json.

No output schema declared.

No examples provided.

get_spec ~121

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.

NameTypeReqDescription
idstringyesThe spec's id, like username/name.

No output schema declared.

No examples provided.

get_spec_file ~113

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.

NameTypeReqDescription
idstringyesThe spec's id, like username/name.
lineinteger–The first line to return. Leave it out to start at the top.
pathstringyesThe file's path, as pull_spec and get_spec list it.

No output schema declared.

No examples provided.

publish_spec ~346

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.

NameTypeReqDescription
filesarrayyesEvery 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 o…
manifeststringyesThe 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.

No output schema declared.

No examples provided.

pull_spec ~181

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.

NameTypeReqDescription
choicesobject–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",…
idstringyesThe spec's id, like username/name.

No output schema declared.

No examples provided.

search_specs ~327

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.

NameTypeReqDescription
kindstring–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.
limitinteger–How many specs to return at most. 20 when left out.
offsetinteger–How many of the specs that matched to pass over first. 0 when left out.
platformstring–Only specs that target this platform.
querystring–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.

No output schema declared.

No examples provided.

unpublish_spec ~79

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.

NameTypeReqDescription
idstringyesThe spec's id, like username/name.

No output schema declared.

No examples provided.

whoami ~68

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the Spekkr MCP server?

Spekkr is a hosted endpoint at https://spekkr.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · spekkr.com

# add to Claude Code
claude mcp add --transport http com-spekkr-spekkr 'https://spekkr.com/mcp'
Common questions

What is the Spekkr MCP server?

Spekkr is an MCP server listed in the public MCP registry as com.spekkr/spekkr. Public registry of specs AI agents can build from. Search, pull and publish over MCP. This page covers its hosted endpoint (https://spekkr.com/mcp).

Is the Spekkr MCP server safe to use?

Spekkr scores 65 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Spekkr MCP server expose?

Spekkr exposes 8 tools: search_specs, get_spec, pull_spec, get_spec_file, check_spec, and 3 more. Their descriptions and schemas cost roughly 1,307 tokens of context every time the server is loaded.

Does the Spekkr MCP server require authentication?

No. We connected to Spekkr without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Spekkr MCP server still maintained?

Spekkr is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Spekkr MCP server?

VerifyMCP ran 13 checks on Spekkr, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.