# ChimpanSEO (remote · chimpanseo.app)

Generate GEO/AEO-optimized articles and publish them to WordPress from your AI agent.

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

## Components

- remote · `chimpanseo.app`: 91/100 (this document), [markdown](https://verifymcp.io/servers/app-chimpanseo-chimpanseo/api-mcp.md), [page](https://verifymcp.io/servers/app-chimpanseo-chimpanseo/api-mcp)

## Channel facts

- Endpoint: `https://chimpanseo.app/api/mcp`
- Transports: `streamable-http`
- Auth: `required (not validated)`
- Version: `1.0.1`

## 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**: 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**: 80/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 1218 tokens (~93/item across 13 items; 13 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 92/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 76% 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.
  - All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 13 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 ChimpanSEO MCP server?

ChimpanSEO is a hosted endpoint at https://chimpanseo.app/api/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 app-chimpanseo-chimpanseo 'https://chimpanseo.app/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "app-chimpanseo-chimpanseo": {
      "url": "https://chimpanseo.app/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "app-chimpanseo-chimpanseo": {
      "type": "http",
      "url": "https://chimpanseo.app/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.app-chimpanseo-chimpanseo]
url = "https://chimpanseo.app/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "app-chimpanseo-chimpanseo": {
      "type": "remote",
      "url": "https://chimpanseo.app/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add app-chimpanseo-chimpanseo --url 'https://chimpanseo.app/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  app-chimpanseo-chimpanseo:
    url: "https://chimpanseo.app/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "app-chimpanseo-chimpanseo": {
      "Transport": "http",
      "Url": "https://chimpanseo.app/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add app-chimpanseo-chimpanseo -t streamable-http -u 'https://chimpanseo.app/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "app-chimpanseo-chimpanseo": {
      "type": "http",
      "url": "https://chimpanseo.app/api/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 91, 0)

- [security] Stability: 0.97 → pass

### 2026-11-04 (score 91, +1)

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

### 2026-11-01 (score 90, +1)

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

### 2026-10-30 (score 89, +1)

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

### 2026-10-28 (score 88, +1)

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

### 2026-10-27 (score 87, 0)

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

### 2026-10-26 (score 87, +1)

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

### 2026-10-24 (score 86, +1)

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

## MCP tools (13)

### `list_sites` (~37 tokens)

List connected sites

List the WordPress/Framer/Webflow sites connected to this ChimpanSEO account, with id, name, url, platform and language.

### `get_usage` (~38 tokens)

Get plan usage and limits

Check the current plan, monthly article limit, articles used this month and articles remaining — call this before generating to use the quota consciously instead of guessing.

### `list_articles` (~40 tokens)

List recent articles

List the most recent articles generated on this account, with title, status, site and link.

Input parameters:

- `limit` (integer): Max number of articles to return

### `get_article` (~79 tokens)

Get article content

Fetch one article's full HTML content and metadata by id — list_articles deliberately omits content to stay compact, use this to actually read what was generated (e.g. after generate_article or refresh_article, or before deciding whether to publish it).

Input parameters:

- `articleId` (string, required): The article id, from list_articles, generate_article or get_generation_status

### `suggest_topics` (~150 tokens)

Suggest article topics

Generates topic suggestions for a site's next articles, using the same logic as the dashboard's topic generator — biased toward an experiment/case-study angle for a share of the results, and informed by the site's differentiators if set, rather than generic keyword-chasing titles. Fast (a few seconds, not a background job) — use this before generate_article or schedule_article instead of inventing topics yourself.

Input parameters:

- `count` (integer): How many topic suggestions to generate
- `creativity` (integer): 0 = safe/proven angles, 100 = more experimental angles
- `siteId` (string, required): Target site id (from list_sites) — determines language, tone, SEO tags and differentiators used

### `list_scheduled_articles` (~67 tokens)

List scheduled articles

List scheduled_article slots (past and future) — topic, target date, status, site. Use this before schedule_article to see what's already queued and avoid duplicating dates/topics.

Input parameters:

- `limit` (integer)
- `siteId` (string): Filter to one site's slots only

### `audit_site` (~102 tokens)

Run a technical SEO audit

Fetches the site's homepage and checks the on-page technical SEO factors that matter for both Google and AI citation — title/meta tags, canonical, H1, mobile viewport, HTTPS, Open Graph, JSON-LD structured data, image alt coverage, indexability, response time. Each finding includes a concrete tip, not just pass/fail. Fast (a few seconds) — no background job needed.

Input parameters:

- `siteId` (string, required): Site id, from list_sites

### `generate_article` (~191 tokens)

Generate a GEO/AEO article

Starts generating a new SEO/GEO-optimized article via AI for a given topic and site. Counts against the account's monthly article quota, same as generating from the dashboard. Does NOT publish it — call publish_article separately once you're happy with it.

ASYNC: this returns a jobId immediately, it does NOT wait for the article. Generation typically takes 1-3 minutes (reasoning model, non-streaming) — poll get_generation_status with the returned jobId every ~15-20s until status is "ready" or "error". (Older integrations that awaited this call directly would hit their own client's default request timeout, typically 60s, long before generation finished — this is why it's async now.)

Input parameters:

- `siteId` (string): Target site id (from list_sites) — determines language, tone and SEO tags used
- `topic` (string, required): The article topic or working title

### `get_generation_status` (~76 tokens)

Check generation status

Poll the status of a generate_article or refresh_article call by jobId. Returns status: "pending" (still working), "ready" (done — includes articleId, title, excerpt, charCount), or "error" (includes the error message).

Input parameters:

- `jobId` (string, required): The jobId returned by generate_article

### `refresh_article` (~141 tokens)

Refresh an existing article

Rewrites an existing article to be current and more SEO/AEO-optimized — updates dates/stats/examples, improves headings, adds a FAQ section, adds 300+ words. Same action as the dashboard's "Migliora & aggiorna" button. If the article is already published to WordPress, the refreshed version is automatically re-published there too (title and WordPress status unchanged); otherwise only ChimpanSEO's own copy is updated.

ASYNC: returns a jobId immediately — poll get_generation_status with it, typically ready in 1-4 minutes.

Input parameters:

- `articleId` (string, required): The article id to refresh, from list_articles

### `publish_article` (~92 tokens)

Publish an article to WordPress

Publish (or save as draft) a previously generated article to its WordPress site. Only works for WordPress sites — Framer/Webflow sites are copy-paste only (Beta) and are not supported here.

Input parameters:

- `articleId` (string, required): The article id, from generate_article or list_articles
- `siteId` (string, required): The WordPress site id to publish to
- `status` (string)

### `schedule_article` (~118 tokens)

Schedule a future article

Schedule a topic to be generated and auto-published at a future date/time on a WordPress site — the same editorial calendar the dashboard uses. Requires a plan with scheduling enabled.

Input parameters:

- `dualLanguage` (boolean): Also publish an Italian translation alongside the original
- `publishStatus` (string)
- `scheduledFor` (string, required): ISO 8601 date-time in the future, e.g. 2026-08-01T09:00:00Z
- `siteId` (string, required)
- `topic` (string, required)

### `cancel_scheduled_article` (~87 tokens)

Cancel a scheduled article

Removes a slot from the editorial calendar, from list_scheduled_articles. Same as deleting it from the dashboard calendar — works regardless of the slot's current status, so double-check it hasn't already published if that matters (see list_scheduled_articles' wp_post_id/article_id fields).

Input parameters:

- `scheduledArticleId` (string, required): The slot id, from list_scheduled_articles or schedule_article

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/app-chimpanseo-chimpanseo/api-mcp#diagnostics

## Score history

- 2026-11-05: 91
- 2026-11-04: 91
- 2026-11-03: 90
- 2026-11-02: 90
- 2026-11-01: 90
- 2026-10-31: 89
- 2026-10-30: 89
- 2026-10-29: 88
- 2026-10-28: 88
- 2026-10-27: 87
- 2026-10-26: 87
- 2026-10-25: 86
- 2026-10-24: 86
- 2026-10-23: 85
- 2026-10-22: 85
- 2026-10-21: 84
- 2026-10-20: 84
- 2026-10-19: 83
- 2026-10-18: 83
- 2026-10-17: 83
- 2026-10-16: 82
- 2026-10-15: 82
- 2026-10-14: 81
- 2026-10-13: 81
- 2026-10-12: 80
- 2026-10-10: 79
- 2026-10-09: 79

## Common questions

### What is the ChimpanSEO MCP server?

ChimpanSEO is an MCP server listed in the public MCP registry as app.chimpanseo/chimpanseo. Generate GEO/AEO-optimized articles and publish them to WordPress from your AI agent. This page covers its hosted endpoint (https://chimpanseo.app/api/mcp).

### Is the ChimpanSEO MCP server safe to use?

ChimpanSEO scores 91 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 ChimpanSEO MCP server expose?

ChimpanSEO exposes 13 tools: list_sites, get_usage, list_articles, get_article, suggest_topics, and 8 more. Their descriptions and schemas cost roughly 1,218 tokens of context every time the server is loaded.

### Does the ChimpanSEO MCP server require authentication?

Yes. ChimpanSEO 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 ChimpanSEO MCP server still maintained?

ChimpanSEO 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://chimpanseo.app/api/mcp
- Authorisation metadata: https://chimpanseo.app/.well-known/oauth-protected-resource/api/mcp
- Website: https://chimpanseo.app/mcp
- Changelog RSS feed: https://verifymcp.io/servers/app-chimpanseo-chimpanseo/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/app-chimpanseo-chimpanseo/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/app-chimpanseo-chimpanseo/api-mcp