pSEO Engine MCP server
net.quantumcx/pseo-enginequantumcx.netstreamable-httpv1.0.0Scanned
Programmatic SEO as callable tools: research, generate, audit and publish landing pages.
10 tools: 1 do something that can't be undone, 5 change things and 4 only read.
- Reads private data · 0
- Reads text others write · 4
- Can send data out · 1
- 2 findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here does something that can't be undone. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the pSEO Engine MCP server can do
The pSEO Engine MCP server is published by quantumcx.net, a domain the MCP Registry verified. It has 10 tools. It can do things that cannot be undone, such as sending, paying or publishing (seo_publish) and create or change data (5 tools: seo_project_create, seo_project_connect_ai, seo_research_start, seo_content_generate and 1 more), but cannot delete data. 4 tools only read.
4 tools bring in text other people can write (seo_research_start, seo_content_generate, seo_audit_start and 1 more); 1 tool can send data out of your system (seo_publish).
The fixed checks matched 2 findings (tool-shadowing). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 18, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
10 tools
Can't be undone 1Claude Code: ask
seo_publishSYNCHRONOUS.Reads text others writeCan send data outNo findings
Why it is in this group
- The name "seo_publish" says "publish": a word for a change that another call does not undo.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe name "seo_publish" says "publish": it sends or publishes something to other people.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
Changes things 5Claude Code: ask
seo_audit_startASYNCHRONOUS.Reads text others writeNo findings
Why it is in this group
- The name "seo_audit_start" says "start": a word for a change.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
seo_content_generateASYNCHRONOUS.Reads text others writeNo findings
Why it is in this group
- The name "seo_content_generate" says "generate": a word for a change.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
seo_project_connect_aiStores the AI provider key this project's generation, audits and research run on — BYOK: the tokens bill YOUR provider account, not ours.No findings
Why it is in this group
- The description's first verb is "store": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
seo_project_createCreates a new programmatic-SEO project and returns its projectId.1 finding
Why it is in this group
- The name "seo_project_create" says "create": a word for a change.
Findings
- Warn
The description contains "every other tool", wording about other tools or servers.
What this check looks forMatched text
description: "...hen seo_project_list comes back empty — every other tool needs a projectId and a new account has..."
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
seo_research_startASYNCHRONOUS.Reads text others writeNo findings
Why it is in this group
- The name "seo_research_start" says "start": a word for a change.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
Only reads 4Show 4 read-only tools
seo_job_statusReturns the most recent background job for a project: type, status (QUEUED/RUNNING/COMPLETED/FAILED/CANCELLED), progress counters and the last log line.No findings
Why it is in this group
- The name "seo_job_status" says "status": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
seo_project_getReturns one project's settings and whether it is configured enough to generate content (needs both a field mapping and a content spec).No findings
Why it is in this group
- The name "seo_project_get" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
seo_project_listLists every programmatic-SEO project this API key can act on, with id, name, slug, custom domain and page count.1 finding
Why it is in this group
- The name "seo_project_list" says "list": a word for reading.
Findings
- Warn
The description contains "every other tool", wording about other tools or servers.
What this check looks forMatched text
description: "...count. Call this FIRST in any session — every other tool needs a projectId from here, and ids ca..."
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
seo_rows_listReturns a page of rows (individual generated pages) with slug, target keyword and status.No findings
Why it is in this group
- The name "seo_rows_list" says "list": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write4
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:16 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 6
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 6 tools that change things (1 irreversible, 5 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://pseo.quantumcx.net/api/agent/mcp: tools/list returned 10 tools to an anonymous client, including seo_publish (irreversible), seo_project_create (write), seo_project_connect_ai (write), seo_research_start (write), seo_content_generate (write) and 1 more
Findings
Matches of fixed checks, with the text they matched.
- Warnseo_project_list
The description contains "every other tool", wording about other tools or servers.
What this check looks forMatched text
description: "...count. Call this FIRST in any session — every other tool needs a projectId from here, and ids ca..."
The description contains "every other tool", wording about other tools or servers.
What this check looks forMatched text
description: "...hen seo_project_list comes back empty — every other tool needs a projectId and a new account has..."
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http pseo-engine https://pseo.quantumcx.net/api/agent/mcp --header 'X-Agent-API-Key: <your-x-agent-api-key>'claude mcp add --transport http pseo-engine https://pseo.quantumcx.net/api/agent/mcp --header 'X-Agent-API-Key: <your-x-agent-api-key>'Run in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__pseo-engine__seo_project_list",
"mcp__pseo-engine__seo_project_get",
"mcp__pseo-engine__seo_rows_list",
"mcp__pseo-engine__seo_job_status"
],
"ask": [
"mcp__pseo-engine__seo_project_create",
"mcp__pseo-engine__seo_project_connect_ai",
"mcp__pseo-engine__seo_research_start",
"mcp__pseo-engine__seo_content_generate",
"mcp__pseo-engine__seo_audit_start",
"mcp__pseo-engine__seo_publish"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as pseo-engine. Review it before you use it.
Capability tags behind 4 rules
- mcp__pseo-engine__seo_research_start untrusted-input
- mcp__pseo-engine__seo_content_generate untrusted-input
- mcp__pseo-engine__seo_audit_start untrusted-input
- mcp__pseo-engine__seo_publish untrusted-input, outbound
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/net.quantumcx/pseo-engine/verify?hash=3b8f43b2a4ed2739eb7573f4eff15688d06583e4c165ec9e4ad3e65fa0b12b4e" | jq -e '.changed == false'Pinned hash 3b8f43b2a4ed, from Nov 18, 2026, 20:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/net.quantumcx/pseo-engine/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/net.quantumcx/pseo-engine)Source: MCP Registry. Synced Oct 21, 2026, 18:53 UTC.
pSEO Engine MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the pSEO Engine MCP server safe?
- No scan can promise that. What its definitions show: 10 tools, 6 of which can change, send or delete something, and 2 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the pSEO Engine MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the pSEO Engine MCP server do things that cannot be undone?
- Yes. 1 tool can send, pay, publish or merge: seo_publish.
What tools does the pSEO Engine MCP server have?
- 10 tools: 1 irreversible, 5 write, 4 read. seo_publish, seo_project_create, seo_project_connect_ai, seo_research_start, seo_content_generate, seo_audit_start, seo_project_list, seo_project_get and 2 more.
Does the pSEO Engine MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the pSEO Engine MCP server send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): seo_publish.
Has the pSEO Engine MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 18, 2026.