ChimpanSEO
REMOTE · CHIMPANSEO.APP
Generate GEO/AEO-optimized articles and publish them to WordPress from your AI agent.
Available components
Last scanned (18 minutes ago)
Scores higher than 98% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Marketing and SEO
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 Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1218 tokens (~93/item across 13 items; 13 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage92
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 76% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 13 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
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.
- 5 Nov 26 0
- Stability: 0.97 → pass security
- 4 Nov 26 +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.
- 1 Nov 26 +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.
- 30 Oct 26 +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.
- 28 Oct 26 +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.
- 27 Oct 26 0
- Tool “generate_article” rewrote its description, which is the text the model reads security
- 26 Oct 26 +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.
- 24 Oct 26 +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.
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 5 Nov 2026 · Probed https://chimpanseo.app/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=chimpanseo.app | CN=YR1,O=Let's Encrypt,C=US | 13 Oct 2026 | 11 Jan 2027 | RSA 2048 | SHA256-RSA | 6de3f43300bb60b2516edefdb6f38cf42dd |
| SANs: chimpanseo.app | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| 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 chimpanseo.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| chimpanseo.app. | 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 |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
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://chimpanseo.app/api/mcp | Verified | 200 | |
| http (plaintext) | http://chimpanseo.app/api/mcp | HTTPS enforced | 308 | https://chimpanseo.app/api/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 →
audit_site Run a technical SEO audit ~102
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.
| Name | Type | Req | Description |
|---|---|---|---|
| siteId | string | yes | Site id, from list_sites |
No output schema declared.
No examples provided.
cancel_scheduled_article Cancel a scheduled article ~87
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).
| Name | Type | Req | Description |
|---|---|---|---|
| scheduledArticleId | string | yes | The slot id, from list_scheduled_articles or schedule_article |
No output schema declared.
No examples provided.
generate_article Generate a GEO/AEO article ~191
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.)
| Name | Type | Req | Description |
|---|---|---|---|
| siteId | string | – | Target site id (from list_sites) — determines language, tone and SEO tags used |
| topic | string | yes | The article topic or working title |
No output schema declared.
No examples provided.
get_article Get article content ~79
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).
| Name | Type | Req | Description |
|---|---|---|---|
| articleId | string | yes | The article id, from list_articles, generate_article or get_generation_status |
No output schema declared.
No examples provided.
get_generation_status Check generation status ~76
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).
| Name | Type | Req | Description |
|---|---|---|---|
| jobId | string | yes | The jobId returned by generate_article |
No output schema declared.
No examples provided.
get_usage Get plan usage and limits ~38
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_articles List recent articles ~40
List the most recent articles generated on this account, with title, status, site and link.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max number of articles to return |
No output schema declared.
No examples provided.
list_scheduled_articles List scheduled articles ~67
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| siteId | string | – | Filter to one site's slots only |
No output schema declared.
No examples provided.
list_sites List connected sites ~37
List the WordPress/Framer/Webflow sites connected to this ChimpanSEO account, with id, name, url, platform and language.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
publish_article Publish an article to WordPress ~92
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.
| Name | Type | Req | Description |
|---|---|---|---|
| articleId | string | yes | The article id, from generate_article or list_articles |
| siteId | string | yes | The WordPress site id to publish to |
| status | string | – | – |
No output schema declared.
No examples provided.
refresh_article Refresh an existing article ~141
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.
| Name | Type | Req | Description |
|---|---|---|---|
| articleId | string | yes | The article id to refresh, from list_articles |
No output schema declared.
No examples provided.
schedule_article Schedule a future article ~118
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.
| Name | Type | Req | Description |
|---|---|---|---|
| dualLanguage | boolean | – | Also publish an Italian translation alongside the original |
| publishStatus | string | – | – |
| scheduledFor | string | yes | ISO 8601 date-time in the future, e.g. 2026-08-01T09:00:00Z |
| siteId | string | yes | – |
| topic | string | yes | – |
No output schema declared.
No examples provided.
suggest_topics Suggest article topics ~150
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.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | How many topic suggestions to generate |
| creativity | integer | – | 0 = safe/proven angles, 100 = more experimental angles |
| siteId | string | yes | Target site id (from list_sites) — determines language, tone, SEO tags and differentiators used |
No output schema declared.
No examples provided.
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.
remote · chimpanseo.app
claude mcp add --transport http app-chimpanseo-chimpanseo 'https://chimpanseo.app/api/mcp'
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.