pSEO Engine MCP Server

by quantumcx Your server? Claim it

not responding

pSEO Engine is listed as active in the registry but did not answer our last check. It exposes 10 tools.

Programmatic SEO as callable tools: research, generate, audit and publish landing pages.

Uptime history 13 days of history · worst day 10%

13 days agonow

12.1%

Uptime 24h

11 of 91 checks

Tools

read from the server

1277 ms

Response time

average over 24h

open, no key

Access

streamable-http

What changed 23

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 11 September 2026. No other catalogue keeps this.

20 Sep a tool description was rewritten seo_research_start

19 Sep 2 tools changed the parameters they ask for seo_project_create, seo_rows_list

19 Sep a tool appeared seo_project_connect_ai

19 Sep a tool description was rewritten seo_rows_list

11 Sep 9 tools appeared seo_audit_start, seo_content_generate, seo_job_status and 6 more

11 Sep 9 tools disappeared seo.audit.start, seo.content.generate, seo.job.status and 6 more

pSEO Engine does not always answer

Over the last week it answered 16.9% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 10 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add pseo-engine --transport http https://pseo.quantumcx.net/api/agent/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "pseo-engine": {
      "url": "https://pseo.quantumcx.net/api/agent/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.pseo-engine]
url = "https://pseo.quantumcx.net/api/agent/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "pseo-engine": {
      "url": "https://pseo.quantumcx.net/api/agent/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "pseo-engine": {
      "url": "https://pseo.quantumcx.net/api/agent/mcp"
    }
  }
}

Available tools 10

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

seo

seo_audit_start

ASYNCHRONOUS. Scans all generated pages for broken text, unfilled placeholders, truncated copy and missing images, recording findings per page. Returns a jobId; poll seo_job_status. This only REPORTS problems — it does not fix them. Costs 30c per call.

seo_content_generate

ASYNCHRONOUS. Starts the content-generation queue over every PENDING row in the project. It also spends real AI budget per generated page. Requires the project to be configured (check readyToGenerate via seo_project_get first). Returns a jobId immediately; poll seo_job_status. Generated pages land in GENERATED status and are NOT live until approved and published. Costs 75c per call.

seo_job_status

Returns the most recent background job for a project: type, status (QUEUED/RUNNING/COMPLETED/FAILED/CANCELLED), progress counters and the last log line. Poll this every few seconds after any tool that starts a job. Do NOT re-call the start tool while status is RUNNING; it will be refused. FREE — this call costs nothing.

seo_project_connect_ai

Stores the AI provider key this project's generation, audits and research run on — BYOK: the tokens bill YOUR provider account, not ours. Recommended: a Google Gemini API key (aistudio.google.com/apikey); its free tier works with no card. Optionally stores a Perplexity API key to enable citation-bearing AI visibility checks. Keys are stored encrypted and can never be read back — only replaced or cleared. FREE — this call costs nothing.

seo_project_create

Creates a new programmatic-SEO project and returns its projectId. Call this when seo_project_list comes back empty — every other tool needs a projectId and a new account has none. The project is created EMPTY: it still needs a data source and a content spec before seo_content_generate will run, so call seo_project_get afterwards and read readinessNote. FREE — this call costs nothing.

seo_project_get

Returns one project's settings and whether it is configured enough to generate content (needs both a field mapping and a content spec). Use this before seo_content_generate to avoid starting a run that will immediately fail. FREE — this call costs nothing.

seo_project_list

Lists every programmatic-SEO project this API key can act on, with id, name, slug, custom domain and page count. Call this FIRST in any session — every other tool needs a projectId from here, and ids cannot be guessed or carried over from another account. FREE — this call costs nothing.

seo_publish

SYNCHRONOUS. Takes approved pages live. IMPORTANT: only rows in REVIEWED status are published — GENERATED drafts are deliberately skipped, because approval is a human gate in this product. The response reports how many were skipped and why; if publishedCount is 0 and skippedNeedsReview is high, the pages need approving in the dashboard first. Costs 15c per call.

seo_research_start

ASYNCHRONOUS. Starts a keyword-research run that mines and qualifies keywords into PENDING rows. It spends real AI budget, so call it once and then poll seo_job_status until status is COMPLETED. Returns immediately with a jobId — the keywords do NOT exist yet when this returns. Fails if a research run is already in progress. HUMAN trial accounts get one research run free; a second run returns code card_required — only a human on the account can start a plan, so stop and report instead of retrying. Costs 750c per call.

seo_rows_list

Returns a page of rows (individual generated pages) with slug, target keyword and status. Statuses are PENDING (no content yet), GENERATING, GENERATED (draft), REVIEWED (approved), PUBLISHED (live), FAILED, FLAGGED_DUPLICATE. Content bodies are NOT included — this is a listing, not an export. Use sort:'risk' to get the review queue ordered by risk score (duplicates and pages with QA findings first) so a human reviews the riskiest pages before bulk-approving the safe ones. Costs 3c per call.

Tools removed

Tools this server used to expose. Anything built against them stopped working on the day they went.

seo.audit.start

removed 11 Sep 2026

seo.content.generate

removed 11 Sep 2026

seo.job.status

removed 11 Sep 2026

seo.project.create

removed 11 Sep 2026

seo.project.get

removed 11 Sep 2026

seo.project.list

removed 11 Sep 2026

seo.publish

removed 11 Sep 2026

seo.research.start

removed 11 Sep 2026

seo.rows.list

removed 11 Sep 2026

Endpoints

URL	Transport	State	Latency	Checked
https://pseo.quantumcx.net/api/agent/mcp	streamable-http	answering	97 ms	10 min ago

Alternatives to pSEO Engine

same job, measured the same way

MAJR AI SEO

by majrdotapp

Audit a page for search and AI answer engines; generate robots.txt, sitemap, head, llms.txt.

answering

SeoGrep

by seogrep

SEO for AI agents: crawl sites, audit pages, pull Search Console data, generate shareable reports.

answering

FormEdge

by formedge

Create, edit, preview and publish FormEdge forms and landing pages, and review submissions.

answering

QrMakerIO

by qrmakerio

Generate styled QR codes, manage dynamic short links with analytics, and publish landing pages.

34 installs/wk local only

Supstack

by drbaher

Evidence-based supplement research, dosing, safety, and interactions as agent-callable tools.

42 installs/wk local only

Google Custom Search MCP

by a1-x-tech

MCP server for Google Custom Search: web and image search via a Programmable Search Engine.

21 installs/wk local only

Topicforge

by topicforge

Generate programmatic SEO articles, topic clusters, FAQ schema, and batch jobs via TopicForge.

40 installs/wk local only

AIRAS

by airas-org

Automated AI research toolkit: hypothesis generation, experiments, and paper writing

220 installs/wk local only

pSEO Engine — questions

Answers built from our own checks of this server.

What can pSEO Engine do?

It exposes 10 tools, read directly from the server on our last check. Among them: seo_audit_start, seo_content_generate, seo_job_status, seo_project_connect_ai, seo_project_create, seo_project_get and 4 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is pSEO Engine working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 11 of 91 checks got a reply (12.1%), average response time 1277 ms. The bar chart above shows every period we have measured.

Did pSEO Engine ever remove tools?

Yes. seo.audit.start, seo.content.generate, seo.job.status, seo.project.create and 5 more are no longer exposed — we recorded the date each one disappeared. A tool vanishing usually means a breaking change for anything that depended on it.

The registry lists pSEO Engine as active — why does it not respond?

The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.

How do I connect pSEO Engine?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does pSEO Engine need an API key?

No. pSEO Engine completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 10 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is pSEO Engine?

It answers our handshake in 1277 ms on average, which is faster than 6% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.