Free technical-SEO audit MCP: crawl a site, run checks, return an LLM-ready shareable report.
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
scan_url2 fields changedInput schema / properties / max_pagesAdded value: +{
+ "description": "How many pages to crawl. Default 50; maximum 200. Ignored for mode=instant.",
+ "maximum": 200,
+ "minimum": 1,
+ "type": "integer"
+}Input schema / properties / mode / descriptionPrevious value: -"Scan mode: \"free\" (default) or \"instant\"."New value: +"Scan mode: \"free\" (default, multi-page) or \"instant\" (single-page quick check)."diff_scanget_issue_detailget_reportget_report_markdownscan_urlClaiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such as io.github.acme/server also needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.
HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at /.well-known/glama.json on the same origin as the connector, then choose Check HTTP challenge.
DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
👋 Maintainer here. Crawlinx is a free, no-signup technical-SEO audit crawler exposed over MCP — point it at any URL and get a health score, a prioritized list of fixes, and a shareable report link. What's different: it runs a real browser engine, so it renders JavaScript and gets past most bot-walls. That means it sees a page the way Googlebot — and AI crawlers like GPTBot/ClaudeBot, which mostly skip JS — actually see it, not the raw HTML most crawlers get. 156 checks, including 2026-era ones others skip: structured-data deprecations, AI-bot accessibility, and agent-readiness. Quick start (Claude Code): claude mcp add --transport http crawlinx https://crawlinx.com/mcp Typical flow: scan_url (start an audit, returns a scan id) → get_report_markdown / get_report → get_issue_detail (expand one issue) → diff_scan (after fixing, confirm it landed and nothing regressed). No API key, no signup, nothing to install. Feedback and check requests very welcome!
SEO MCP server: crawl your site, find AI-visibility gaps, and ship the fix from your coding agent.
Technical SEO + GEO (AI-search) site audits: hosted crawls, prioritized fixes, report diffs.
Security, SEO and AI-visibility scanner for web apps · free scans and focused checks via MCP.
Professional SEO auditing: 15 tools, 9 checks, CWV, E-E-A-T, schema, GEO. Free tier.
Add one secure layer between your agents and this server.
Each tool has a clearly distinct purpose: submit scan (scan_url), retrieve report in JSON or Markdown (get_report, get_report_markdown), drill into an issue (get_issue_detail), and compare scans (diff_scan). No overlapping functionality.
All tool names follow a consistent verb_noun pattern (e.g., scan_url, get_report, diff_scan). Format variants like get_report_markdown are logical extensions, not inconsistencies.
Five tools perfectly cover the SEO auditing workflow: initiating a scan, retrieving results in two formats, expanding issue details, and comparing scans. The count is neither excessive nor minimal.
The tool set covers the essential lifecycle: scan submission, result retrieval in multiple formats, issue detail expansion, and diffing. Missing list_scans or cancel_scan, but these are minor gaps; agents can work with existing tools.
