SEOmatic MCP server
ai.seomatic/seomaticseomatic.aistreamable-httpv1.10.1Scanned
SEO agent: GSC, keywords, local rank tracking, Business Profile, AI visibility, approval-gated fixes
2 tools: 2 change things.
- Reads private data · 0
- Reads text others write · 1
- Can send data out · 0
- No findings
Sign-in required, OAuth metadata published. Remote posture
With Anlyon
2 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
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 SEOmatic MCP server can do
The SEOmatic MCP server is published by seomatic.ai, a domain the MCP Registry verified. It has 2 tools. It can create or change data (2 tools: check_site and connect_seomatic), but cannot delete data. None of its tools only reads.
1 tool brings in text other people can write (check_site).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint asks for sign-in and publishes OAuth metadata.
Last scanned Oct 29, 2026, version 1.10.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.
2 tools
Changes things 2Claude Code: ask
check_siteFree first check of the user's OWN website, no account needed: whether Google can index the homepage (status, redirects, noindex, canonical, robots.txt for Googlebot and the AI sea…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 read-only (readOnlyHint: true), but an annotation never lowers a class.
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 Free first check of the user's OWN website, no account needed: whether Google can index the homepage (status, redirects, noindex, canonical, robots.txt for Googlebot and the AI search crawlers, JavaScript-only rendering) and a sample of up to 10 sitemap pages, the top fixes ranked by impact, and what needs Search Console to check. Present the verdict and the fixes. Cost: FREE.
Annotations the server declares
- title: Check a Site (no sign-in)
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
connect_seomaticSigns the user in to SEOmatic (free) so answers can use their own Search Console data, audits and tracking.No 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 read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Signs the user in to SEOmatic (free) so answers can use their own Search Console data, audits and tracking. Calling it shows the sign-in prompt; after that every SEOmatic tool is available. Applies when the user wants real clicks and rankings, or asks for something check_site cannot do. Cost: FREE.
Annotations the server declares
- title: Connect SEOmatic
- 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 or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- 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.
Looked at Nov 20, 2026, 18:27 UTC, unchanged since Nov 20, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 401
- tools/list served without credentials
- no
- Tools that change things, listed without credentials
- 0
- Protocol version
- not observed
- WWW-Authenticate on 401
- yes
- resource_metadata in WWW-Authenticate
- https://app.seomatic.ai/.well-known/oauth-protected-resource/api/mcp
- RFC 9728 protected resource metadata
- https://app.seomatic.ai/.well-known/oauth-protected-resource/api/mcp
- Authorization servers
- https://app.seomatic.ai
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- yes
Posture changes
- Nov 20, 2026
- resource_metadata in WWW-Authenticate: https://app.seomatic.ai/.well-known/oauth-protected-resource to https://app.seomatic.ai/.well-known/oauth-protected-resource/api/mcp
- RFC 9728 protected resource metadata: https://app.seomatic.ai/.well-known/oauth-protected-resource to https://app.seomatic.ai/.well-known/oauth-protected-resource/api/mcp
- Nov 13, 2026
- HTTP status of an anonymous initialize: 200 to 401
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 2 to 0
- Protocol version: 2025-06-18 to none
- WWW-Authenticate on 401: not observed to yes
- resource_metadata in WWW-Authenticate: none to https://app.seomatic.ai/.well-known/oauth-protected-resource
- RFC 9728 protected resource metadata: https://app.seomatic.ai/.well-known/oauth-protected-resource/api/mcp to https://app.seomatic.ai/.well-known/oauth-protected-resource
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. resource_metadata in WWW-Authenticate: https://app.seomatic.ai/.well-known/oauth-protected-resource -> https://app.seomatic.ai/.well-known/oauth-protected-resource/api/mcp; RFC 9728 protected resource metadata: https…View diff
- resource_metadata in WWW-Authenticate: https://app.seomatic.ai/.well-known/oauth-protected-resource to https://app.seomatic.ai/.well-known/oauth-protected-resource/api/mcp
- RFC 9728 protected resource metadata: https://app.seomatic.ai/.well-known/oauth-protected-resource to https://app.seomatic.ai/.well-known/oauth-protected-resource/api/mcp
PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 401; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 2 -> 0 (and 4 more).View diff
- HTTP status of an anonymous initialize: 200 to 401
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 2 to 0
- Protocol version: 2025-06-18 to none
- WWW-Authenticate on 401: not observed to yes
- resource_metadata in WWW-Authenticate: none to https://app.seomatic.ai/.well-known/oauth-protected-resource
- RFC 9728 protected resource metadata: https://app.seomatic.ai/.well-known/oauth-protected-resource/api/mcp to https://app.seomatic.ai/.well-known/oauth-protected-resource
Install
Pinned to version 1.10.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http seomatic https://app.seomatic.ai/api/mcpclaude mcp add --transport http seomatic https://app.seomatic.ai/api/mcpRun 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.
{
"permissions": {
"allow": [],
"ask": [
"mcp__seomatic__check_site",
"mcp__seomatic__connect_seomatic"
],
"deny": []
}
}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 seomatic. Review it before you use it.
Capability tags behind 1 rule
- mcp__seomatic__check_site untrusted-input
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/ai.seomatic/seomatic/verify?hash=3d650999d858635ab45aaef11a41364b07bef3c49e7041a7182a3881486b6631" | jq -e '.changed == false'Pinned hash 3d650999d858, from Oct 29, 2026, 16:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/ai.seomatic/seomatic/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/ai.seomatic/seomatic)Source: MCP Registry · repository. Synced Nov 18, 2026, 01:17 UTC.
SEOmatic MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the SEOmatic MCP server safe?
- No scan can promise that. What its definitions show: 2 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the SEOmatic MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the SEOmatic 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 SEOmatic MCP server have?
- 2 tools: 2 write. check_site and connect_seomatic.
Does the SEOmatic MCP server need sign-in or OAuth?
- Yes. Its remote endpoint answered 401 without credentials, and it publishes OAuth protected resource metadata (RFC 9728); its authorization server supports dynamic client registration.
Does the SEOmatic MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the SEOmatic MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Oct 29, 2026.