Runs 66 technical SEO and AI-readiness checks on a site and explains what each check looks at, why it matters, and how to fix it.
What you can do
This remote MCP server exposes a set of 66 technical SEO and AI-readiness checks. For each check it reports what the check examines, why the result matters, and how to fix the issue found. It is hosted by the provider and reached over streamable HTTP, so the assistant calls it directly rather than running anything locally.
When to use it
Useful when auditing a website's technical SEO or its readiness for AI crawlers and assistants, and when you want findings paired with remediation guidance rather than raw scores. Suited to site owners, SEO specialists, and developers reviewing a site before or after changes.
Requirements
A remote MCP endpoint at the provider's host, reached over streamable HTTP. No packages, environment variables, or headers are declared, and no authentication is declared. Network access to the provider's endpoint is required.
Before you install
The manifest declares no authentication, so confirm how access is controlled before connecting. Checks are performed against a site you submit, which means the target URL is sent to the provider's service; avoid submitting internal, staging, or otherwise non-public addresses unless that is acceptable.
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.trakis%2Fseo-checks/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.
Find Trakis checks by a word or a problem, when you do not know the check's code. Searches titles, what each check looks at, why it matters and where the problem usually comes from. Returns up to 10 checks, best matches first.
Parametersqueryrequired
explain_check
Explain a check
The full explanation of one Trakis check: what it looks at, why it matters, where the problem usually comes from, how to fix it (with a worked example when there is one), how to verify it without Trakis, and how an audit counts it.
Parametersidrequired
list_checks
List the checks
Every check a Trakis audit runs, optionally only one category or one severity, with its code, title and a link to its explanation.
Parameterscategoryseverity
Version history
1
v1.0.0LatestOct 12, 2026
Score
83%
83% 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 listedRequired15 pts
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.