Mehmoodqureshi Seo MCP Server
@mehmoodqureshi/seo-mcp
npm
v0.1.6
Published by @mehmoodqureshi — 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.
An SEO MCP server (stdio CLI). Free, keyless on-page & technical SEO tools — single-page and site-wide audits, robots.txt, sitemap, structured-data, broken-link and keyword checks, professional PDF reports, plus PageSpeed/Lighthouse (Google PSI or local h
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 2
medium Unconstrained URL/host parameter "url" on "check_robots"MTC-CAP-007
Tool "check_robots" 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 check_robots · inputSchema.properties.url
medium Dynamic module load from a non-literal (dist/src/seo/lighthouse-local.js)MTC-SRC-005
In the server's implementation (`dist/src/seo/lighthouse-local.js:21`): Loading a module chosen at runtime (from a variable) can pull in and run attacker-influenced code paths. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: on('specifier', 'return import(specifier)'); let cachedHint; function missingDepHint(err) { const msg = err instance
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/src/seo/lighthouse-local.js
Tools 10
Each tool and what it can reach — statically extracted from the published source.
check_robotsingests untrusted inputaudit_pageno sensitive capabilityaudit_siteno sensitive capabilitycheck_sitemapno sensitive capabilityexport_audit_pdfno sensitive capabilityexport_site_pdfno sensitive capabilityextract_schemano sensitive capabilityfind_broken_linksno sensitive capabilitykeyword_ideasno sensitive capabilitypagespeedno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (10 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 3
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.1.6 latest |
A 96/100 | 2 | 1.13.0 | 2026-09-07 |
v0.1.5 |
A 96/100 | 2 | 1.12.1 | 2026-08-03 |
v0.1.4 |
A 96/100 | 2 | 1.12.1 | 2026-07-29 |
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 @mehmoodqureshi/seo-mcp --onlineOther implementations of Mehmoodqureshi Seo 7
Independent packages implementing the same tool, scanned with the same engine. Compare all 8 side by side →
SEO toolkit MCP server — analyze meta tags, robots.txt, sitemaps, keyword density, readability, and heading structure
MCP Server for generating SEO page content
MCP server for Google Search Console and Bing Webmaster Tools.
A free SEO tool MCP (Model Control Protocol) service based on Ahrefs data. Includes features such as backlinks, keyword ideas, and more.
Open-source SEO analysis toolkit for LLM agents — CLI + MCP server.
SEO MCP with V2.1 next_action and optional fields (backward compatible)
More in Marketing & Social
Official Abyssfall game info, newsletter double opt-in, and merch reservation tools.
AdCritter ads platform: docs, API reference, app scaffolding, and white-label integration.
Google AdSense MCP Server - Monitor earnings, reports, and account health via Claude/AI
Operational empathy for technical founders + PE/VC operators navigating high-stakes B2B interactions. 28 MCP tools + CLI: ICP scoring, persona simulation, battlecards, deal classification, prospect discovery, investor matching, founder wellness, plus mark
MCP server for Bing Webmaster Tools — SEO site management, URL submission, sitemaps, stats, keywords
MCP (Model Context Protocol) server that helps AI agents use Primer Brand (@primer/react-brand) correctly when building GitHub marketing and landing pages.