Corpus Plan MCP server
co.corpushq.plan/corpus-planplan.corpushq.costreamable-httpv0.1.0Scanned
Free SEO/GEO audits of public websites and AI answer-engine citation checks. No login or API key.
6 tools: 2 change things and 4 only read.
- Reads private data · 1
- Reads text others write · 2
- Can send data out · 2
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
2 tools here change things. Govern them.
- 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 Corpus Plan MCP server can do
The Corpus Plan MCP server is published by plan.corpushq.co, a domain the MCP Registry verified. It has 6 tools. It can create or change data (2 tools: run_audit and check_citations), but cannot delete data. 4 tools only read.
1 tool reads private data (describe_corpus_plan); 2 tools bring in text other people can write (run_audit and check_citations); 2 tools can send data out of your system (run_audit and check_citations). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 12, 2026, version 0.1.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.
6 tools
Changes things 2Claude Code: ask
check_citationsUse this when the user asks whether AI answer engines cite their website.Reads text others writeCan send data outNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Description, as the server wrote it Use this when the user asks whether AI answer engines cite their website. Asks one answer engine (Perplexity) three customer-style questions written from the site's own pages and returns each question, the sites it cited, whether this site was one of them, and the date. A result for the same site from the last 24 hours is returned again instead of asking again.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
run_auditUse this when the user wants a website audited.Reads text others writeCan send data outNo findings
Why it is in this group
- The name "run_audit" says "run": 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.
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Description, as the server wrote it Use this when the user wants a website audited. Starts Corpus Plan's free audit of a public website (up to 20 pages of that site) and returns the overall score, the five pillar scores including AI citability, the top three issues, the Product information document and the workspace link where the user can save the report. The same site audited from an AI assistant in the last 24 hours is returned again instead of re-crawled. If the result says running, call again with the same url.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
Only reads 4Show 4 read-only tools
describe_corpus_planReturn Corpus Plan's public SEO/GEO audit capabilities, product links, and safety notes.Reads private dataNo findings
Why it is in this group
- The name "describe_corpus_plan" says "describe": a word for reading.
What it can reach
- private-dataThe description's first sentence says "return" and "note": it reads notes.
Description, as the server wrote it Return Corpus Plan's public SEO/GEO audit capabilities, product links, and safety notes.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_public_reportRead the stored public audit report for a saved Corpus Plan share slug.No findings
Why it is in this group
- The name "get_public_report" says "get": a word for reading.
Description, as the server wrote it Read the stored public audit report for a saved Corpus Plan share slug. Unsaved reports require saving through the website first. Only public report facts are returned.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_report_progressRead the current status and progress lines for a Corpus Plan audit behind a public report slug.No findings
Why it is in this group
- The name "get_report_progress" says "get": a word for reading.
Description, as the server wrote it Read the current status and progress lines for a Corpus Plan audit behind a public report slug.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_report_recommendationsReturn observed findings ordered critical, major, minor, then other severities, with existing fix hints.No findings
Why it is in this group
- The name "get_report_recommendations" says "get": a word for reading.
Description, as the server wrote it Return observed findings ordered critical, major, minor, then other severities, with existing fix hints. Requires a saved public share slug, not private account access. No new crawl, invented findings or automatic fixes.
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.
4 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 private-data tool breaks every one.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write2
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out2
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
{
"permissions": {
"deny": [
"mcp__corpus-plan__describe_corpus_plan"
]
}
}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, 18:32 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
- 2
- 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
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://plan.corpushq.co/mcp: tools/list returned 6 tools to an anonymous client, including run_audit (write), check_citations (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools1 added, 1 changed.+1 added~1 changedView diff
- Added:get_report_recommendationsOnly reads
- Changed:run_auditChanges thingsdescription
Install
Pinned to version 0.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http corpus-plan https://plan.corpushq.co/mcpclaude mcp add --transport http corpus-plan https://plan.corpushq.co/mcpRun 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__corpus-plan__describe_corpus_plan",
"mcp__corpus-plan__get_public_report",
"mcp__corpus-plan__get_report_progress",
"mcp__corpus-plan__get_report_recommendations"
],
"ask": [
"mcp__corpus-plan__run_audit",
"mcp__corpus-plan__check_citations"
],
"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 corpus-plan. Review it before you use it.
Capability tags behind 3 rules
- mcp__corpus-plan__describe_corpus_plan private-data
- mcp__corpus-plan__run_audit untrusted-input, outbound
- mcp__corpus-plan__check_citations 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/co.corpushq.plan/corpus-plan/verify?hash=6a36a535a1c38005935cc3107e37de057365cecd63e05633aab2b0e37db4ad55" | jq -e '.changed == false'Pinned hash 6a36a535a1c3, from Nov 12, 2026, 09:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/co.corpushq.plan/corpus-plan/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/co.corpushq.plan/corpus-plan)Source: MCP Registry. Synced Oct 21, 2026, 17:46 UTC.
Corpus Plan MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Corpus Plan MCP server safe?
- No scan can promise that. What its definitions show: 6 tools, 2 of which can change, send or delete something, and 0 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 Corpus Plan MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Corpus Plan MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Corpus Plan MCP server have?
- 6 tools: 2 write, 4 read. run_audit, check_citations, describe_corpus_plan, get_public_report, get_report_progress and get_report_recommendations.
Does the Corpus Plan MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Corpus Plan MCP server send data to outside services?
- 2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): run_audit and check_citations.
Has the Corpus Plan MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 12, 2026. Every change is on this page and in its Atom feed.