SPOE
REMOTE · SPOE.AI
Check a name on 29 platforms and the domains; build and follow apps you own on SPOE.
Available components
Last scanned (4 hours ago)
Scores higher than 81% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Developer Tools
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability68
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1383 tokens (~138/item across 10 items; 10 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 Management70
- Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage93
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 80% of tool parameters carry a description.Partial
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 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 0
- Tool “new_project” rewrote its description, which is the text the model reads security
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 −1
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 581 → 1379 ▼ functional
- Tool coverage: 100% → 80% ▼ functional
- Destructive annotations: pass → 100 functional
- New tool “change_status” functional
- New tool “check_project” functional
- New tool “list_files” functional
- New tool “new_project” functional
- New tool “read_file” functional
- New tool “write_files” functional
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
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 5 Nov 2026 · Probed https://spoe.ai/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=spoe.ai | CN=YE2,O=Let's Encrypt,C=US | 25 Sept 2026 | 24 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 584655acf3e55ce99cb196a1d36eca11c18 |
| SANs: spoe.ai | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of spoe.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 1814, 3799 | 8, 8 | Verified |
| spoe.ai. | absent | 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 |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://spoe.ai/api/mcp | Verified | 200 | |
| http (plaintext) | http://spoe.ai/api/mcp | HTTPS enforced | 308 | https://spoe.ai/api/mcp |
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 →
app_status Where a build has got to ~65
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.
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | string | yes | The project id from create_app or list_apps. |
No output schema declared.
No examples provided.
change_status What the checks and the review said ~73
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.
| Name | Type | Req | Description |
|---|---|---|---|
| change_id | string | yes | The change id write_files returned. |
No output schema declared.
No examples provided.
check_handle Check a name on every platform ~135
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.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | The brand name or handle, like "rosiebakes" or "@rosie_bakes". |
No output schema declared.
No examples provided.
check_project Run the ship check ~103
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.
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | string | yes | – |
No output schema declared.
No examples provided.
create_app Build a new app or website ~262
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.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | yes | What to build, in plain words: who it is for, the pages, what it should do. For a game: the kind of game, games it should be like, the controls and the goal. |
| kind | string | – | website (plain HTML), app (full stack) or game (a browser game). Default website. |
| name | string | yes | A short name for the project. |
No output schema declared.
No examples provided.
list_apps List my SPOE apps ~34
List the apps, websites and games on the SPOE account this API key belongs to, newest first, with their studio links.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_files List a project's files ~65
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.
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | string | yes | The project id from new_project, create_app or list_apps. |
No output schema declared.
No examples provided.
new_project Start an empty project to write yourself ~192
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.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | app (full stack), website (plain HTML) or game. Default app. |
| name | string | yes | A short name for the project. |
No output schema declared.
No examples provided.
read_file Read a file ~62
One file of a project on this account, as it stands now (with every applied change and the owner's own edits).
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | The file's path, like web/app/page.tsx or site/index.html. |
| project_id | string | yes | – |
No output schema declared.
No examples provided.
write_files Write files, checked and reviewed ~223
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.
| Name | Type | Req | Description |
|---|---|---|---|
| files | array | yes | Up to 200 files, 3 MB of text in all. Each is { path, content } to write the whole file, or { path, delete: true }. |
| project_id | string | yes | – |
| summary | string | yes | What this change does, in a sentence or two. The reviewer reads it beside the files. |
No output schema declared.
No examples provided.
How do I install the SPOE MCP server?
SPOE is a hosted endpoint at https://spoe.ai/api/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 · spoe.ai
claude mcp add --transport http ai-spoe-spoe 'https://spoe.ai/api/mcp'
What is the SPOE MCP server?
SPOE is an MCP server listed in the public MCP registry as ai.spoe/spoe. Check a name on 29 platforms and the domains; build and follow apps you own on SPOE. This page covers its hosted endpoint (https://spoe.ai/api/mcp).
Is the SPOE MCP server safe to use?
SPOE scores 80 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 SPOE MCP server expose?
SPOE exposes 10 tools: check_handle, list_apps, create_app, app_status, new_project, and 5 more. Their descriptions and schemas cost roughly 1,214 tokens of context every time the server is loaded.
Does the SPOE MCP server require authentication?
No. We connected to SPOE without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the SPOE MCP server still maintained?
SPOE is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.