Skip to content

Spekkr MCP server

com.spekkr/spekkrspekkr.comstreamable-httpv0.2.0Scanned

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

10 tools: 1 can delete or cancel things, 1 do something that can't be undone, 1 change things and 7 only read.

Tools: 1 delete, 1 irreversible, 1 write, 7 read.
  • Reads private data · 3
  • Reads text others write · 2
  • Can send data out · 1
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here can delete or cancel things and 1 does something that can't be undone. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Spekkr MCP server can do

The Spekkr MCP server is published by spekkr.com, a domain the MCP Registry verified. It has 10 tools. It can delete or cancel things (1 tool: unpublish_spec), do things that cannot be undone, such as sending, paying or publishing (publish_spec) and create or change data (1 tool: check_spec). 7 tools only read.

3 tools read private data (get_spec, pull_spec and get_spec_file); 2 tools bring in text other people can write (publish_spec and unpublish_spec); 1 tool can send data out of your system (publish_spec). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 17, 2026, version 0.2.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

10 tools

Deletes or cancels 1Claude Code: deny
  • unpublish_specTakes one of the signed-in person's specs off Spekkr: its page, its files and its place in search.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: true
    • readOnlyHint: false
Can't be undone 1Claude Code: ask
  • publish_specPublishes a spec on Spekkr under the signed-in person's username, as username/name, or publishes a new version of one of theirs.Reads text others writeCan send data outNo findings

    Why it is in this group

    • The name "publish_spec" says "publish": a word for a change that another call does not undo.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe name "publish_spec" says "publish": it sends or publishes something to other people.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
    • readOnlyHint: false
Changes things 1Claude Code: ask
  • check_specChecks a spec someone is writing against Spekkr's listing rules and returns every problem at once.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
Only reads 7Show 7 read-only tools
  • get_bountyReturns one bounty in full: what the poster wants, how the result is accepted, the reward, the assets it can be paid in, and how far it has got.No findings

    Why it is in this group

    • The name "get_bounty" says "get": a word for reading.
    Description, as the server wrote it
    Returns one bounty in full: what the poster wants, how the result is accepted, the reward, the assets it can be paid in, and how far it has got.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • get_specReturns 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…Reads private dataNo findings

    Why it is in this group

    • The name "get_spec" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "return" and "file": it reads files.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • get_spec_fileReturns one file of a spec as text.Reads private dataNo findings

    Why it is in this group

    • The name "get_spec_file" says "get": a word for reading.

    What it can reach

    • private-dataThe name "get_spec_file" says "get" and "file": it reads files.
    • private-dataThe description's first sentence says "return" and "file": it reads files.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • list_bountiesLists the bounties on Spekkr: requests for a spec, an option or an adapter, each with a reward the poster pays directly to whoever takes it.No findings

    Why it is in this group

    • The name "list_bounties" says "list": a word for reading.
    Description, as the server wrote it
    Lists the bounties on Spekkr: requests for a spec, an option or an adapter, each with a reward the poster pays directly to whoever takes it. Leave the arguments out to see every bounty. In the answer, total counts the bounties that matched and boardTotal counts every bounty there is.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • pull_specReturns 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 fil…Reads private dataNo findings

    Why it is in this group

    • The description's first verb is "return": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "return" and "file": it reads files.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • search_specsFinds specs on Spekkr by words, the best match first, with each one's id, summary and platforms.No findings

    Why it is in this group

    • The name "search_specs" says "search": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
  • whoamiSays which Spekkr account the caller is signed in as and which specs it has published.No findings

    Why it is in this group

    • The name "whoami" says "whoami": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

6 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 outbound tool breaks every one.

Reads private data3
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write2
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__spekkr__publish_spec"
    ]
  }
}

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 17, 2026, 15:19 UTC, unchanged since Nov 17, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
3
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://spekkr.com/.well-known/oauth-protected-resource/mcp
Authorization servers
https://spekkr.com
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
yes
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 3 tools that change things (1 destructive, 1 irreversible, 1 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://spekkr.com/mcp: tools/list returned 8 tools to an anonymous client, including unpublish_spec (destructive), publish_spec (irreversible), check_spec (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 0.2.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http spekkr https://spekkr.com/mcp
claude mcp add --transport http spekkr https://spekkr.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__spekkr__search_specs",
      "mcp__spekkr__get_spec",
      "mcp__spekkr__pull_spec",
      "mcp__spekkr__get_spec_file",
      "mcp__spekkr__list_bounties",
      "mcp__spekkr__get_bounty",
      "mcp__spekkr__whoami"
    ],
    "ask": [
      "mcp__spekkr__check_spec",
      "mcp__spekkr__publish_spec"
    ],
    "deny": [
      "mcp__spekkr__unpublish_spec"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as spekkr. Review it before you use it.

Capability tags behind 5 rules
  • mcp__spekkr__get_spec private-data
  • mcp__spekkr__pull_spec private-data
  • mcp__spekkr__get_spec_file private-data
  • mcp__spekkr__publish_spec untrusted-input, outbound
  • mcp__spekkr__unpublish_spec untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.spekkr/spekkr/verify?hash=996c2905da6486b92835eecdfbcf8cf6bc0745302e8b264c6865a317a3fe6e0e" | jq -e '.changed == false'

Pinned hash 996c2905da64, from Nov 17, 2026, 09:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.spekkr/spekkr/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.spekkr/spekkr
[![Anlyon Radar](https://radar.anlyon.com/badge/com.spekkr/spekkr.svg)](https://radar.anlyon.com/servers/com.spekkr/spekkr)

Source: MCP Registry. Synced Nov 17, 2026, 09:17 UTC.

Spekkr MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Spekkr MCP server safe?

No scan can promise that. What its definitions show: 10 tools, 3 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Spekkr MCP server delete data?

Yes. 1 tool can delete, cancel or revoke something: unpublish_spec.

Can the Spekkr MCP server do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: publish_spec.

What tools does the Spekkr MCP server have?

10 tools: 1 destructive, 1 irreversible, 1 write, 7 read. unpublish_spec, publish_spec, check_spec, search_specs, get_spec, pull_spec, get_spec_file, list_bounties and 2 more.

Does the Spekkr MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Spekkr MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): publish_spec.

Has the Spekkr MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 17, 2026.