Skip to content

Trakis SEO checks

by trakis.io · remote · no sign-in to list tools · v1.0.0 · published by io.trakis

66 technical SEO and AI-readiness checks: what each looks at, why it matters, how to fix it

Read only
CompareRegistry entry

3 tools: 3 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

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

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

3 tools

Only reads 3Claude Code: allow
  • explain_checkThe 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 ve…No findings

    Why it is in this group

    • The name "explain_check" says "explain": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Explain a check
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_checksEvery check a Trakis audit runs, optionally only one category or one severity, with its code, title and a link to its explanation.No findings

    Why it is in this group

    • The name "list_checks" says "list": a word for reading.
    Description, as the server wrote it
    Every check a Trakis audit runs, optionally only one category or one severity, with its code, title and a link to its explanation.

    Annotations the server declares

    • title: List the checks
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • search_checksFind Trakis checks by a word or a problem, when you do not know the check's code.No findings

    Why it is in this group

    • The name "search_checks" says "search": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Search the checks
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__seo-checks__search_checks",
      "mcp__seo-checks__explain_check",
      "mcp__seo-checks__list_checks"
    ],
    "ask": [],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as seo-checks. Review it before you use it.