Trakis MCP server

• Registry nameio.trakis/seo-checksverified in the MCP registry

The registry name sits under trakis.io. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-27
• Tools3
• Server calls itselftrakis
• Server version1.0.0
• Protocol version2025-06-18

On 2026-10-27 the server answered initialize and tools/list without a sign-in. First answer in 244 ms.

• Whether its tools do the product's job has not been judged yet.
• Checked on 1 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP scoreafter a weeka score needs 7 daily checks: 1 so far
• Answeredmeasuring1 of the 7 daily checks it takes to print a share
• Median first answer242 ms
• Space in an agent's context≈ 388 tokensthe definitions of all its tools (3), which an agent carries on every turn
• Tool definitionsA · 100 of 100
• Typed results0 of 3 toolsdeclared outputSchema: results come typed, read once

• Every tool passes all six checks.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• 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_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_checks

  Every check a Trakis audit runs, optionally only one category or one severity, with its code, title and a link to its explanation.

• io.trakis/site-auditsanswers, requires sign-inverified in the MCP registry