SPOE MCP server
ai.spoe/spoespoe.aistreamable-httpv1.0.0Scanned
Check a name on 29 platforms and the domains; build and follow apps you own on SPOE.
10 tools: 1 do something that can't be undone, 4 change things and 5 only read.
- Reads private data · 3
- Reads text others write · 3
- Can send data out · 0
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here does something that can't be undone. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
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 SPOE MCP server can do
The SPOE MCP server is published by spoe.ai, a domain the MCP Registry verified. It has 10 tools. It can do things that cannot be undone, such as sending, paying or publishing (write_files) and create or change data (4 tools: check_handle, create_app, new_project and check_project), but cannot delete data. 5 tools only read.
3 tools read private data (list_files, read_file and change_status); 3 tools bring in text other people can write (check_handle, list_apps and app_status).
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.
Last scanned Nov 11, 2026, version 1.0.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
Can't be undone 1Claude Code: ask
write_filesSend a change: whole files to write (path and full content) and files to delete.No findings
Why it is in this group
- The name "write_files" says "write": a word for a change.
- The description's first verb is "send": a word for sending, and what is sent cannot be taken back.
Description, as the server wrote it Send a change: whole files to write (path and full content) and files to delete. SPOE checks it (for an app: its migrations on a fresh Postgres and its API routes) and a second AI from another model family reviews it. On a project that applies changes on its own (the default) a change the review passes goes in as a version the owner can undo; one with a high or critical finding, or over a file the owner edited since, waits for the owner in the studio. Costs only the review's credits (estimated now, charged when it finishes, never if it fails). Then call change_status: fix what the findings say and send the files again.
Annotations the server declares
- title: Write files
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
Changes things 4Claude Code: ask
check_handleCheck whether a brand name or username is free on X, YouTube, LinkedIn, GitHub, Shopify, Bluesky, Snapchat and more (29 platforms), and on the main domain endings (.com, .ai, .io, …Reads text others write1 finding
Why it is in this group
- The name "check_handle" says "handle": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Warn
The server marks "check_handle" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"openWorldHint":true}; The name "check_handle" says "handle": a word for a change.
Description, as the server wrote it Check whether a brand name or username is free on X, YouTube, LinkedIn, GitHub, Shopify, Bluesky, Snapchat and more (29 platforms), and on the main domain endings (.com, .ai, .io, .com.au and others). Each platform is only trusted while it still calls a certainly-taken name taken; platforms that refuse checks (Instagram, TikTok, Facebook, Reddit) come back as "check yourself" with a link. Free, no API key needed.
Annotations the server declares
- title: Check a name
- readOnlyHint: true
- openWorldHint: true
check_projectSPOE's ship check on the project as it stands, free and with no AI: keys written in the code, SQL or shell commands built from text, raw HTML, cookies accepted from any site, route…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 SPOE's ship check on the project as it stands, free and with no AI: keys written in the code, SQL or shell commands built from text, raw HTML, cookies accepted from any site, routes that change data without sign-in, and what search engines will miss. The same check every export ships as check.mjs. A critical finding stops a publish until the owner confirms it, so fix those with write_files first.
Annotations the server declares
- title: Ship check
- readOnlyHint: true
- openWorldHint: false
create_appStart building a new app, website or game on SPOE from a description.No findings
Why it is in this group
- The name "create_app" says "create": a word for a change.
Description, as the server wrote it Start building a new app, website or game on SPOE from a description. kind "website" makes a plain HTML site (fast, can be published at name.spoe.dev); kind "app" makes a full-stack Next.js, Fastify and Postgres app; kind "game" makes a browser game (Phaser for 2D, Three.js for 3D) that plays on a computer and a phone, can be published at name.spoe.dev, and borrows the mechanics of any games it is asked to be like, never their names, characters or art. A second AI from another model family reviews the change. Costs credits from the account: estimated first, charged when the build finishes, never if it fails. Returns the studio link to watch it and the project id for app_status.
Annotations the server declares
- title: Build an app
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
new_projectMake a new SPOE project from SPOE's starter, with nothing built yet and nothing charged, for you to write with write_files.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.
Description, as the server wrote it Make a new SPOE project from SPOE's starter, with nothing built yet and nothing charged, for you to write with write_files. kind "app": Next.js 15 (web/, app router, React 19) with a Fastify API (api/src) on Postgres (migrations in api/migrations, numbered .sql files), owner pages behind ADMIN_PASSWORD, and a rate limiter in api/src/limits.js. kind "website": plain HTML, CSS and JavaScript in site/. kind "game": Phaser 3 or Three.js in site/, with the engines in site/vendor/ (never edit those). Returns the project id, its studio link (live preview, publish, export) and the starter's files.
Annotations the server declares
- title: New empty project
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
Only reads 5Show 5 read-only tools
app_statusShow where an app on this account stands: its latest build (queued, generating, reviewing, waiting for the owner, applied, failed), the review's verdict, and its live address when …Reads text others writeNo findings
Why it is in this group
- The name "app_status" says "status": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "show" and "review": it reads comments, which other people can write.
Description, as the server wrote it Show where an app on this account stands: its latest build (queued, generating, reviewing, waiting for the owner, applied, failed), the review's verdict, and its live address when published.
Annotations the server declares
- title: Build status
- readOnlyHint: true
- openWorldHint: false
change_statusWhere a change sent with write_files stands: being reviewed, applied, or waiting for the owner, with every finding (severity, file, line, what is wrong and how to fix it).Reads private dataNo findings
Why it is in this group
- The name "change_status" says "status": a word for reading.
What it can reach
- private-dataThe description's first sentence says "file": it reads files.
Description, as the server wrote it Where a change sent with write_files stands: being reviewed, applied, or waiting for the owner, with every finding (severity, file, line, what is wrong and how to fix it). Fix the findings and send the files again with write_files.
Annotations the server declares
- title: Change status
- readOnlyHint: true
- openWorldHint: false
list_appsList the apps, websites and games on the SPOE account this API key belongs to, newest first, with their studio links.Reads text others writeNo findings
Why it is in this group
- The name "list_apps" says "list": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "list" and "website": it reads web pages, which anyone can write.
Description, as the server wrote it List the apps, websites and games on the SPOE account this API key belongs to, newest first, with their studio links.
Annotations the server declares
- title: List my apps
- readOnlyHint: true
- openWorldHint: false
list_filesEvery file in a project on this account, with its size.Reads private dataNo findings
Why it is in this group
- The name "list_files" says "list": a word for reading.
What it can reach
- private-dataThe name "list_files" says "list" and "file": it reads files.
- private-dataThe description's first sentence says "file": it reads files.
Description, as the server wrote it Every file in a project on this account, with its size. Files in site/vendor/ are game engines and generated files are made by SPOE: read them, never write them.
Annotations the server declares
- title: List files
- readOnlyHint: true
- openWorldHint: false
read_fileOne file of a project on this account, as it stands now (with every applied change and the owner's own edits).Reads private dataNo findings
Why it is in this group
- The name "read_file" says "read": a word for reading.
What it can reach
- private-dataThe name "read_file" says "read" and "file": it reads files.
- private-dataThe description's first sentence says "file": it reads files.
Description, as the server wrote it One file of a project on this account, as it stands now (with every applied change and the owner's own edits).
Annotations the server declares
- title: Read a file
- readOnlyHint: true
- openWorldHint: false
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.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.
- Reads private data3
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write3
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
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.
Looked at Nov 20, 2026, 18:27 UTC, unchanged since Oct 29, 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
- 5
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 5 tools that change things (1 irreversible, 4 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://spoe.ai/api/mcp: tools/list returned 10 tools to an anonymous client, including write_files (irreversible), check_handle (write), create_app (write), new_project (write), check_project (write)
Posture changes
- Oct 29, 2026
- Tools that change things, listed without credentials: 2 to 5
Findings
Matches of fixed checks, with the text they matched.
- Warncheck_handle
The server marks "check_handle" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"openWorldHint":true}; The name "check_handle" says "handle": a word for a change.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools1 changed.~1 changedView diff
- Changed:new_projectChanges thingsdescription
Tools6 added.+6 addedView diff
- Added:change_statusOnly reads
- Added:check_projectChanges things
- Added:list_filesOnly reads
- Added:new_projectChanges things
- Added:read_fileOnly reads
- Added:write_filesCan't be undone
PostureRemote posture changed. Tools that change things, listed without credentials: 2 -> 5.View diff
- Tools that change things, listed without credentials: 2 to 5
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http spoe https://spoe.ai/api/mcpclaude mcp add --transport http spoe https://spoe.ai/api/mcpRun 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.
{
"permissions": {
"allow": [
"mcp__spoe__list_apps",
"mcp__spoe__app_status",
"mcp__spoe__list_files",
"mcp__spoe__read_file",
"mcp__spoe__change_status"
],
"ask": [
"mcp__spoe__check_handle",
"mcp__spoe__create_app",
"mcp__spoe__new_project",
"mcp__spoe__write_files",
"mcp__spoe__check_project"
],
"deny": []
}
}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 spoe. Review it before you use it.
Capability tags behind 6 rules
- mcp__spoe__check_handle untrusted-input
- mcp__spoe__list_apps untrusted-input
- mcp__spoe__app_status untrusted-input
- mcp__spoe__list_files private-data
- mcp__spoe__read_file private-data
- mcp__spoe__change_status private-data
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/ai.spoe/spoe/verify?hash=213374a56071a2577962a31104a0851801f64f4919c2750f6619573a6718bd2f" | jq -e '.changed == false'Pinned hash 213374a56071, from Nov 11, 2026, 22:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/ai.spoe/spoe/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/ai.spoe/spoe)Source: MCP Registry. Synced Oct 21, 2026, 17:43 UTC.
SPOE MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the SPOE MCP server safe?
- No scan can promise that. What its definitions show: 10 tools, 5 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the SPOE MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the SPOE MCP server do things that cannot be undone?
- Yes. 1 tool can send, pay, publish or merge: write_files.
What tools does the SPOE MCP server have?
- 10 tools: 1 irreversible, 4 write, 5 read. write_files, check_handle, create_app, new_project, check_project, list_apps, app_status, list_files and 2 more.
Does the SPOE MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the SPOE MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the SPOE MCP server changed its tools?
- Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 11, 2026. Every change is on this page and in its Atom feed.