# Corpus Plan (remote · plan.corpushq.co)

Free SEO/GEO audits of public websites and AI answer-engine citation checks. No login or API key.

- Trust score: 82/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `plan.corpushq.co`: 82/100 (this document), [markdown](https://verifymcp.io/servers/co-corpushq-plan-corpus-plan/plan.md), [page](https://verifymcp.io/servers/co-corpushq-plan-corpus-plan/plan)

## Channel facts

- Endpoint: `https://plan.corpushq.co/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.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-11-05.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - 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**: 78/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 489 tokens (~97/item across 5 items; 5 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 57/100
  - Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 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 Corpus Plan MCP server?

Corpus Plan is a hosted endpoint at https://plan.corpushq.co/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 co-corpushq-plan-corpus-plan 'https://plan.corpushq.co/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "co-corpushq-plan-corpus-plan": {
      "url": "https://plan.corpushq.co/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "co-corpushq-plan-corpus-plan": {
      "type": "http",
      "url": "https://plan.corpushq.co/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.co-corpushq-plan-corpus-plan]
url = "https://plan.corpushq.co/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "co-corpushq-plan-corpus-plan": {
      "type": "remote",
      "url": "https://plan.corpushq.co/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add co-corpushq-plan-corpus-plan --url 'https://plan.corpushq.co/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  co-corpushq-plan-corpus-plan:
    url: "https://plan.corpushq.co/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "co-corpushq-plan-corpus-plan": {
      "Transport": "http",
      "Url": "https://plan.corpushq.co/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add co-corpushq-plan-corpus-plan -t streamable-http -u 'https://plan.corpushq.co/mcp'
```

### Other

```json
{
  "mcpServers": {
    "co-corpushq-plan-corpus-plan": {
      "type": "http",
      "url": "https://plan.corpushq.co/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-11-05 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-29 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-27 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-25 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-23 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-21 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (5)

### `describe_corpus_plan` (~28 tokens)

Describe Corpus Plan public audits

Return Corpus Plan's public SEO/GEO audit capabilities, product links, and safety notes.

### `get_public_report` (~60 tokens)

Read a saved shared audit report

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.

Input parameters:

- `slug` (string, required): The slug from a /r/{slug} Corpus Plan report URL.

### `get_report_progress` (~47 tokens)

Read shared audit progress

Read the current status and progress lines for a Corpus Plan audit behind a public report slug.

Input parameters:

- `slug` (string, required): The slug from a /r/{slug} Corpus Plan report URL.

### `run_audit` (~135 tokens)

Run a free website audit

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 with AI citability first, 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.

Input parameters:

- `url` (string, required): The website to audit, e.g. example.com or https://example.com.

### `check_citations` (~121 tokens)

Check which sites an AI answer engine cites

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.

Input parameters:

- `brand` (string): Optional business name, used to keep it out of the questions.
- `url` (string, required): The website to check, e.g. example.com.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/co-corpushq-plan-corpus-plan/plan#diagnostics

## Score history

- 2026-11-05: 82
- 2026-11-04: 81
- 2026-11-03: 81
- 2026-11-02: 81
- 2026-11-01: 80
- 2026-10-31: 80
- 2026-10-30: 79
- 2026-10-29: 79
- 2026-10-28: 78
- 2026-10-27: 78
- 2026-10-26: 77
- 2026-10-25: 77
- 2026-10-24: 76
- 2026-10-23: 76
- 2026-10-22: 75
- 2026-10-21: 75
- 2026-10-20: 74
- 2026-10-19: 74

## Common questions

### What is the Corpus Plan MCP server?

Corpus Plan is an MCP server listed in the public MCP registry as co.corpushq.plan/corpus-plan. Free SEO/GEO audits of public websites and AI answer-engine citation checks. No login or API key. This page covers its hosted endpoint (https://plan.corpushq.co/mcp).

### Is the Corpus Plan MCP server safe to use?

Corpus Plan scores 82 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 Corpus Plan MCP server expose?

Corpus Plan exposes 5 tools: describe_corpus_plan, get_public_report, get_report_progress, run_audit, check_citations. Their descriptions and schemas cost roughly 391 tokens of context every time the server is loaded.

### Does the Corpus Plan MCP server require authentication?

No. We connected to Corpus Plan without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Corpus Plan MCP server still maintained?

Corpus Plan is still listed as active in the MCP registry. We last reached this channel on 5 November 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://plan.corpushq.co/mcp
- Website: https://plan.corpushq.co/connectors/claude
- Changelog RSS feed: https://verifymcp.io/servers/co-corpushq-plan-corpus-plan/plan.xml
- Changelog JSON feed: https://verifymcp.io/servers/co-corpushq-plan-corpus-plan/plan.json
- HTML version of this page: https://verifymcp.io/servers/co-corpushq-plan-corpus-plan/plan