SPOE is an MCP server published by ai.spoe, hosted at spoe.ai. When last checked on 2026-11-22 it was working: it answers and lists its tools. It declares 10 tools, including check_handle, list_apps, create_app, app_status, new_project.
Check a name on 29 platforms and the domains; build and follow apps you own on SPOE.
Nothing else in the archive shares these values.
Squares are this server's values; dots are other servers sharing them. A shared address or publisher is a lead, not proof of a common operator.
Inferred from the host name and headers: what a server runs on, not who runs 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.
| Parameter | Type | Description |
|---|---|---|
| name * | string | The brand name or handle, like "rosiebakes" or "@rosie_bakes". |
{
"name": "check_handle",
"title": "Check a name on every platform",
"description": "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.",
"inputSchema": {
"type": "object",
"required": [
"name"
],
"properties": {
"name": {
"type": "string",
"description": "The brand name or handle, like \"rosiebakes\" or \"@rosie_bakes\"."
}
}
},
"annotations": {
"title": "Check a name",
"readOnlyHint": true,
"openWorldHint": true
}
}List the apps, websites and games on the SPOE account this API key belongs to, newest first, with their studio links.
No parameters.
{
"name": "list_apps",
"title": "List my SPOE apps",
"description": "List the apps, websites and games on the SPOE account this API key belongs to, newest first, with their studio links.",
"inputSchema": {
"type": "object",
"properties": {}
},
"annotations": {
"title": "List my apps",
"readOnlyHint": true,
"openWorldHint": false
}
}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.
| Parameter | Type | Description |
|---|---|---|
| kind | string | website (plain HTML), app (full stack) or game (a browser game). Default website. |
| name * | string | A short name for the project. |
| description * | string | 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. |
{
"name": "create_app",
"title": "Build a new app or website",
"description": "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.",
"inputSchema": {
"type": "object",
"required": [
"name",
"description"
],
"properties": {
"kind": {
"enum": [
"website",
"app",
"game"
],
"type": "string",
"description": "website (plain HTML), app (full stack) or game (a browser game). Default website."
},
"name": {
"type": "string",
"description": "A short name for the project."
},
"description": {
"type": "string",
"description": "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."
}
}
},
"annotations": {
"title": "Build an app",
"readOnlyHint": false,
"openWorldHint": false,
"idempotentHint": false,
"destructiveHint": false
}
}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.
| Parameter | Type | Description |
|---|---|---|
| project_id * | string | The project id from create_app or list_apps. |
{
"name": "app_status",
"title": "Where a build has got to",
"description": "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.",
"inputSchema": {
"type": "object",
"required": [
"project_id"
],
"properties": {
"project_id": {
"type": "string",
"description": "The project id from create_app or list_apps."
}
}
},
"annotations": {
"title": "Build status",
"readOnlyHint": true,
"openWorldHint": false
}
}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.
| Parameter | Type | Description |
|---|---|---|
| kind | string | app (full stack), website (plain HTML) or game. Default app. |
| name * | string | A short name for the project. |
{
"name": "new_project",
"title": "Start an empty project to write yourself",
"description": "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.",
"inputSchema": {
"type": "object",
"required": [
"name"
],
"properties": {
"kind": {
"enum": [
"website",
"app",
"game"
],
"type": "string",
"description": "app (full stack), website (plain HTML) or game. Default app."
},
"name": {
"type": "string",
"description": "A short name for the project."
}
}
},
"annotations": {
"title": "New empty project",
"readOnlyHint": false,
"openWorldHint": false,
"idempotentHint": false,
"destructiveHint": false
}
}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.
| Parameter | Type | Description |
|---|---|---|
| project_id * | string | The project id from new_project, create_app or list_apps. |
{
"name": "list_files",
"title": "List a project's files",
"description": "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.",
"inputSchema": {
"type": "object",
"required": [
"project_id"
],
"properties": {
"project_id": {
"type": "string",
"description": "The project id from new_project, create_app or list_apps."
}
}
},
"annotations": {
"title": "List files",
"readOnlyHint": true,
"openWorldHint": false
}
}One file of a project on this account, as it stands now (with every applied change and the owner's own edits).
| Parameter | Type | Description |
|---|---|---|
| path * | string | The file's path, like web/app/page.tsx or site/index.html. |
| project_id * | string |
{
"name": "read_file",
"title": "Read a file",
"description": "One file of a project on this account, as it stands now (with every applied change and the owner's own edits).",
"inputSchema": {
"type": "object",
"required": [
"project_id",
"path"
],
"properties": {
"path": {
"type": "string",
"description": "The file's path, like web/app/page.tsx or site/index.html."
},
"project_id": {
"type": "string"
}
}
},
"annotations": {
"title": "Read a file",
"readOnlyHint": true,
"openWorldHint": false
}
}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.
| Parameter | Type | Description |
|---|---|---|
| files * | array | Up to 200 files, 3 MB of text in all. Each is { path, content } to write the whole file, or { path, delete: true }. |
| summary * | string | What this change does, in a sentence or two. The reviewer reads it beside the files. |
| project_id * | string |
{
"name": "write_files",
"title": "Write files, checked and reviewed",
"description": "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.",
"inputSchema": {
"type": "object",
"required": [
"project_id",
"summary",
"files"
],
"properties": {
"files": {
"type": "array",
"items": {
"type": "object",
"required": [
"path"
],
"properties": {
"path": {
"type": "string"
},
"delete": {
"type": "boolean"
},
"content": {
"type": "string",
"description": "The whole file."
}
}
},
"description": "Up to 200 files, 3 MB of text in all. Each is { path, content } to write the whole file, or { path, delete: true }."
},
"summary": {
"type": "string",
"description": "What this change does, in a sentence or two. The reviewer reads it beside the files."
},
"project_id": {
"type": "string"
}
}
},
"annotations": {
"title": "Write files",
"readOnlyHint": false,
"openWorldHint": false,
"idempotentHint": false,
"destructiveHint": false
}
}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.
| Parameter | Type | Description |
|---|---|---|
| change_id * | string | The change id write_files returned. |
{
"name": "change_status",
"title": "What the checks and the review said",
"description": "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.",
"inputSchema": {
"type": "object",
"required": [
"change_id"
],
"properties": {
"change_id": {
"type": "string",
"description": "The change id write_files returned."
}
}
},
"annotations": {
"title": "Change status",
"readOnlyHint": true,
"openWorldHint": false
}
}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.
| Parameter | Type | Description |
|---|---|---|
| project_id * | string |
{
"name": "check_project",
"title": "Run the ship check",
"description": "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.",
"inputSchema": {
"type": "object",
"required": [
"project_id"
],
"properties": {
"project_id": {
"type": "string"
}
}
},
"annotations": {
"title": "Ship check",
"readOnlyHint": true,
"openWorldHint": false
}
}SPOE is a private AI app builder whose users own and export their code. check_handle works without a key. Everything else acts on the SPOE account whose developer API key is sent as "Authorization: Bearer spoe_sk_..." (made at https://spoe.ai/settings, under API keys). Two ways to build. create_app: SPOE's own AI builds it, for credits; tell the user the estimate. Or build it yourself: new_project (free), read_file and list_files to see the starter, write_files to send whole files (checked and reviewed by a second AI, for the review's credits), then change_status until it is applied, fixing what the findings say; check_project runs the free ship check before the owner publishes. The owner previews, publishes and exports from the studio link.
Names, descriptions and schemas were written by the server and are shown as data.
Pattern matches on what the server declares. They show what it says it can do, not what it does.
None yet. Changes appear after a server's second daily check.