# Docket SEO (mcpb · linux-x64)

SEO audits that run on your computer: score, ranked fixes and AI-search checks. Free to try.

- Trust score: 38/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- mcpb · `linux-x64`: 38/100 (this document), [markdown](https://verifymcp.io/servers/mattkerr09-docket/docket-linux-x86-64.md), [page](https://verifymcp.io/servers/mattkerr09-docket/docket-linux-x86-64)
- mcpb · `Docket-1.3.150-macos.mcpb`: 6/100, [markdown](https://verifymcp.io/servers/mattkerr09-docket/docket-macos.md), [page](https://verifymcp.io/servers/mattkerr09-docket/docket-macos)

## Channel facts

- Registry: `mcpb`
- Package: `https://github.com/mattkerr09/docket-site/releases/download/v1.3.150/Docket-1.3.150-linux-x86_64.mcpb`
- Transport: `stdio`
- SHA-256: `211d213c4b57570bdb870df1d108b739e4ce4d7f4e4ced40de070b3274127c8a`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, 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.

- **Supply Chain Security**: 0/100
  - No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  - Known CVEs could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).
- **Provenance & Transparency**: 32/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - License check failed: the license (SEE LICENSE IN https://docketseo.app/legal/terms/) isn't a recognized OSI-approved license.
  - Actively maintained (last published 0 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 441 tokens (~88/item across 5 items; 5 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability observed for 0 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**Unverified: 2 categories.** Categories scored 0 because we could not verify them: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the Docket SEO MCP server?

Docket SEO ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, 211d213c4b57570bdb870df1d108b739e4ce4d7f4e4ced40de070b3274127c8a; the commands to do that are on this page. If it does not match, do not open it.

- Download bundle: `https://github.com/mattkerr09/docket-site/releases/download/v1.3.150/Docket-1.3.150-linux-x86_64.mcpb`
- SHA-256: `211d213c4b57570bdb870df1d108b739e4ce4d7f4e4ced40de070b3274127c8a`

### Verify on macOS / Linux

```bash
echo "211d213c4b57570bdb870df1d108b739e4ce4d7f4e4ced40de070b3274127c8a  Docket-1.3.150-linux-x86_64.mcpb" | shasum -a 256 -c
```

### Verify on Windows (PowerShell)

```powershell
(Get-FileHash -Algorithm SHA256 .\Docket-1.3.150-linux-x86_64.mcpb).Hash -eq "211d213c4b57570bdb870df1d108b739e4ce4d7f4e4ced40de070b3274127c8a"
```

## 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-05 (score 38)

First indexed and scored.

## MCP tools (5)

### `audit_site` (~136 tokens)

Crawl a website and return Docket's SEO findings: an overall score, and every issue found with its severity, how many pages it affects, and the specific fix. Takes a few minutes on a real site.

Input parameters:

- `max_pages` (integer): Pages to crawl (default 40).
- `max_seconds` (number): Time budget (default 180.0).
- `offline` (boolean): Skip every third-party connector. A normal audit contacts Google PageSpeed, DNS and docketseo.app; set true to keep the run entirely local.
- `url` (string, required): The site to audit, e.g. https://example.com

### `get_last_report` (~66 tokens)

Return the most recent audit Docket has kept, with its score and every finding, without crawling again. Give a url to get the latest audit of that site. Free (unactivated) audits are not kept.

Input parameters:

- `url` (string): Only audits of this site (optional).

### `explain_finding` (~104 tokens)

Explain one problem from a kept audit in full: what is wrong, which pages, why it matters, and the exact fix and markup. Name it by check id (e.g. schema.none) or by words from its title.

Input parameters:

- `finding` (string, required): A check id, or words from the finding's title.
- `report_id` (string): Use this kept audit (optional).
- `url` (string): Use the latest audit of this site (optional).

### `compare_audits` (~98 tokens)

Compare two kept audits of the same site: the score change, the change in each area, and which problems are new, fixed, worse or better. Defaults to the two most recent audits of the site.

Input parameters:

- `newer` (string): Report id of the later audit (optional).
- `older` (string): Report id of the earlier audit (optional).
- `url` (string): The site (optional if both ids are given).

### `list_checks` (~37 tokens)

List every check Docket runs, with its lane and what it looks for. Answers 'what does Docket actually check?' without crawling anything.

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/mattkerr09-docket/docket-linux-x86-64#diagnostics

## Score history

- 2026-11-05: 38

## Common questions

### What is the Docket SEO MCP server?

Docket SEO is an MCP server listed in the public MCP registry as io.github.mattkerr09/docket. SEO audits that run on your computer: score, ranked fixes and AI-search checks. Free to try. This page covers its MCPB bundle (https://github.com/mattkerr09/docket-site/releases/download/v1.3.150/Docket-1.3.150-linux-x86_64.mcpb).

### Is the Docket SEO MCP server safe to use?

Docket SEO scores 38 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 Docket SEO MCP server expose?

Docket SEO exposes 5 tools: audit_site, get_last_report, explain_finding, compare_audits, list_checks. Their descriptions and schemas cost roughly 441 tokens of context every time the server is loaded.

### What did VerifyMCP test on the Docket SEO MCP server?

VerifyMCP ran 11 checks on Docket SEO, covering Source repository, Provenance, License, Maintenance and 7 more. 5 items could not be completed, a gap on our side rather than a finding about Docket SEO: Malware scan, Known CVEs, Install scripts, Dependency health and 1 more. 2 categories score 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an MCPB bundle, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Repository: https://github.com/mattkerr09/docket-mcp
- Website: https://docketseo.app/
- Changelog RSS feed: https://verifymcp.io/servers/mattkerr09-docket/docket-linux-x86-64.xml
- Changelog JSON feed: https://verifymcp.io/servers/mattkerr09-docket/docket-linux-x86-64/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/mattkerr09-docket/docket-linux-x86-64.json
- HTML version of this page: https://verifymcp.io/servers/mattkerr09-docket/docket-linux-x86-64
