Agent MCP Directory

SEOmatic: MCP server, CLI and agent surfaces

Yes: SEOmatic runs a public MCP server at app.seomatic.ai that listed 2 tools to a client with no credentials on 4 November 2026. Examples: check_site, connect_seomatic. It speaks streamable-http, protocol 2026-07-28. Ora's cached score for seomatic.ai is 35, grade D, read on 5 November 2026.

Fact sheet

CompanySEOmatic
Domainseomatic.ai
CategoryMarketing (assigned by this directory from the registry description)
MCP serverVerified (No authentication)
Ora score35, grade D; Ora scanned the domain on 27 August 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for seomatic.ai, a vendor-published score)
Company found throughthe GitHub MCP Registry; the official MCP Registry
Last verified4 November 2026

MCP server

Endpointhttps://app.seomatic.ai/api/mcp
How it was foundlisted in the GitHub MCP Registry; the official MCP Registry
Transportstreamable-http
HTTP status200
Protocol version2026-07-28
Serverseomatic 1.0.0
Capabilitiestools, prompts, resources
Tools2
Resources5
Prompts5
Connected4 November 2026, 20:04 UTC
Handshake time1,251 ms over 1 attempt

Tools listed

2 tools

  • check_site
  • connect_seomatic

Connector log

2 connections on 4 November 2026, read-only methods only

  • 19:59:26Z https://app.seomatic.ai/api/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1474 ms
  • 20:04:27Z https://app.seomatic.ai/api/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1251 ms

Authentication

Auth typeNo authentication

The sign-in route, step by step

  1. Send the handshake to https://app.seomatic.ai/api/mcp over streamable-http. Servers on the 2026-07-28 revision answer server/discover; older servers answer initialize.
  2. Send tools/list, then resources/list and prompts/list if the capabilities name them.
  3. Send no token. The connector sent none and the server answered, so any MCP client can read this list.
  4. Calling a tool is a separate step this directory never takes.

See OAuth for MCP: client ID metadata documents and dynamic registration for how each route works.

CLI

No CLI is on record for SEOmatic. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See shipping a CLI agents can use.

Other agent surfaces

Agent surfaces other than MCP and CLI
SurfaceResult
OpenAPI fileNo OpenAPI file at the root paths checked.
WebMCP in the initial HTMLNot checked: the home page was not read by the shared crawl.
MCP discovery fileNot checked: the domain is not in the shared crawl for this edition.
A2A agent cardNot checked: the domain is not in the shared crawl for this edition.
A2A agent card (older path)Not checked: the domain is not in the shared crawl for this edition.
agents.jsonNot checked: the domain is not in the shared crawl for this edition.
OAuth authorization server metadataNot checked: the domain is not in the shared crawl for this edition.
NLWeb endpointNot checked in this edition.

Registry listings

Registry listings
RegistryListed
Official MCP RegistryYes: ai.seomatic/seomatic
GitHub MCP RegistryYes
awesome-remote-mcp-serversNo
SmitheryNot checked: Smithery's listing pages and search API were unavailable on 4 November 2026.
GlamaNot checked: Glama's API needs a key and attribution terms.