# pSEO Engine (remote · pseo.quantumcx.net)

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

- Trust score: 76/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-25

## Components

- remote · `pseo.quantumcx.net`: 76/100 (this document), [markdown](https://verifymcp.io/servers/net-quantumcx-pseo-engine/api-agent-mcp.md), [page](https://verifymcp.io/servers/net-quantumcx-pseo-engine/api-agent-mcp)

## Channel facts

- Endpoint: `https://pseo.quantumcx.net/api/agent/mcp`
- Transports: `streamable-http`
- Auth: `required`
- 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-09-25.

- **Endpoint Security**: 89/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - 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**: 71/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2110 tokens (~211/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**: 0/100
  - Stability check failed: schema churn in the 16 days we've observed: 9 tool removals, 0 breaking changes, 0 auth/transport breaks, 10 additions.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **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**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the pSEO Engine MCP server?

pSEO Engine is a hosted endpoint at https://pseo.quantumcx.net/api/agent/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 net-quantumcx-pseo-engine 'https://pseo.quantumcx.net/api/agent/mcp'
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "net-quantumcx-pseo-engine": {
      "type": "remote",
      "url": "https://pseo.quantumcx.net/api/agent/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add net-quantumcx-pseo-engine --url 'https://pseo.quantumcx.net/api/agent/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  net-quantumcx-pseo-engine:
    url: "https://pseo.quantumcx.net/api/agent/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "net-quantumcx-pseo-engine": {
      "Transport": "http",
      "Url": "https://pseo.quantumcx.net/api/agent/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add net-quantumcx-pseo-engine -t streamable-http -u 'https://pseo.quantumcx.net/api/agent/mcp'
```

### Other

```json
{
  "mcpServers": {
    "net-quantumcx-pseo-engine": {
      "type": "http",
      "url": "https://pseo.quantumcx.net/api/agent/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-09-25 (score 76, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-24 (score 76, 0)

- [security] The server rewrote its instructions, which are the text every model session reads

### 2026-09-20 (score 76, 0)

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

### 2026-09-19 (score 76, +3)

- [security regression] Authorization: partial → fail

### 2026-09-18 (score 73, 0)

- [security] Tool “seo_rows_list” rewrote its description, which is the text the model reads
- [cosmetic] “seo_rows_list” added an optional parameter “sort”

### 2026-09-17 (score 73, −1)

- [functional regression] Schema quality: 164 → 194
- [functional] New tool “seo_project_connect_ai”
- [cosmetic] “seo_project_create” added an optional parameter “aiApiKey”
- [cosmetic] “seo_project_create” added an optional parameter “aiBaseUrl”
- [cosmetic] “seo_project_create” added an optional parameter “aiModel”
- [cosmetic] “seo_project_create” added an optional parameter “perplexityApiKey”

### 2026-09-10 (score 74, +9)

- [security regression] Stability: unverified → fail
- [security regression] A breaking change shipped without a version bump: still 1.0.0
- [security regression] Tool “seo.audit.start” was removed
- [security regression] Tool “seo.content.generate” was removed
- [security regression] Tool “seo.job.status” was removed
- [security regression] Tool “seo.project.create” was removed
- [security regression] Tool “seo.project.get” was removed
- [security regression] Tool “seo.project.list” was removed
- [security regression] Tool “seo.publish” was removed
- [security regression] Tool “seo.research.start” was removed
- [security regression] Tool “seo.rows.list” was removed
- [security improvement] Authorization: unverified → partial
- [security] The server rewrote its instructions, which are the text every model session reads
- [functional] First check of Tool coverage: 100
- [functional] Destructive annotations: All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
- [functional] New tool “seo_audit_start”
- [functional] New tool “seo_content_generate”
- [functional] New tool “seo_job_status”
- [functional] New tool “seo_project_create”
- [functional] New tool “seo_project_get”
- [functional] New tool “seo_project_list”
- [functional] New tool “seo_publish”
- [functional] New tool “seo_research_start”
- [functional] New tool “seo_rows_list”

### 2026-09-09 (score 65)

First indexed and scored.

## MCP tools (10)

### `seo_project_list` (~72 tokens)

List projects

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.

Output parameters:

- `hint` (string): What to do next, given whether the list was empty.
- `projects` (array): Every project this key can act on. Empty on a new account.

### `seo_project_create` (~321 tokens)

Create a project

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.

Input parameters:

- `aiApiKey` (string): BYOK: the AI provider key this project runs on (stored encrypted). Recommended: a Google Gemini key from aistudio.google.com/apikey — its free tier works with no card. Omit to connect later via seo_p…
- `aiBaseUrl` (string): Optional OpenAI-compatible base URL for the key. Defaults to Google's Gemini endpoint. Example for OpenRouter: https://openrouter.ai/api/v1
- `aiModel` (string): Optional model id. Defaults to gemini-2.5-flash on the Gemini endpoint.
- `domain` (string): Optional custom domain the pages will be published on, e.g. 'example.com'. Omit to serve them under the platform's own domain.
- `name` (string, required): Display name, e.g. 'Plumbers by city'. The URL slug is derived from it automatically.
- `perplexityApiKey` (string): Optional Perplexity API key (api.perplexity.ai) to enable citation-bearing AI visibility checks for this project. Stored encrypted.
- `template` (string): Page template. Defaults to 'location'.

Output parameters:

- `domain` (string|null)
- `name` (string)
- `nextStep` (string)
- `projectId` (string): Pass this to every other tool.
- `readyToGenerate` (boolean): Always false here — a new project has no data source yet.
- `slug` (string)
- `template` (string)

### `seo_project_connect_ai` (~314 tokens)

Connect (or replace) a project's AI keys

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.

Input parameters:

- `aiApiKey` (string): The AI provider key to store (replaces any stored one). Omit to leave unchanged.
- `aiBaseUrl` (string): Optional OpenAI-compatible base URL; defaults to Google's Gemini endpoint.
- `aiModel` (string): Optional model id; defaults to gemini-2.5-flash on the Gemini endpoint.
- `clearAiKey` (boolean): Pass true to REMOVE the stored AI key — generation stops until a new one is connected.
- `clearPerplexityKey` (boolean): Pass true to REMOVE the stored Perplexity key.
- `perplexityApiKey` (string): Optional Perplexity API key for visibility checks; replaces any stored one. Omit to leave unchanged.
- `projectId` (string, required): The project id, exactly as returned by seo_project_list (a cuid such as 'cmtjyi1q20000l204octn48ai'). Not the slug, not the display name. If you do not have one, call seo_project_list first.

Output parameters:

- `aiKeyConnected` (boolean)
- `note` (string)
- `perplexityKeyConnected` (boolean)
- `projectId` (string)

### `seo_project_get` (~117 tokens)

Get one project's configuration and readiness

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.

Input parameters:

- `projectId` (string, required): The project id, exactly as returned by seo_project_list (a cuid such as 'cmtjyi1q20000l204octn48ai'). Not the slug, not the display name. If you do not have one, call seo_project_list first.

Output parameters:

- `domain` (string|null)
- `indexable` (boolean): False while the project is in staging mode.
- `name` (string)
- `projectId` (string)
- `readinessNote` (string): Plain-language reason, whichever way readyToGenerate went.
- `readyToGenerate` (boolean)
- `researchBrief` (string|null)
- `slug` (string)
- `template` (string)

### `seo_rows_list` (~286 tokens)

List pages in a project

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.

Input parameters:

- `limit` (integer): How many rows to return, 1-200. Defaults to 50. Values above 200 are rejected — page through instead of asking for everything.
- `projectId` (string, required): The project id, exactly as returned by seo_project_list (a cuid such as 'cmtjyi1q20000l204octn48ai'). Not the slug, not the display name. If you do not have one, call seo_project_list first.
- `sort` (string): 'risk' returns pages ordered by review risk (highest first), each with a score, band and human-readable reasons. Omit for creation order.
- `status` (string): Optional exact status filter. Omit for all statuses. Must be one of the listed values, uppercase.

Output parameters:

- `limit` (integer)
- `projectId` (string)
- `returned` (integer): How many rows came back; compare with limit to detect more pages.
- `rows` (array)

### `seo_job_status` (~146 tokens)

Check the latest background job

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.

Input parameters:

- `projectId` (string, required): The project id, exactly as returned by seo_project_list (a cuid such as 'cmtjyi1q20000l204octn48ai'). Not the slug, not the display name. If you do not have one, call seo_project_list first.

Output parameters:

- `job`: Null when no job has ever run for this project.
- `note` (string)
- `projectId` (string)
- `stillRunning` (boolean): Keep polling while true.

### `seo_research_start` (~271 tokens)

Start AI keyword research

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.

Input parameters:

- `brief` (string, required): One or two sentences describing the niche and the customer, e.g. 'Plumbing lead generation for independent plumbers across UK cities'. Must be at least 10 characters — a bare keyword is not enough co…
- `projectId` (string, required): The project id, exactly as returned by seo_project_list (a cuid such as 'cmtjyi1q20000l204octn48ai'). Not the slug, not the display name. If you do not have one, call seo_project_list first.
- `targetCount` (integer): How many keywords to mine, 10-2000. Higher costs more AI time. Start around 200 unless told otherwise.

Output parameters:

- `jobId` (string): Poll seo_job_status; the keywords do not exist yet.
- `nextStep` (string)
- `projectId` (string)
- `started` (boolean)

### `seo_content_generate` (~150 tokens)

Generate page content for pending rows

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.

Input parameters:

- `projectId` (string, required): The project id, exactly as returned by seo_project_list (a cuid such as 'cmtjyi1q20000l204octn48ai'). Not the slug, not the display name. If you do not have one, call seo_project_list first.

Output parameters:

- `jobId` (string): Poll seo_job_status until COMPLETED.
- `nextStep` (string)
- `projectId` (string)
- `total` (integer): Rows queued for generation.

### `seo_audit_start` (~130 tokens)

Audit every generated page for defects

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.

Input parameters:

- `projectId` (string, required): The project id, exactly as returned by seo_project_list (a cuid such as 'cmtjyi1q20000l204octn48ai'). Not the slug, not the display name. If you do not have one, call seo_project_list first.

Output parameters:

- `jobId` (string): Poll seo_job_status.
- `nextStep` (string)
- `projectId` (string)

### `seo_publish` (~145 tokens)

Publish approved pages

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.

Input parameters:

- `projectId` (string, required): The project id, exactly as returned by seo_project_list (a cuid such as 'cmtjyi1q20000l204octn48ai'). Not the slug, not the display name. If you do not have one, call seo_project_list first.

Output parameters:

- `note` (string)
- `projectId` (string)
- `publishedCount` (integer): Rows taken live by this call.
- `skippedNeedsReview` (integer): GENERATED drafts skipped: approval is a human gate.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/net-quantumcx-pseo-engine/api-agent-mcp#diagnostics

## Score history

- 2026-09-25: 76
- 2026-09-24: 76
- 2026-09-23: 76
- 2026-09-22: 76
- 2026-09-21: 76
- 2026-09-20: 76
- 2026-09-19: 76
- 2026-09-18: 73
- 2026-09-17: 73
- 2026-09-16: 74
- 2026-09-15: 74
- 2026-09-14: 74
- 2026-09-13: 74
- 2026-09-12: 74
- 2026-09-11: 74
- 2026-09-10: 74
- 2026-09-09: 65

## Common questions

### What is the pSEO Engine MCP server?

pSEO Engine is an MCP server listed in the public MCP registry as net.quantumcx/pseo-engine. Programmatic SEO as callable tools: research, generate, audit and publish landing pages. This page covers its hosted endpoint (https://pseo.quantumcx.net/api/agent/mcp).

### Is the pSEO Engine MCP server safe to use?

pSEO Engine scores 76 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 pSEO Engine MCP server expose?

pSEO Engine exposes 10 tools: seo_project_list, seo_project_create, seo_project_connect_ai, seo_project_get, seo_rows_list, and 5 more. Their descriptions and schemas cost roughly 1,952 tokens of context every time the server is loaded.

### Does the pSEO Engine MCP server require authentication?

Yes. pSEO Engine asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the pSEO Engine MCP server still maintained?

pSEO Engine is still listed as active in the MCP registry. We last reached this channel on 25 September 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://pseo.quantumcx.net/api/agent/mcp
- Authorisation metadata: https://pseo.quantumcx.net/.well-known/oauth-protected-resource/api/agent/mcp
- Website: https://quantumcx.net/pseo-engine
- Changelog RSS feed: https://verifymcp.io/servers/net-quantumcx-pseo-engine/api-agent-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/net-quantumcx-pseo-engine/api-agent-mcp.json
- HTML version of this page: https://verifymcp.io/servers/net-quantumcx-pseo-engine/api-agent-mcp