Should my agent depend on the MCP server io.github.retampweb/pa1m-seo?

Verdict: allow — rich-slow-shared — safe to depend on As of 2026-08-15T11:28:18Z: a dated observation with receipts, not a warranty.

Pa1m SEO

io.github.retampweb/pa1m-seo

Pay-per-call SEO agent: keyword research, SERP analysis, on-page optimization. x402, USDC on Base.

— the operator's own registry description reported

Publisher io.github.retampweb · first seen 2026-08-12 · endpoint https://seo.hypa1m.xyz/mcp

allow

verdict

rich-slow-shared

cluster

ok_tools

answers

tools served

Dependency rating derived

allow — rich-slow-shared — safe to depend on

Cluster rich-slow-shared · distinctiveness 0.491 (moderate). Every figure is a percentile or class within the 11,094-server census — see the whole spectrum.

Reach — can an agent get to it?

answersalive_tools

latency384 ms

vs populationslow

protocolcurrent

authopen

Use — can it use it?

tools36

vs populationhigh

capabilities2

harnessA

Trust — can it rely on it?

identityshared

servers on its host1

servers on its domain3

verifiabilityunassessed

duplicate inventoryno

drift events0

answers trueno primary

🔏 Signed receipt rr_e7f52c42a168acd4523fff5e · ed25519 · key rs-rcpt-2026-08 — this rating is tamper-evident; an agent gets the full signature from check_server and can verify it against the published key.

Tools last seen

analyze_endpoint backlinks_check backlinks_check_bulk backlinks_status brief check_accessibility check_ai_geo check_content check_core_seo check_crawlability check_eeat check_html check_i18n check_images check_js_rendering check_legal check_links check_mobile check_performance check_redirects check_security check_social check_structured_data check_technical check_url_structure get_status google_check_report google_check_status google_index_check google_index_check_bulk google_index_report google_index_status google_index_submit google_index_submit_bulk scan_full scan_quick

Harness readiness observed

Can an agent's harness pick this tool and call it correctly? Graded on the three things an agent reads — name, description, typed parameters. Band A — an agent can pick and call these reliably.

legibility check	tools passing	ok
name is clear & specific	36/36	✓
has a description	36/36	✓
description is substantive	36/36	✓
parameters are typed	36/36	✓
parameters are described	26/36	26/36

36 of 36 tools graded · 36 with a captured input schema. RS-008, Tier-1 — no domain knowledge, applies to any tool. “Alive” is not the same as “usable”.

Truth checks observed

Not in the Tier-2 trade lane, or not yet checked. Tier-2 re-derives a server's answers against published primary sources — see truth checks.

Protocol conformance observed

2025-06-18

protocol version

—

session model

1.28.1

server version Pa1m SEO

Capabilities: experimental tools

Drift

No confirmed drift on record. Baseline set 2026-08-14; changes appear here after human review.

History observed

Every probe we made, oldest → newest (2 shown, 2026-08-12 → 2026-08-14). Green answered · amber answered-but-walled · red no useful answer. A gap in our cadence is a gap in coverage, not evidence about the server.

changelog (1 events)

date	type	what changed
2026-08-12	outcome	first probe: ok_tools

raw probe records

probed (UTC)	outcome	http	ms	protocol
2026-08-14T20:00:10Z	ok_tools	200	384	2025-06-18
2026-08-12T05:35:22Z	ok_tools	200	388	2025-06-18

Watch or embed this verdict

Operators: put the live verdict in your README — it updates with every census, links back here, and is a dated observation, never a warranty:

[![Robin Saige verdict](https://robinsaige.com/badge/io.github.retampweb/pa1m-seo.svg)](https://robinsaige.com/s/io.github.retampweb/pa1m-seo)

Depend on it? Subscribe to its change feed — outcome changes and confirmed drift, no account needed. Building on it? The full dossier as JSON — verdict, rating, truth checks, history — stable enough to gate CI on.

← overview