Fetch and follow the instructions at https://qamcp.dev/setup.md to test my MCP server.Your AI finds your server in your project, tests it with QAmcp, explains what's wrong in plain words, fixes it with your OK, and tests again. Read the instructions
Directory / AI SEO Crew
AI SEO Crew
by aiseocrew.com · https://www.aiseocrew.com/mcp
AI agents that research, write and publish SEO articles on your website, from your AI assistant.
Partial: 9 of 11 checks · 8 Nov 2026
At a glance
- Runs where
- On their server. What you send to it goes to them.
- What you need
- Nothing: it answered without a login
- Tools
- 13 tools
- Its own safety labels
- 8 read-only, 2 labeled as deleting or destroying, 3 labeled as changing things
- Memory it takes
- About 2,200 tokens of your AI's memory, just for its tool descriptions
Tokens are an estimate: the characters in its tool names, descriptions and inputs, divided by 4. The exact number depends on your AI model. Safety labels are what the server says about itself. From our latest test, 8 Nov 2026.
Is AI SEO Crew MCP server safe?
- None of the hidden-instruction wordings we know were found in its 13 tool descriptions.
- Its error messages showed no secrets or internal details.
- 8 of its 13 tools are labeled read-only; the others may change or send things.
- Overall it scored 84/100 on 8 Nov 2026.
A test can only see what the server shows from outside, not what it does with your data behind the scenes. Connect servers from makers you trust.
What this test does not check
- Its source code and packages.
- What a tool quietly does behind the scenes, such as writing a file or calling another service.
- Instructions hidden inside live tool answers. We only look for those in tool descriptions.
- Hidden instructions worded in a way our list doesn't know yet.
- Tools that could change something. Those are read, never run.
What QAmcp can and can't see · How to tell if an MCP server is safe · Hidden instructions · Prompt injection
Known security advisories
It lists no public code, so there is nothing to look up in GitHub Security Advisories or OSV.dev. QAmcp tests how a server behaves. It does not scan source code.
What it can do
13 tools, in the server's own words.
check_page_seoread-onlyChecks one public web page the way search engines see it: HTTP status, robots.txt and meta robots rules for Googlebot, Bingbot and AI crawlers (GPTBot, OAI-Sea…
find_keyword_ideasread-onlyReturns real searches people type into Google around a topic, from Google autocomplete, grouped into questions, comparisons, buying searches and others.
generate_llms_txtread-onlyReads a website's homepage, navigation and sitemap, then writes an llms.txt file (the markdown summary some AI tools read) that the owner can upload to the sit…
list_sitesread-onlyLists the websites in the user's AI SEO Crew account with their status (plan being built, ready), article counts, where the crew publishes, and the account pla…
add_siteAdds a website to the user's AI SEO Crew account and starts building its SEO plan: the crew reads the site, works out what the business sells and plans article…
get_seo_planread-onlyReturns the SEO plan of one site: progress while the crew is still building it, then the planned articles in writing order with their target Google search, mon…
add_topicAdds a Google search the user wants to rank for to the top of a site's SEO plan, with an optional article title.
list_articlesread-onlyLists a site's articles by status: written (waiting for approval), in_progress, published, or failed.
get_articleread-onlyReturns one article: title, status, meta description, target search, the full text in Markdown, its sources and, once published, its URL.
write_articleAsks the crew to research and write one SEO blog post from the site's plan right away, sourced and in the site's own style, instead of waiting for its slot.
publish_articlePublishes one written article to the user's live website through its connected platform (WordPress, Webflow, Wix, Framer, Shopify, GitHub or webhook), then res…
skip_articleRemoves a planned, failed or written (unpublished) article from a site's plan so the crew never writes or publishes it.
get_resultsread-onlyReturns Google Search Console results for a site over the last 28 days: total clicks and impressions, and the published articles with the most clicks.
Test results
Safe mode: only tools labeled read-only were run. How the test works
- !Ready for the newest MCP versionnote
1 warning
- !Uses an older MCP version (2025-11-25). It works today, but it isn't on the July 2026 version (2026-07-28) yet.
- !Every tool is describednote
5 warnings
- !add_topic: Inputs with no description: site_id
- !list_articles: Inputs with no description: site_id, offset
- !get_article: Inputs with no description: article_id
- !skip_article: Inputs with no description: article_id
- !get_results: Inputs with no description: site_id
- ✓ConnectsConnected in 1.4 spass
- ✓Lists its toolsFound 13 toolspass
- ✓Tools are labeled safe or dangerousEvery tool has a safety labelpass
- ✓No known hidden instructionsNone of the hidden-instruction wordings we know were found in tool descriptions. New wordings can get past this check.pass
- ✓Fast enoughpass
All good
- ✓Connecting took 1.4 s
- ✓Listing tools took 151 ms
- ✓No secrets leakedChecked 21 error messages: no secrets or internal detailspass
- ✓Follows MCP best practices (not scored yet)Tool names, safety labels and tool list size follow the MCP guidepass
- –Tools work with good inputsnot tested
Not tested
- –check_page_seo: Needs you to sign in, so it was not tested (not counted against the server)
- –find_keyword_ideas: Needs you to sign in, so it was not tested (not counted against the server)
- –generate_llms_txt: Needs you to sign in, so it was not tested (not counted against the server)
- –get_seo_plan: Needs you to sign in, so it was not tested (not counted against the server)
- –list_articles: Needs you to sign in, so it was not tested (not counted against the server)
- –get_article: Needs you to sign in, so it was not tested (not counted against the server)
- –get_results: Needs you to sign in, so it was not tested (not counted against the server)
- –list_sites: Not run: labeled read-only, but its description says "publishes", which usually means it changes something. Skipped to be safe: if it only reads, a clearer description helps AI apps too, or test again with --owner
- and 5 more
- –Bad inputs give a clean errornot tested
Not tested
- –check_page_seo: Needs you to sign in, so bad inputs were not tested
- –find_keyword_ideas: Needs you to sign in, so bad inputs were not tested
- –generate_llms_txt: Needs you to sign in, so bad inputs were not tested
- –get_seo_plan: Needs you to sign in, so bad inputs were not tested
- –list_articles: Needs you to sign in, so bad inputs were not tested
- –get_article: Needs you to sign in, so bad inputs were not tested
- –get_results: Needs you to sign in, so bad inputs were not tested
- –Tools work togetherNo safe tool returned data to start a chain from, so chains were not tested (not counted either way)not tested
Test it yourself
Free and open source. Same checks, same score.
npx qamcp-cli https://www.aiseocrew.com/mcpShow this score on GitHub
Free for every server in the directory. Paste this into your README: the badge shows the score from our latest test.
[](https://qamcp.dev/s/com-aiseocrew-www-ai-seo-crew.html)Score over time
- 8 Nov 202684
One test so far. New tests will show here.
Reviews
Coming soon: reviews from people who use AI SEO Crew, signed in with GitHub, one per person. Reviews never change the score.
QAmcp Monitor tests it every hour and emails you when it goes down, the score drops, a tool changes or a secret leaks. Free for 1 server, no card.
Have a concern, or want it removed? Ask us and we'll take it off the list. How the directory works