Skip to content
QuantumCX logo

QuantumCX MCP server

Which MCP servers are QuantumCX's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-26

← Back to QuantumCX

Whose server it is
  • Registry namenet.quantumcx/pseo-engineverified in the MCP registry

The registry name sits under quantumcx.net. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-26
  • Stateanswerschecked 2026-10-26
  • Tools10
  • Server calls itselfpseo-engine
  • Server version1.0.0
  • Protocol version2025-06-18

On 2026-10-26 the server answered initialize and tools/list without a sign-in. First answer in 712 ms.

Should an agent connect itConnect it, with care
  • Its tools do generate SEO pages from a research brief, but not track search rankings for published pages.

Once connected

  • For "generate SEO pages from a research brief", the likely first call is seo_project_list.
  • seo_publish change data without a sign-in: anyone with the address can call them.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 9, the first on 2026-10-26
  • INITE MCP score69 of 100answers 100 · does the job 50 · definitions 100 · context 100 · connects 100 · lowered by the warning signs below
  • What an agent can do with it1 of 2 use cases
  • Answered100% of days9 of 9 daily checks
  • Median first answer196 ms
  • Space in an agent's context≈ 2,609 tokensthe definitions of all its tools (10), which an agent carries on every turn
  • Tool definitionsA · 100 of 100
  • Typed results10 of 10 toolsdeclared outputSchema: results come typed, read once
  • Every tool passes all six checks.

What an agent can do with it

  • can do · generate SEO pages from a research brief
  • not sure · review generated pages before they are published
  • cannot · track search rankings for published pages

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

  • Tools that change data, on a server that answers without a sign-in: seo_publish

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers10 tools · read 2026-10-26
  • 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…

  • 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…

  • 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…

  • 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…

  • 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…

  • 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…

  • 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…

  • 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…

  • 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…

  • 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…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

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

Add it

Claude Code, in a terminal

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

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://pseo.quantumcx.net/api/agent/mcp as a custom connector in the settings.

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.