# SPOE (remote · spoe.ai)

Check a name on 29 platforms and the domains; build and follow apps you own on SPOE.

- Trust score: 80/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `spoe.ai`: 80/100 (this document), [markdown](https://verifymcp.io/servers/ai-spoe-spoe/api-mcp.md), [page](https://verifymcp.io/servers/ai-spoe-spoe/api-mcp)

## Channel facts

- Endpoint: `https://spoe.ai/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 68/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 70/100
  - Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 93/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 80% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http ai-spoe-spoe 'https://spoe.ai/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "ai-spoe-spoe": {
      "url": "https://spoe.ai/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ai-spoe-spoe": {
      "type": "http",
      "url": "https://spoe.ai/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ai-spoe-spoe]
url = "https://spoe.ai/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-spoe-spoe": {
      "type": "remote",
      "url": "https://spoe.ai/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ai-spoe-spoe --url 'https://spoe.ai/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-spoe-spoe:
    url: "https://spoe.ai/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "ai-spoe-spoe": {
      "Transport": "http",
      "Url": "https://spoe.ai/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ai-spoe-spoe -t streamable-http -u 'https://spoe.ai/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "ai-spoe-spoe": {
      "type": "http",
      "url": "https://spoe.ai/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 80, +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.

### 2026-11-03 (score 79, +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.

### 2026-11-02 (score 78, 0)

- [security] Tool “new_project” rewrote its description, which is the text the model reads

### 2026-10-31 (score 78, +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.

### 2026-10-29 (score 77, +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.

### 2026-10-28 (score 76, −1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional regression] Schema quality: 581 → 1379
- [functional regression] 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”

### 2026-10-26 (score 77, +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.

### 2026-10-24 (score 76, +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.

## MCP tools (10)

### `check_handle` (~135 tokens)

Check a name on every platform

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.

Input parameters:

- `name` (string, required): The brand name or handle, like "rosiebakes" or "@rosie_bakes".

### `list_apps` (~34 tokens)

List my SPOE apps

List the apps, websites and games on the SPOE account this API key belongs to, newest first, with their studio links.

### `create_app` (~262 tokens)

Build a new app or website

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.

Input parameters:

- `description` (string, required): 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, required): A short name for the project.

### `app_status` (~65 tokens)

Where a build has got to

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.

Input parameters:

- `project_id` (string, required): The project id from create_app or list_apps.

### `new_project` (~192 tokens)

Start an empty project to write yourself

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.

Input parameters:

- `kind` (string): app (full stack), website (plain HTML) or game. Default app.
- `name` (string, required): A short name for the project.

### `list_files` (~65 tokens)

List a project's files

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.

Input parameters:

- `project_id` (string, required): The project id from new_project, create_app or list_apps.

### `read_file` (~62 tokens)

Read a file

One file of a project on this account, as it stands now (with every applied change and the owner's own edits).

Input parameters:

- `path` (string, required): The file's path, like web/app/page.tsx or site/index.html.
- `project_id` (string, required)

### `write_files` (~223 tokens)

Write files, checked and reviewed

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.

Input parameters:

- `files` (array, required): 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, required)
- `summary` (string, required): What this change does, in a sentence or two. The reviewer reads it beside the files.

### `change_status` (~73 tokens)

What the checks and the review said

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.

Input parameters:

- `change_id` (string, required): The change id write_files returned.

### `check_project` (~103 tokens)

Run the ship check

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.

Input parameters:

- `project_id` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ai-spoe-spoe/api-mcp#diagnostics

## Score history

- 2026-11-05: 80
- 2026-11-04: 79
- 2026-11-03: 79
- 2026-11-02: 78
- 2026-11-01: 78
- 2026-10-31: 78
- 2026-10-30: 77
- 2026-10-29: 77
- 2026-10-28: 76
- 2026-10-27: 77
- 2026-10-26: 77
- 2026-10-25: 76
- 2026-10-24: 76
- 2026-10-23: 75
- 2026-10-22: 75
- 2026-10-21: 74
- 2026-10-20: 74
- 2026-10-19: 74
- 2026-10-18: 73
- 2026-10-17: 73
- 2026-10-16: 73
- 2026-10-15: 72

## Common questions

### 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.

## Links

- Remote endpoint: https://spoe.ai/api/mcp
- Website: https://spoe.ai/docs/api#mcp
- Changelog RSS feed: https://verifymcp.io/servers/ai-spoe-spoe/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-spoe-spoe/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/ai-spoe-spoe/api-mcp