Our grade: 4 checks
Based on public data, not a full audit. See how we grade. Something changed? Request a re-grade.
Community rating
- 5 0
- 4 3
- 3 5
- 2 0
- 1 0
Trust in production
- Trust it - 25%
- With caveats - 63%
- Wouldn't - 13%
63% would recommend this server
How reviewers scored it
- Setup & docs 3.8
- Auth experience 3.5
- Reliability 3.4
- Maintainer responsiveness 3.8
Why it got a B
AgentSEO's own server for SEO research, from Joy Technologies, with 45 tools covering search results, keywords, backlinks, competitor domains, content briefs, local audits and rank tracking. You can use the hosted endpoint or the MIT-licensed npm package, which runs locally over stdio and calls the same API; the code behind the API and the hosted endpoint isn't public. Every tool except job status spends credits, and the README warns that repeating a call can charge again because the client sends no idempotency key. The free plan is 100 credits once, and paid plans start at $9 a month. Hint labels on the tools aren't access controls. The local package also loads a .env file from the folder it starts in, and that file can set the API address your key is sent to, so keep AGENTSEO_API_URL in your client config as the README shows. No advisories on record. Biggest deduction: every documented setup uses one API key with no scopes, kept in your client config, so it can do anything your account can until you revoke it. An OAuth endpoint also answers at /mcp/oauth, but the docs don't mention it and it offers no self-service client sign-up, so we scored the key.
How to connect
{
"mcpServers": {
"agentseo": {
"url": "https://www.agentseo.dev/mcp",
"headers": {
"Authorization": "Bearer sk_live_your_key",
"x-project-id": "client-alpha",
"x-workflow-id": "nightly-refresh"
}
}
}
}
claude mcp add --transport http agentseo https://www.agentseo.dev/mcp \
--header "Authorization: Bearer sk_live_your_key" \
--header "x-project-id: client-alpha" \
--header "x-workflow-id: nightly-refresh"
{
"mcpServers": {
"agentseo": {
"command": "npx",
"args": ["-y", "@agentseo/mcp-server"],
"env": {
"AGENTSEO_API_KEY": "sk_live_your_key",
"AGENTSEO_API_URL": "https://www.agentseo.dev/api/v1",
"AGENTSEO_PROJECT_ID": "client-alpha",
"AGENTSEO_WORKFLOW_ID": "nightly-refresh"
}
}
}
}
Is AgentSEO MCP Server safe?
Is AgentSEO MCP Server safe to use?
AgentSEO MCP Server grades B (solid, with minor gaps). Login is required, but access is coarse: one sign-in or key covers more than your agent needs, so grant the narrowest account you can. Upkeep is hard to verify (closed source or a single maintainer), so pin the version you tested.
Does AgentSEO MCP Server have known vulnerabilities?
Not in our current data: it has no open CVEs or advisories. We re-check as new ones are published.
Does AgentSEO MCP Server support authentication?
Yes. It requires a login, so access can be tied to a person or a scoped key.
Alternatives in SEO Data
- A Ahrefs MCPOfficial hosted Ahrefs server for backlinks, keywords, and site metrics, with OAuth sign-in.
- A CrakSEO SEO Tools MCP ServerCrakSEO's hosted, read-only server for live Google and Bing results, keyword volume and difficulty, backlinks, rankings, competitor gaps, site audits, Google Maps ranks and ChatGPT or Perplexity brand mentions, paid from prepaid API credits.
- B BotSee MCP ServerOfficial hosted server that runs AI-visibility analyses (question sets across personas and models) and returns competitor, keyword and cited-source results; uses paid credits.
- B DataForSEO MCP ServerOfficial DataForSEO server for SERP, keyword, and backlink data via its API, hosted or local.
- B Datrace MCP ServerHosted server for Amazon marketplace research that looks up ASINs, keyword demand, rankings, traffic, ad signals and category data; free beta with monthly credits.
Community reviews
Works, just lock it down
Good for experimenting, still deciding about production. The scope options are worth reading carefully, the defaults are broader than I wanted.
Used for Competitor gap analysis
- Setup & docs 3/5
- Auth experience 3/5
- Reliability 3/5
- Maintainer responsiveness 3/5
Does the job, docs could be better
It does the job, but it took some tweaking. Filed an issue and got a reply within two days. Auth is handled properly, and revoking access later was one click. The OAuth flow worked first time in Claude Code. Keep permissions tight and it is a good tool.
Used for Briefing writers with search data
- Setup & docs 4/5
- Auth experience 4/5
- Reliability 3/5
- Maintainer responsiveness 3/5
Solid core, fiddly setup
Some tools are great, a couple feel half finished. Scoped the token to just what the agent needs and it respected that.
Used for Spotting traffic drops early
- Setup & docs 3/5
- Auth experience 4/5
- Reliability 3/5
- Maintainer responsiveness 4/5
Clean integration, sensible permissions
Replaced a homegrown script with AgentSEO MCP Server and have not looked back. The OAuth flow worked first time in Claude Code. Sign-in flow was painless and I never had to paste a key into a config file. Recommended, with sensible guardrails.
Used for Competitor gap analysis
- Setup & docs 5/5
- Auth experience 4/5
- Reliability 5/5
- Maintainer responsiveness 5/5
Easy win for our agent setup
Been running this for about a month now. Sign-in flow was painless and I never had to paste a key into a config file. Releases come often and the changelog is clear. Happy to run it in production.
Used for Keyword research for a content plan
- Setup & docs 3/5
- Auth experience 3/5
- Reliability 4/5
- Maintainer responsiveness 4/5
Quietly reliable
Set this up for our team after comparing a few options. Scoped the token to just what the agent needs and it respected that.
Used for Backlink audits
- Setup & docs 5/5
- Auth experience 4/5
- Reliability 4/5
- Maintainer responsiveness 3/5
Decent, not set-and-forget
Mostly reliable, with the odd timeout. Nice that it supports both stdio and HTTP, I use stdio locally and HTTP for the shared agent. The OAuth flow worked first time in Claude Code. I would use it in prod, but only with a human approving writes.
Used for Weekly ranking checks
- Setup & docs 3/5
- Auth experience 3/5
- Reliability 3/5
- Maintainer responsiveness 4/5
Good, but read the permissions first
Took longer to configure than I expected. I like that access goes through a proper sign-in instead of a long-lived secret on disk. Fine in production if you sandbox it.
Used for Weekly ranking checks
- Setup & docs 4/5
- Auth experience 3/5
- Reliability 2/5
- Maintainer responsiveness 4/5
Write a review
Ran this server? Tell other teams how it went. You get one review per server. We email you a link to confirm it, then an editor checks it before it goes up. We never show your email.