SEO
Capped at 70: no passing tool call yet; the tests add up to 95. Why scores are capped
Test points add up to 95; the score is capped at 70 until a tool call passes. Not a quality or security rating. Methodology
Test points before the cap (95/100)
- Install20/20
- Handshake30/30
- Maintenance25/25
- Docs10/15
- License10/10
Tested npm seo 0.24.0 (Apache-2.0; repo iannuttall/seo). Installed pinned with scripts off (npm --ignore-scripts) and launched with `mcp serve`: initialize and tools/list over stdio succeeded with no credentials and listed 16 tools (16 annotated by the server: 13 read-only, 0 destructive). Real calls: 0 of 3 real function calls passed. Calls need a seoskill.dev sign-in. Core tools not tested: 70 cap.
Tool-call test (2026-11-19 UTC, direct MCP stdio client, no LLM): fail. 0 of 3 real function calls passed. Calls need a seoskill.dev sign-in. Evidence: local test run, Nov 19, 2026 UTC.
Transport (tested 2026-11-19 UTC): stdio
Token cost (estimate): approx. 8574 tokens, cl100k estimate (16 tools, measured 2026-11-19 UTC, version 0.24.0). This is an estimate from our testing of the tool names, descriptions and input schemas, counted with cl100k_base.
Permissions: 2 read, 2 write (state-changing), 12 unclassified · Auth: API key · Rate limit: unknown · Pricing unit: unknown
Auth: API key. Rate limit: unknown. Pricing unit: unknown.
seo_compare— write (state-changing)seo_crawl— unclassifiedseo_data— unclassifiedseo_describe_provider— readseo_feedback— unclassifiedseo_index— unclassifiedseo_internal_links— unclassifiedseo_lint— unclassifiedseo_list_providers— readseo_next— unclassifiedseo_page— unclassifiedseo_report— write (state-changing)seo_research— unclassifiedseo_run_provider— unclassifiedseo_sites— unclassifiedseo_submit— unclassified
listing-flags calls_need_key or auth_kind
Score 70/100 · Tools 16 · Token cost approx. 8,574 tokens · Compare · Last tested 2026-11-19 UTC · Version tested 0.24.0 · Package seo · Repo iannuttall/seo
Summary: SEO completed an MCP handshake without credentials and exposed 16 tools.
Evidence summary
- Handshake
- pass
- Tools listed
- 16
- Context cost
- approx. 8574 tokens, cl100k estimate (16 tools, measured 2026-11-19 UTC, version 0.24.0; an estimate) ranking · add up your servers' context cost
- API key
- Connects without a key; tool calls need one
- Tested
- 2026-11-19 UTC
Test results
| Test | Result | Points | Evidence |
|---|---|---|---|
| install | pass | 20 | npm install seo --ignore-scripts (Node v24.22.1, Linux) succeeded in 4s. |
| handshake | pass | 30 | MCP initialize + tools/list over stdio succeeded with no credentials; 16 tools listed in 3.0s. |
| maintenance | pass | 25 | Repo pushed 0 days before test; 637 GitHub stars. |
| docs | partial | 10 | README over 3,000 chars; install instructions present. Check of the package's own README (README shipped in npm package). |
| license | pass | 10 | Apache-2.0 (OSI-approved). |
Local-model readiness
Token cost (estimate): approx. 8574 tokens, cl100k estimate for 16 tools · about 105% of an 8k context. This is an estimate from our testing (counted with cl100k_base).
Small-model friendly (schema heuristic, not a model result): unknown.
Not tested
Small-model task runs: Not yet tested.
What we tested and what we didn't
Tested on 2026-11-19 UTC
- Install from the registry
- We connected with no credentials and asked for its tool list: it listed 16 tools (Method details: MCP
initializethentools/list) - Maintenance signals (last push, archived/deprecated status)
- Docs (README length, install and config example)
- License (OSI-approved or not)
- Token cost (estimate)
Not tested
- Security: not audited (no code review, no permission or data-flow analysis)
- Real tasks (no functional task runs yet)
- Behaviour with real credentials or a real account
- Performance, rate limits or load
- Correctness of results beyond the listed tasks
Methodology: how we test. A high score means it installs and responds, not that giving it access to your data carries no risk.
Known security issues
Not yet checked.
Monthly roundup: MCP security issues, October 2026.
Tool list changes
Baseline recorded from the 2026-11-19 UTC test run; changes appear after the next test.
Snapshot hash (fingerprint of the tool list)
8f8fd63607b8: SHA-256 of the canonical tool names, descriptions and input schemas. If it changes, the tool list changed.
Raw test record (JSON)
{
"name": "seo",
"version": "0.24.0",
"registry": "npm",
"status": "working",
"tested": "2026-11-19",
"tools_count": 16,
"deprecated": false,
"archived": false,
"tests": {
"install": [
"pass",
20,
"`npm install seo --ignore-scripts` (Node v24.22.1, Linux) succeeded in 4s."
],
"handshake": [
"pass",
30,
"MCP `initialize` + `tools/list` over stdio succeeded with no credentials; 16 tools listed in 3.0s."
],
"maintenance": [
"pass",
25,
"Repo pushed 0 days before test; 637 GitHub stars."
],
"docs": [
"partial",
10,
"README over 3,000 chars; install instructions present. Check of the package's own README (README shipped in npm package)."
],
"license": [
"pass",
10,
"Apache-2.0 (OSI-approved)."
]
},
"testedAt": "2026-11-19T06:10:14.133Z"
}Install
npx -y seo mcp serve
Pin the version we tested
npx -y --ignore-scripts seo@0.24.0 mcp serve
tested 2026-11-19 UTC. Newer versions may differ and were not tested by us.
{
"mcpServers": {
"seo": {
"command": "npx",
"args": [
"-y",
"seo@0.24.0",
"mcp",
"serve"
]
}
}
}Tools listed
seo_sites, seo_next, seo_report, seo_page, seo_compare, seo_index, seo_submit, seo_research, seo_data, seo_lint, seo_feedback, seo_crawl, seo_internal_links, seo_list_providers, seo_describe_provider, seo_run_provider
Quick config
{
"mcpServers": {
"seo": {
"command": "npx",
"args": [
"-y",
"seo",
"mcp",
"serve"
]
}
}
}Add to config Opens the config generator with this server selected.
Setup
- Install. Run
npm install seo --ignore-scripts(Node v24.22.1). This is the exact command we ran on 2026-11-19 UTC. - Configure. Add the mcpServers entry below to your MCP client config.
- Verify. Restart the client and check that tools/list returns tools (16 in our test).
{
"mcpServers": {
"seo": {
"command": "npx",
"args": [
"-y",
"seo",
"mcp",
"serve"
]
}
}
}Test history
- 2026-11-19 UTC: New
Related: Best web search MCP servers
FAQ
Is SEO deprecated?
No. SEO was not deprecated or archived when we last tested it on 2026-11-19 UTC.
What replaces SEO?
Nothing; SEO is not deprecated as of 2026-11-19 UTC.
Does SEO need an API key?
It connects and lists 16 tools without a key, but its tool calls need one.
Embed the badge
Every tested server gets a free embeddable badge. It shows the current score and test date and expires after 90 days. Testing is free; payment never changes a score.