
SEOclar — SEO MCP Server
io.github.verbatikPublished by GitHub account verbatikv1.0.0Updated Oct 30, 2026
SEO MCP server for keyword research, live SERPs, backlinks, site audits and AI visibility.
Overview
Remote SEO MCP server that lets an assistant run keyword research, pull live SERPs, check backlinks, audit sites and track AI visibility.
- What you can do
- Keyword research: explore and evaluate keywords for search demand.
- Live SERPs: retrieve current search engine results pages.
- Backlinks: inspect a site's inbound link profile.
- Site audits: review a site for SEO issues.
- AI visibility: check how a site or brand appears in AI answers.
- When to use it
- Useful when an assistant needs current search data while doing SEO work — planning content around keywords, checking rankings and backlinks, auditing a site, or measuring AI visibility. Worth adding if you already work in SEO and want those lookups inside your assistant instead of separate tools.
- Requirements
- A remote MCP endpoint at seoclar.com over streamable HTTP. OAuth authentication is required, so you need an account with the provider and must complete the OAuth sign-in flow. No environment variables or headers are declared.
Installation
In SourceWeft
- Open SEOclar — SEO MCP Server in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.verbatik%2Fseoclar/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"seoclar-seo": {
"type": "http",
"url": "https://seoclar.com/mcp"
}
}
}Tools
0Version history
1- v1.0.0LatestOct 29, 2026
Score
67% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.