Trakis MCP server

https://trakis.io/mcp

It is a remote MCP server, the standard way assistants plug in outside tools.

Claude (claude.ai and the desktop app): Settings → Connectors → Add custom connector. Name it Trakis and paste the address above.

Claude Code:

claude mcp add --transport http trakis https://trakis.io/mcp

Other assistants and editors that take a remote MCP server by URL: add the same address. Where a configuration file is asked for:

{
  "mcpServers": {
    "trakis": { "url": "https://trakis.io/mcp" }
  }
}

• Search the checks (search_checks) — 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.
• Explain a check (explain_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.
• List the checks (list_checks) — Every check a Trakis audit runs, optionally only one category or one severity, with its code, title and a link to its explanation.

Things to ask: “What does CRAWL-008 mean and how do I fix it?”, “Which Trakis checks are about canonical tags?”, “List the critical checks.”

A second address reads your account: your sites, the last audit of each, and the exact fix for a problem on them. Add it the same way:

https://trakis.io/mcp/account

The assistant sends you to Trakis to sign in, shows you where the access goes, and asks you to allow it. It can only read, and you can disconnect it at any time in Settings, under Connected apps. It also has the three tools above.

• List my sites (list_sites) — The sites in the signed-in person's Trakis account, with the grade and date of each site's last audit and how many critical problems it has.
• Get a site's health (get_site_health) — One site's last audit: grade, change since the audit before, scores by category, and the problems to fix first — each counted once, with the pages it covers and the effort to fix it.
• Explain a finding on my site (explain_finding) — The exact fix for one problem on one of the person's sites: what was found, the evidence, the steps and ready-to-paste code with the site's own addresses, and the pages it applies to.
• What changed on my site (get_site_changes) — What changed between a site's last audit and the one before: problems fixed and new, and the pages' own changes — a title rewritten, a page that started answering an error or asked to leave the index, a big drop in text — with examples, and an AI-written sentence on what each means where there is one.
• Internal links worth adding (get_link_opportunities) — A site's internal links: how many clicks each page is from the home page, how many links each page receives, and the links worth adding — pages whose own text names what another page is about without linking to it, with the exact words to link.
• My positions in Google (get_search_positions) — Where a site shows up in Google, from its own Search Console: its searches by band of position (1–3, 4–10, 11–20, 21+) week by week, which ones moved up or down since the week before, which entered or left the first ten, and the last week's searches with clicks and impressions.

• The public address does not see anybody’s sites; the account address sees yours, and only after you allowed it.
• Neither runs an audit. For that, use the form on the start page or your account.
• They only read. Every tool is marked read-only, and none can change anything, anywhere.

On the public address, nothing about you: the answer comes from the public reference of the checks. On the account address, the name the assistant registered under and when you connected it — the access itself is kept only as a fingerprint that cannot be turned back into a key. The privacy page says the same. Questions: hello@trakis.io.