Mmcp.market

pseolint MCP server

by ouranos-labs·io.github.ouranos-labs/pseolint·v0.6.4
No reviews yet

Penalty-risk audit for programmatic SEO sites: verdict, risk score, and a fix manifest.

B82/100grade B
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
B82/100

full report

Adoption
Growing

7 stars58 downloads/wk

Reviews

Write one

Nobody has reviewed pseolint yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

pseolint tools (4)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • pseolint_audit_site
  • pseolint_check_page_technical

    Use when a user asks to check a specific page URL for technical SEO issues. Checks per-page rules only: canonical tags, Open Graph tags, JSON-LD schema, robots directives, meta tags, thin content, and author signals. Does NOT check cross-page rules (duplicates, cannibalization, linking) — use pseolint_audit_site for those. Both human-readable text and structured data (structuredContent) are return

  • pseolint_explain_score

    Use when a user wants to understand WHY their pseolint verdict is concerning/critical, what categories are failing, and what to fix first. Returns a prioritized breakdown with quick wins listed before structural fixes, plus a pass/fail verdict against the risk threshold. Both human-readable text and structured data (structuredContent) are returned. A failing threshold is reported via `passed`, not

  • pseolint_orchestrate_audit

    Use when a user wants concrete, paste-able fixes (rewritten H1s, JSON-LD blocks, robots.txt patches, internal-link suggestions) — not just a list of issues.

Public scan report

scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it

no findings
  • Code scan7 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 5 days ago15/15
  • Maintainer identityregistry namespace matches repository owner7/10
Overall 82/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

What the publisher says

From the pseolint repository's README, as published. We do not edit it. Read it on GitHub

Methodology · Leaderboard · Report a bug · Skills for agents

The only tool purpose-built for programmatic SEO compliance. It shifts the unit of analysis from URL to template: point it at a 10,000-URL pSEO directory and pseolint identifies the template clusters (e.g. /listing/:slug, /category/:slug), samples K pages from each, and produces a per-template verdict + variance metric. Fix one template, fix N pages.

npx pseolint http://localhost:3000

Table of contents

  • Why this exists
  • How pseolint differs
  • Quick Start
  • What It Checks: the 65 rules
  • CLI Options
  • GitHub Action
  • Fix rail: from audit to pull request
  • Skills for Claude & coding agents
  • Roadmap
  • Contributing

Skills for Claude & coding agents (new)

Design pages that pass before you crawl them. The skills/ suite gives Claude (and any agent that supports the skills / Claude Code plugin format) programmatic-SEO and answer-engine optimization (AEO / GEO) guidance where every recommendation is bound to a runnable pseolint rule:

npx skills add ouranos-labs/pseolint --skill pseolint aeo
  • pseolint: full-lifecycle programmatic SEO: design → build → audit → fix → gate.
  • aeo: get cited in AI Overviews / ChatGPT / Perplexity, not just ranked.

Unlike prose checklists, these have teeth: the design-time advice ends in npx pseolint pass/fail. See skills/README.md.

Why this exists

Programmatic SEO works, when it works. The gap between "1,000 indexed pages" and "1,000 pages that survive a SpamBrain pass" is where most pSEO sites die. The Helpful Content Update made that gap permanent.

Existing SEO tools (Screaming Frog, Sitebulb, Ahrefs Site Audit) were built for editorially-curated sites. They check pages one at a time. But the SpamBrain risks of pSEO are between pages: doorway clusters, near-duplicates, entity-swap templates, thin-content propagation. You can't catch them with per-page rules.

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Install directly

Runs npx -y @pseolint/mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add pseolint -- npx -y @pseolint/mcp
Add to Cursor

pseolint: common questions

Is pseolint MCP server safe?
Mostly: it is graded B (82/100). Read the pseolint safety report
How do I install pseolint?
It runs on your machine. Copy the Claude Code, Claude Desktop or Cursor config from the install section.
Does pseolint need an API key?
Yes. The registry entry asks for ANTHROPIC_API_KEY.
Is pseolint maintained?
The last commit was 5 days ago (2026-09-22). The latest release is v0.6.4.
What can I use instead of pseolint?
Servers from other publishers that do the same job: Crawlie MCP server, VibeSEO MCP server and site-spec MCP server. Compare all pseolint alternatives.

Alternatives to pseolint

Same job from other publishers: the closest match first, then the best rated.

All pseolint alternatives →
  • Crawlie
    Technical SEO + GEO (AI-search) site audits: hosted crawls, prioritized fixes, report diffs.
    A
  • VibeSEO
    SEO research, keyword discovery, site audits, Search Console, backlinks and content workflow.
    A
  • site-spec
    MCP server: audit any website for SEO, accessibility, and AI-searchability, then auto-fix it.
    A
  • SEO Data
    SEO data for AI agents: Google SERP, keyword research, backlinks, site audits, AI answer visibility.
    A
  • mcp-seo-audit
    Technical SEO site audit MCP: health score, issues, robots, sitemap, JSON-LD.
    B
pseolint vs Crawliepseolint vs VibeSEOpseolint vs site-spec

More from ouranos-labs →