Seo Audit Console MCP Server
@houtini/seo-audit-console
npm
v0.8.0
Published by @houtini — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.
The complete technical SEO audit at conversation speed: Google Search Console history + a first-party crawl + on-demand DataForSEO, merged into one prioritised audit inside Claude - 90 checks ranked by recoverable clicks, with paste-ready fixes, keyword a
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 4 = 96. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −3 | capability blast radius (moderate) — client exposure if the model is manipulated |
| −1 | publisher verification (public source) — no provenance, but the source is public and inspectable |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Findings 1
medium Unconstrained URL/host parameter "url" on "normalize_url"MTC-CAP-007
Tool "normalize_url" takes a URL/host parameter "url" with no allowlist/pattern. An outbound-request tool with an unbounded destination enables SSRF and cloud-metadata access (e.g. 169.254.169.254).
Fix: Allowlist destinations or constrain the parameter; block private/link-local addresses server-side.
Location: tool normalize_url · inputSchema.properties.url
Tools 48
Each tool and what it can reach — statically extracted from the published source.
check_agent_readinessingests untrusted inputcheck_crawl_statusingests untrusted inputdata_locationingests untrusted inputdata_storageingests untrusted inputlist_templatesingests untrusted inputnews_discoveryingests untrusted inputnormalize_urlingests untrusted inputpull_backlinksingests untrusted inputquery_dataingests untrusted inputrecon_targetsingests untrusted input
Show 38 more tools ↓
run_auditingests untrusted inputscore_passagesingests untrusted inputstart_crawlingests untrusted inputsuggest_pagesingests untrusted inputsync_gscingests untrusted inputtop_pagesingests untrusted inputcheck_sync_statusno sensitive capabilitycompetitors_domainno sensitive capabilitycomposition_cookbookno sensitive capabilitycontent_opportunitiesno sensitive capabilitydetect_changesno sensitive capabilitydomain_visibilityno sensitive capabilitydraft_contentno sensitive capabilityexport_reportno sensitive capabilityfix_findingno sensitive capabilityinspect_urlsno sensitive capabilitykeyword_listno sensitive capabilitykeyword_volumeno sensitive capabilitylink_intersectno sensitive capabilitylist_checksno sensitive capabilitylist_propertiesno sensitive capabilitymarket_sizingno sensitive capabilitypage_intersectionno sensitive capabilitypage_lighthouseno sensitive capabilityquery_auditno sensitive capabilityranked_keywordsno sensitive capabilityrecon_todosno sensitive capabilityrelated_termsno sensitive capabilityresolve_entitiesno sensitive capabilitysave_recon_todono sensitive capabilitysearch_intentno sensitive capabilityseo_audit_helpno sensitive capabilityserp_featuresno sensitive capabilityserve_dashboardno sensitive capabilitytopic_gapsno sensitive capabilitytopic_trendno sensitive capabilitytrack_ranksno sensitive capabilityyoutube_discoveryno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (48 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions 9
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v0.8.0 latest |
A 96/100 | 1 | 1.13.0 | 2026-09-05 |
v0.7.8 |
A 96/100 | 1 | 1.12.1 | 2026-08-21 |
v0.6.0 |
A 96/100 | 1 | 1.12.1 | 2026-08-17 |
v0.5.1 |
A 96/100 | 1 | 1.12.1 | 2026-08-16 |
v0.5.0 |
A 96/100 | 1 | 1.12.1 | 2026-08-14 |
Show 4 more versions ↓
v0.4.9 |
A 96/100 | 1 | 1.12.1 | 2026-08-09 |
v0.3.0 |
A 96/100 | 1 | 1.12.1 | 2026-08-07 |
v0.2.3 |
A 96/100 | 1 | 1.12.1 | 2026-08-05 |
v0.2.0 |
A 96/100 | 1 | 1.12.1 | 2026-08-04 |
Embed this score
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
Verify this score yourself
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan @houtini/seo-audit-console --onlineMore in Security & Testing
The Stripe Agent Toolkit enables popular agent frameworks including LangChain and Vercel's AI SDK to integrate with Stripe APIs through function calling.
MCP (Model Context Protocol) server for AgentGate. Enables Claude and other MCP-compatible AI assistants to request approvals.
Scan any website for AI agent readiness, payment protocols, and discovery endpoints
MCP server for aigently security guardrails — reads static catalog-data JSON, zero API dependency
Governed threat modeling, code threat verification, traceability & compliance, as MCP tools.
Governed threat modeling, code threat verification, traceability & compliance, as MCP tools.