seo.rank MCP server
Commit Nov 11, 2026Performs on-page SEO audits to provide scores and prioritized fixes for web pages.
Also known as moshcoder/seo.rank, seo-rank
- Stars
- 0
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- —
- Last commit
- Nov 11, 2026
- License
- MIT
What is seo.rank MCP?
seo.rank performs on-page SEO audits to provide scores and prioritized fixes for web pages.
Summary generated from the project's README
About seo.rank MCP server
Performing on-page SEO audits to receive scores and prioritized fixes is what this MCP server enables for AI agents. It evaluates web pages across approximately 25 weighted categories, including crawlability, security, content, mobile markup, social rich results, and speed. The tool provides a 0–100 score and a list of necessary improvements sorted by their importance to search engines.
Developers can connect this server to Claude using the bunx seorank mcp command. While the server defaults to remote audits via the hosted service, users can run audits in-process by setting the SEORANK_LOCAL variable. The remote service offers a free tier limited to 10 audits per visitor per day, but developers can bypass these limits by providing an SEORANK_API_KEY or by running the tool locally with the --local flag. The system uses Bun's HTMLRewriter for fast parsing without needing a headless browser.
What you can do with it
- 1Audit page SEO healthAsk an AI agent to analyze a specific URL to find its SEO score and necessary improvements.
- 2Identify high-priority fixesRequest a prioritized list of technical SEO issues that need to be addressed to improve search rankings.
- 3Check remaining audit quotaHave an AI agent verify how many more audits can be performed before hitting daily limits.
- 4Analyze content densityDetermine the most frequent words and phrases on a webpage to understand its topical focus.
Written from the project's README. Every use case is checked against a quote from it.
Automated checks
Ran Nov 15, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachablemoshcoder/seo.rank is public and reachablegithub.com/moshcoder/seo.rank ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-11-11github.com/moshcoder/seo.rank ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubseo.rank
A free, open-source on-page SEO audit. Paste a URL, get a 0–100 score and the fixes that matter most, in the order to make them. Web app, JSON API, CLI, TUI and an MCP server for AI agents.
seo.rank is a Moshpit site. It is listed on pit.world at pit.world/b/seo.rank.
# the CLI and TUI
bunx seorank audit example.com
bunx seorank audit example.com --local # on your machine, no daily limit
bunx seorank # interactive
# your agent
claude mcp add seorank -- bunx seorank mcp
What it checks
About 25 checks, weighted by how much they matter to search engines:
| Group | Checks |
|---|---|
| Crawlability | HTTP status, noindex (meta and X-Robots-Tag), robots.txt (does it block this page for Googlebot?), XML sitemap, canonical |
| Security | HTTPS, http→https redirect, HSTS |
| Content | title length, meta description length, one H1, heading outline, word count, whether the most repeated phrase is in the title or H1, image alt coverage, internal links |
| Mobile & markup | viewport, lang, charset, favicon |
| Social & rich results | Open Graph, X/Twitter card, JSON-LD types (and broken JSON-LD), hreflang |
| Speed | time to first byte, HTML size, compression |
Plus the top words and two-to-three word phrases on the page, with density.
The score is the weighted share of checks passed (a warning earns half). The fix list is sorted by what each fix is worth.
How it stays free
- No paid APIs, no headless browser. One audit is a handful of HTTP requests (the page, robots.txt, a sitemap, the http check) and a few milliseconds of parsing with Bun's built-in HTMLRewriter.
- 10 audits per visitor per day, enforced on the server. A visitor is an HMAC of their IP under a secret held only in memory and replaced at every UTC midnight, when the counts reset.
- A global cap (2,000 fresh audits a day by default) as a cost circuit breaker, and at most 8 audits in flight at once.
- A one-hour cache per URL; re-opening a recent result does not use an audit.
- Over the limit: the page says so, the API answers
429withRetry-After. Or run it yourself with--local, without limits.
Privacy
No cookies (the server strips Set-Cookie from every response) and no accounts. The pages load two things from crawlproof.com: its cookieless analytics script and an ad in a sandboxed cross-origin frame (CRAWLPROOF_AD_SLOT overrides the slot, off removes ads); the CSP allows crawlproof.com in script-src, connect-src and frame-src and nothing else. nginx keeps no access log for the site and the app logs nothing per request. Strict CSP, Referrer-Policy: no-referrer.
Safe fetching
seo.rank fetches URLs that strangers give it, so src/fetch.ts only fetches http(s) on ports 80/443, refuses credentials in URLs, checks that every address a name resolves to is public (no loopback, RFC 1918, link-local, CGNAT, ULA, multicast, v4-mapped or NAT64 forms of those), follows at most five redirects by hand and re-checks every hop, only lets the page redirect within its own site, and enforces a timeout and a 2 MB cap.
API
GET /api/audit?url=example.com (or POST {"url": …}) |
the full audit: score, grade, checks[], fixes[], page, robotsTxt, sitemap, keywords, cached, quota |
GET /api/quota |
{ limit, used, remaining, resetAt } |
GET /health |
{ ok, version, today, keyed } |
Add fields=summary (and optionally top=N, default 5, max 25) for a small answer: url, finalUrl, status, score, grade, summary, the top N fixes, checkedAt, cached, quota.
Headers X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset. CORS open, no key needed.
API keys (trusted callers)
SEORANK_API_KEYS lists keys for our own services, comma-separated, each name:key or a bare key (16+ characters). A request with Authorization: Bearer <key> or X-API-Key: <key>:
- skips the per-visitor free limit and does not count against the public global cap;
- has its own daily cap per key,
SEORANK_KEY_DAILY_LIMIT(default 50,000), reported in the sameX-RateLimit-*headers and byGET /api/quotawith the key; - runs behind its own concurrency gate,
SEORANK_KEY_CONCURRENCY(default 4), so keyed batches and public visitors cannot starve each other.
A wrong key is a 401, never a quiet fall back to the free tier. Keys are compared in constant time and never logged; /health reports per-key usage by name only. The CLI and MCP server send SEORANK_API_KEY when it is set.
Surfaces
The house rule: everything ships a TUI, a CLI, an MCP and an API.
| Web + API | bun src/server.ts (PORT, default 8790; SEORANK_DAILY_LIMIT, SEORANK_GLOBAL_DAILY_CAP, SEORANK_CONCURRENCY, SEORANK_API_KEYS, SEORANK_KEY_DAILY_LIMIT, SEORANK_KEY_CONCURRENCY, PIT_VERIFY) |
| CLI | seorank audit URL [--json] [--local] [--fixes], seorank quota, seorank open URL, seorank serve |
| TUI | seorank |
| MCP | seorank mcp: tools audit (url, format text/json) and quota. SEORANK_LOCAL=1 runs audits in-process |
The CLI, TUI and MCP server talk to https://seo.rank (or SEORANK_URL). Because seo.rank is a Moshpit name, the client resolves it with your system resolver if you are on the Moshpit network, otherwise through the Moshpit DNS-over-HTTPS resolver, and verifies the certificate against the Moshpit Root CA bundled in the package (public/moshpit-root-ca.crt). If the instance cannot be reached at all, the CLI and MCP server run the audit locally.
MCP config
{ "mcpServers": { "seorank": { "command": "bunx", "args": ["seorank", "mcp"] } } }
Run your own
git clone https://github.com/moshcoder/seo.rank && cd seo.rank
bun install
bun src/server.ts # http://127.0.0.1:8790
bun test
Production runs on bare metal with bin/install.sh (OpenInstall): a systemd unit running bun behind nginx.
More
- What AI crawlers and answer engines can read on a page: CrawlProof.
- A site built for you, with every check passing: pit.world/build.
License
MIT
seo.rank MCP questions
How can I use this with an AI agent?
You can add it to Claude using the command: claude mcp add seorank -- bunx seorank mcp.
Does the service require an account or cookies?
No, the service uses no accounts and no cookies, stripping Set-Cookie from every response for privacy.