# Trakis SEO checks (remote · trakis.io)

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

- Trust score: 85/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `trakis.io`: 85/100 (this document), [markdown](https://verifymcp.io/servers/io-trakis-seo-checks/trakis.md), [page](https://verifymcp.io/servers/io-trakis-seo-checks/trakis)

## Channel facts

- Endpoint: `https://trakis.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 79/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 376 tokens (~125/item across 3 items; 3 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 80/100
  - Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Trakis SEO checks MCP server?

Trakis SEO checks is a hosted endpoint at https://trakis.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

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

### Cursor

```json
{
  "mcpServers": {
    "io-trakis-seo-checks": {
      "url": "https://trakis.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-trakis-seo-checks": {
      "type": "http",
      "url": "https://trakis.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-trakis-seo-checks]
url = "https://trakis.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-trakis-seo-checks": {
      "type": "remote",
      "url": "https://trakis.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-trakis-seo-checks --url 'https://trakis.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-trakis-seo-checks:
    url: "https://trakis.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-trakis-seo-checks": {
      "Transport": "http",
      "Url": "https://trakis.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-trakis-seo-checks -t streamable-http -u 'https://trakis.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-trakis-seo-checks": {
      "type": "http",
      "url": "https://trakis.io/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 85, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 84, +1)

No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 83, +1)

No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-29 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-27 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-25 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-23 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-20 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (3)

### `search_checks` (~90 tokens)

Search the 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.

Input parameters:

- `query` (string, required): A word or short phrase, e.g. "canonical", "robots.txt", "duplicate title", "structured data".

### `explain_check` (~95 tokens)

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.

Input parameters:

- `id` (string, required): The check's code, e.g. "CRAWL-008" or "onpage-005". Case does not matter.

### `list_checks` (~62 tokens)

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.

Input parameters:

- `category` (string): Only the checks of this category.
- `severity` (string): Only the checks of this severity.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-trakis-seo-checks/trakis#diagnostics

## Score history

- 2026-11-05: 85
- 2026-11-04: 85
- 2026-11-03: 84
- 2026-11-02: 84
- 2026-11-01: 83
- 2026-10-31: 83
- 2026-10-30: 82
- 2026-10-29: 82
- 2026-10-28: 81
- 2026-10-27: 81
- 2026-10-26: 80
- 2026-10-25: 80
- 2026-10-24: 79
- 2026-10-23: 79
- 2026-10-22: 78
- 2026-10-21: 78
- 2026-10-20: 78
- 2026-10-19: 77
- 2026-10-18: 77
- 2026-10-17: 76
- 2026-10-16: 76
- 2026-10-15: 75
- 2026-10-14: 75
- 2026-10-13: 74
- 2026-10-12: 74

## Common questions

### What is the Trakis SEO checks MCP server?

Trakis SEO checks is an MCP server listed in the public MCP registry as io.trakis/seo-checks. 66 technical SEO and AI-readiness checks: what each looks at, why it matters, how to fix it. This page covers its hosted endpoint (https://trakis.io/mcp).

### Is the Trakis SEO checks MCP server safe to use?

Trakis SEO checks scores 85 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Trakis SEO checks MCP server expose?

Trakis SEO checks exposes 3 tools: search_checks, explain_check, list_checks. Their descriptions and schemas cost roughly 247 tokens of context every time the server is loaded.

### Does the Trakis SEO checks MCP server require authentication?

No. We connected to Trakis SEO checks without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Trakis SEO checks MCP server still maintained?

Trakis SEO checks is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Trakis SEO checks MCP server?

VerifyMCP ran 13 checks on Trakis SEO checks, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://trakis.io/mcp
- Website: https://trakis.io/connect
- Changelog RSS feed: https://verifymcp.io/servers/io-trakis-seo-checks/trakis.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-trakis-seo-checks/trakis/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/io-trakis-seo-checks/trakis.json
- HTML version of this page: https://verifymcp.io/servers/io-trakis-seo-checks/trakis