Skip to content

ChimpanSEO MCP server

app.chimpanseo/chimpanseochimpanseo.appstreamable-httpv1.0.1Scanned

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

13 tools: 3 can delete or cancel things, 3 change things and 7 only read.

Tools: 3 delete, 0 irreversible, 3 write, 7 read.
  • Reads private data · 0
  • Reads text others write · 5
  • Can send data out · 1
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

3 tools here can delete or cancel things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

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 ChimpanSEO MCP server can do

The ChimpanSEO MCP server is published by chimpanseo.app, a domain the MCP Registry verified. It has 13 tools. It can delete or cancel things (3 tools: refresh_article, publish_article and cancel_scheduled_article) and create or change data (3 tools: suggest_topics, generate_article and schedule_article). 7 tools only read.

5 tools bring in text other people can write (list_sites, get_article, audit_site and 2 more); 1 tool can send data out of your system (publish_article).

The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.

Last scanned Nov 12, 2026, version 1.0.1.

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.

13 tools

Deletes or cancels 3Claude Code: deny
  • cancel_scheduled_articleRemoves a slot from the editorial calendar, from list_scheduled_articles.No findings

    Why it is in this group

    • The name "cancel_scheduled_article" says "cancel": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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).

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: false
  • publish_articlePublish (or save as draft) a previously generated article to its site: WordPress, or a Webflow/Framer site connected with an API token or key (Framer publishing deploys the whole p…Reads text others writeCan send data outNo findings

    Why it is in this group

    • The name "publish_article" says "publish": a word for a change that another call does not undo.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe name "publish_article" says "publish": it sends or publishes something to other people.
    Description, as the server wrote it
    Publish (or save as draft) a previously generated article to its site: WordPress, or a Webflow/Framer site connected with an API token or key (Framer publishing deploys the whole project, so unpublished changes in the project go live too). Sites connected for copy-paste only are not supported here.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: true
  • refresh_articleRewrites an existing article to be current and more SEO/AEO-optimized — updates dates/stats/examples, improves headings, adds a FAQ section, adds 300+ words.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it destructive (destructiveHint: true).

    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
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: true
Changes things 3Claude Code: ask
  • generate_articleStarts generating a new SEO/GEO-optimized article via AI for a given topic and site.No findings

    Why it is in this group

    • The name "generate_article" says "generate": a word for a change.
    Description, as the server wrote it
    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-2 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.)

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • schedule_articleSchedule a topic to be generated and auto-published at a future date/time on a WordPress site — the same editorial calendar the dashboard uses.No findings

    Why it is in this group

    • The name "schedule_article" says "schedule": a word for a change.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • suggest_topicsGenerates 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 re…1 finding

    Why it is in this group

    • The description's first verb is "generate": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "suggest_topics" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The description's first verb is "generate": a word for a change.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
Only reads 7Show 7 read-only tools
  • audit_siteFetches 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 …Reads text others writeNo findings

    Why it is in this group

    • The description's first verb is "fetch": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "fetch" and "http": it reads web pages, which anyone can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • get_articleFetch 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.Reads text others writeNo findings

    Why it is in this group

    • The name "get_article" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "fetch" and "html": it reads web pages, which anyone can write.
    Description, as the server wrote it
    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).

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_generation_statusPoll the status of a generate_article or refresh_article call by jobId.No findings

    Why it is in this group

    • The name "get_generation_status" says "get": a word for reading.
    Description, as the server wrote it
    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).

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_usageCheck 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.No findings

    Why it is in this group

    • The name "get_usage" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_articlesList the most recent articles generated on this account, with title, status, site and link.No findings

    Why it is in this group

    • The name "list_articles" says "list": a word for reading.
    Description, as the server wrote it
    List the most recent articles generated on this account, with title, status, site and link.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_scheduled_articlesList scheduled_article slots (past and future) — topic, target date, status, site.No findings

    Why it is in this group

    • The name "list_scheduled_articles" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_sitesList the WordPress/Framer/Webflow sites connected to this ChimpanSEO account, with id, name, url, platform and language.Reads text others writeNo findings

    Why it is in this group

    • The name "list_sites" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "list" and "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    List the WordPress/Framer/Webflow sites connected to this ChimpanSEO account, with id, name, url, platform and language.

    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 write5
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.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:29 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 (3 destructive, 3 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://chimpanseo.app/api/mcp: tools/list returned 13 tools to an anonymous client, including refresh_article (destructive), publish_article (destructive), cancel_scheduled_article (destructive), suggest_topics (write), generate_article (write) and 1 more

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "suggest_topics" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The description's first verb is "generate": a word for a change.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools2 changed.~2 changedView diff
  2. Tools1 changed.~1 changedView diff

Install

Pinned to version 1.0.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http chimpanseo https://chimpanseo.app/api/mcp --header 'Authorization: <your-authorization>'
claude mcp add --transport http chimpanseo https://chimpanseo.app/api/mcp --header 'Authorization: <your-authorization>'

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.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__chimpanseo__list_sites",
      "mcp__chimpanseo__get_usage",
      "mcp__chimpanseo__list_articles",
      "mcp__chimpanseo__get_article",
      "mcp__chimpanseo__list_scheduled_articles",
      "mcp__chimpanseo__audit_site",
      "mcp__chimpanseo__get_generation_status"
    ],
    "ask": [
      "mcp__chimpanseo__suggest_topics",
      "mcp__chimpanseo__generate_article",
      "mcp__chimpanseo__schedule_article"
    ],
    "deny": [
      "mcp__chimpanseo__refresh_article",
      "mcp__chimpanseo__publish_article",
      "mcp__chimpanseo__cancel_scheduled_article"
    ]
  }
}

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 chimpanseo. Review it before you use it.

Capability tags behind 5 rules
  • mcp__chimpanseo__list_sites untrusted-input
  • mcp__chimpanseo__get_article untrusted-input
  • mcp__chimpanseo__audit_site untrusted-input
  • mcp__chimpanseo__refresh_article untrusted-input
  • mcp__chimpanseo__publish_article 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/app.chimpanseo/chimpanseo/verify?hash=2d6df1bcd587f776ebcf0b2a816d3343424ea21279c80f65314d5dcf135ffb1b" | jq -e '.changed == false'

Pinned hash 2d6df1bcd587, from Nov 12, 2026, 00:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/app.chimpanseo/chimpanseo/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for app.chimpanseo/chimpanseo
[![Anlyon Radar](https://radar.anlyon.com/badge/app.chimpanseo/chimpanseo.svg)](https://radar.anlyon.com/servers/app.chimpanseo/chimpanseo)

Source: MCP Registry. Synced Oct 21, 2026, 17:44 UTC.

ChimpanSEO MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the ChimpanSEO MCP server safe?

No scan can promise that. What its definitions show: 13 tools, 6 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the ChimpanSEO MCP server delete data?

Yes. 3 tools can delete, cancel or revoke something: refresh_article, publish_article and cancel_scheduled_article.

Can the ChimpanSEO 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 ChimpanSEO MCP server have?

13 tools: 3 destructive, 3 write, 7 read. refresh_article, publish_article, cancel_scheduled_article, suggest_topics, generate_article, schedule_article, list_sites, get_usage and 5 more.

Does the ChimpanSEO MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the ChimpanSEO 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): publish_article.

Has the ChimpanSEO MCP server changed its tools?

Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 12, 2026. Every change is on this page and in its Atom feed.