pSEO Engine
REMOTE · PSEO.QUANTUMCX.NET · SCANNED SEP 25
Programmatic SEO as callable tools: research, generate, audit and publish landing pages.
Available components
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. How we score → Why this is hard to score →
Endpoint Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability check failed: schema churn in the 16 days we've observed: 9 tool removals, 0 breaking changes, 0 auth/transport breaks, 10 additions. See how to fix → Fail
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
remote · pseo.quantumcx.net
claude mcp add --transport http net-quantumcx-pseo-engine 'https://pseo.quantumcx.net/api/agent/mcp'
{
"mcpServers": {
"net-quantumcx-pseo-engine": {
"url": "https://pseo.quantumcx.net/api/agent/mcp"
}
}
} {
"servers": {
"net-quantumcx-pseo-engine": {
"type": "http",
"url": "https://pseo.quantumcx.net/api/agent/mcp"
}
}
} [mcp_servers.net-quantumcx-pseo-engine] url = "https://pseo.quantumcx.net/api/agent/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"net-quantumcx-pseo-engine": {
"type": "remote",
"url": "https://pseo.quantumcx.net/api/agent/mcp",
"enabled": true
}
}
} openclaw mcp add net-quantumcx-pseo-engine --url 'https://pseo.quantumcx.net/api/agent/mcp' --transport streamable-http
mcp_servers:
net-quantumcx-pseo-engine:
url: "https://pseo.quantumcx.net/api/agent/mcp" {
"McpServers": {
"net-quantumcx-pseo-engine": {
"Transport": "http",
"Url": "https://pseo.quantumcx.net/api/agent/mcp"
}
}
} assistant mcp add net-quantumcx-pseo-engine -t streamable-http -u 'https://pseo.quantumcx.net/api/agent/mcp'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- 20 Sept 26 0
- Tool “seo_research_start” rewrote its description, which is the text the model reads security
- 19 Sept 26 +3
- Authorization: partial → fail ▼ security
- 18 Sept 26 0
- Tool “seo_rows_list” rewrote its description, which is the text the model reads security
- “seo_rows_list” added an optional parameter “sort” cosmetic
- 17 Sept 26 −1
- Schema quality: 164 → 194 ▼ functional
- New tool “seo_project_connect_ai” functional
- “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” cosmetic
- 10 Sept 26 +9
- Stability: unverified → fail ▼ security
- A breaking change shipped without a version bump: still 1.0.0 ▼ security
- Tool “seo.audit.start” was removed ▼ security
- Tool “seo.content.generate” was removed ▼ security
- Tool “seo.job.status” was removed ▼ security
- Tool “seo.project.create” was removed ▼ security
- Tool “seo.project.get” was removed ▼ security
- Tool “seo.project.list” was removed ▼ security
- Tool “seo.publish” was removed ▼ security
- Tool “seo.research.start” was removed ▼ security
- Tool “seo.rows.list” was removed ▼ security
- Authorization: unverified → partial ▲ security
- The server rewrote its instructions, which are the text every model session reads security
- 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” functional
- 9 Sept 26 65
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 25 Sept 2026 · Probed https://pseo.quantumcx.net/api/agent/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=pseo.quantumcx.net | CN=YR2,O=Let's Encrypt,C=US | 4 Sept 2026 | 3 Dec 2026 | RSA 2048 | SHA256-RSA | 6d281491b471a2eb183f87a6afcd36ab70f |
| SANs: pseo.quantumcx.net | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of pseo.quantumcx.net. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| net. | present | 37331 | 13 | Verified |
| quantumcx.net. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://pseo.quantumcx.net/api/agent/mcp | Verified | 200 | |
| http (plaintext) | http://pseo.quantumcx.net/api/agent/mcp | HTTPS enforced | 308 | https://pseo.quantumcx.net/api/agent/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
seo_audit_start Audit every generated page for defects ~130
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.
| Name | Type | Req | Description |
|---|---|---|---|
| projectId | string | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| jobId | string | yes | Poll seo_job_status. |
| nextStep | string | yes | – |
| projectId | string | yes | – |
No examples provided.
seo_content_generate Generate page content for pending rows ~150
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.
| Name | Type | Req | Description |
|---|---|---|---|
| projectId | string | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| jobId | string | – | Poll seo_job_status until COMPLETED. |
| nextStep | string | yes | – |
| projectId | string | yes | – |
| total | integer | – | Rows queued for generation. |
No examples provided.
seo_job_status Check the latest background job ~146
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.
| Name | Type | Req | Description |
|---|---|---|---|
| projectId | string | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| job | – | yes | Null when no job has ever run for this project. |
| note | string | – | – |
| projectId | string | yes | – |
| stillRunning | boolean | – | Keep polling while true. |
No examples provided.
seo_project_connect_ai Connect (or replace) a project's AI keys ~314
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| aiKeyConnected | boolean | yes | – |
| note | string | yes | – |
| perplexityKeyConnected | boolean | yes | – |
| projectId | string | yes | – |
No examples provided.
seo_project_create Create a project ~321
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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'. |
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string|null | yes | – |
| name | string | yes | – |
| nextStep | string | yes | – |
| projectId | string | yes | Pass this to every other tool. |
| readyToGenerate | boolean | yes | Always false here — a new project has no data source yet. |
| slug | string | yes | – |
| template | string | yes | – |
No examples provided.
seo_project_get Get one project's configuration and readiness ~117
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.
| Name | Type | Req | Description |
|---|---|---|---|
| projectId | string | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string|null | yes | – |
| indexable | boolean | yes | False while the project is in staging mode. |
| name | string | yes | – |
| projectId | string | yes | – |
| readinessNote | string | yes | Plain-language reason, whichever way readyToGenerate went. |
| readyToGenerate | boolean | yes | – |
| researchBrief | string|null | yes | – |
| slug | string | yes | – |
| template | string | yes | – |
No examples provided.
seo_project_list List projects ~72
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| hint | string | yes | What to do next, given whether the list was empty. |
| projects | array | yes | Every project this key can act on. Empty on a new account. |
No examples provided.
seo_publish Publish approved pages ~145
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.
| Name | Type | Req | Description |
|---|---|---|---|
| projectId | string | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| note | string | – | – |
| projectId | string | yes | – |
| publishedCount | integer | – | Rows taken live by this call. |
| skippedNeedsReview | integer | – | GENERATED drafts skipped: approval is a human gate. |
No examples provided.
seo_research_start Start AI keyword research ~271
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.
| Name | Type | Req | Description |
|---|---|---|---|
| brief | string | yes | 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 | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| jobId | string | yes | Poll seo_job_status; the keywords do not exist yet. |
| nextStep | string | yes | – |
| projectId | string | yes | – |
| started | boolean | yes | – |
No examples provided.
seo_rows_list List pages in a project ~286
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | yes | – |
| projectId | string | yes | – |
| returned | integer | yes | How many rows came back; compare with limit to detect more pages. |
| rows | array | yes | – |
No examples provided.
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.