pseolint
NPM · @PSEOLINT/MCP · SCANNED SEP 24
Penalty-risk audit for programmatic SEO sites: verdict, risk score, and a fix manifest.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security90
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects undici 5.29.0, reached via @pseolint/core > ai > @ai-sdk/provider-utils > undici. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 34 of 128 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 30 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability68
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1141 tokens (~285/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the pseolint MCP server?
pseolint runs locally as an npm package, launched with npx -y @pseolint/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pseolint/mcp
claude mcp add ouranos-labs-pseolint -- npx -y @pseolint/mcp
{
"mcpServers": {
"ouranos-labs-pseolint": {
"command": "npx",
"args": [
"-y",
"@pseolint/mcp"
]
}
}
} {
"servers": {
"ouranos-labs-pseolint": {
"command": "npx",
"args": [
"-y",
"@pseolint/mcp"
]
}
}
} codex mcp add ouranos-labs-pseolint -- npx -y @pseolint/mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ouranos-labs-pseolint": {
"type": "local",
"command": [
"npx",
"-y",
"@pseolint/mcp"
],
"enabled": true
}
}
} openclaw mcp add ouranos-labs-pseolint --command npx --arg -y --arg @pseolint/mcp
mcp_servers:
ouranos-labs-pseolint:
command: "npx"
args: ["-y", "@pseolint/mcp"] {
"McpServers": {
"ouranos-labs-pseolint": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@pseolint/mcp"
]
}
}
} assistant mcp add ouranos-labs-pseolint -t stdio -c npx -a -y @pseolint/mcp
{
"mcpServers": {
"ouranos-labs-pseolint": {
"command": "npx",
"args": [
"-y",
"@pseolint/mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 24 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Sept 26 0
- Security disclosure: unverified → fail ▼ functional
- 22 Sept 26 +1
- Security disclosure: fail → unverified ▼ functional
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 −3
- Stability: pass → 0.80 functional
- 18 Sept 26 0
- Stability: 0.97 → pass security
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 24 Sept 2026 · Analysed npm/@pseolint/mcp@0.6.4
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 12 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-2mjp-6q6p-2qxm | CVE-2026-1525 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L | yes |
| GHSA-35p6-xmwp-9g52 | CVE-2026-6733 | low | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N | yes |
| GHSA-4992-7rv2-5pvq | CVE-2026-1527 | medium | CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N | yes |
| GHSA-8xcm-r25x-g524 | CVE-2026-16728 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N | yes |
| GHSA-g8m3-5g58-fq7m | CVE-2026-11525 | low | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N | yes |
| GHSA-g9mf-h72j-4rw9 | CVE-2026-22036 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-m8rv-5g2x-5cg5 | CVE-2026-15157 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N | yes |
| GHSA-p88m-4jfj-68fv | CVE-2026-9679 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N | yes |
| GHSA-v3r7-h72x-cjcm | CVE-2026-16729 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N | yes |
| GHSA-v9p9-hfj2-hcw8 | CVE-2026-2229 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-vrm6-8vpv-qv8q | CVE-2026-1526 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-vxpw-j846-p89q | CVE-2026-12151 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 128 packages
| Packages resolved | 128 |
|---|---|
| Deprecated | 1 |
| Stale | 34 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
pseolint_audit_site Audit Site for SpamBrain Risk ~440
Use when a user asks to check their website for SEO issues, SpamBrain risk, duplicate content, thin pages, or before deploying a programmatic SEO site. Crawls the site, runs 40+ rules scored across 4 categories (integrity, discoverability, citation, data), and returns a verdict (ready/caution/concerning/critical) plus a numeric risk score (0-100, lower is better) with actionable findings. Pre-flight site classification suppresses pSEO-targeted rules on small marketing sites and blogs unless strict mode is set. When the audited site has ≥2 detected URL templates, the response includes a `templates` array with per-template verdicts, risk scores, category grades, variance metrics (uniformityScore, topDriver), and audited-URL counts. Both human-readable text and structured data (structuredContent) are returned. A high-risk site is NOT a tool error — check the `passed` field / `verdict`, not `isError`.
| Name | Type | Req | Description |
|---|---|---|---|
| authorityScore | integer | – | Bring-your-own domain authority (0-100). >=80 shifts the verdict one tier lenient on established brands; <=30 shifts one tier stricter on newer/lower-authority operators. The raw risk number is never… |
| format | string | – | Text-content format. Use 'json' for full machine-readable output, 'console' for a human-readable summary. structuredContent is always returned regardless. |
| sampleSeed | integer | – | Integer seed for deterministic stratified sampling. Same seed + same sampleSize = same audit = same verdict, run after run. |
| sampleSize | integer | – | Audit a random subset of N pages. 0 = all pages up to the MCP cap of 50. Set explicitly to override the cap (up to 500). |
| source | string | yes | URL (e.g. http://localhost:3000) or local directory path (e.g. ./out) to audit |
| threshold | integer | – | Risk threshold — `passed` is false if risk >= this value (default: 40, semantically equivalent to 'caution' verdict) |
| Name | Type | Req | Description |
|---|---|---|---|
| categories | object | yes | – |
| findingCount | number | yes | – |
| findings | array | yes | Up to 100 findings, severity-ordered. See findingCount for the total and findingsTruncated for whether any were dropped. |
| findingsTruncated | boolean | – | True when more than the cap of findings exist and the structured array was shortened. Use json format or the CLI for the full set. |
| pageCount | number | yes | – |
| passed | boolean | yes | – |
| risk | number | yes | – |
| templates | array | – | – |
| textTruncated | boolean | – | True when the text content (not the structured data) was shortened or replaced to fit the size cap. |
| threshold | number | yes | – |
| verdict | string | yes | – |
No examples provided.
pseolint_check_page_technical Check Single Page Technical SEO ~130
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 returned.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Full URL of the page to check (e.g. https://yoursite.com/templates/california-llc) |
| Name | Type | Req | Description |
|---|---|---|---|
| findings | array | yes | – |
| issueCount | number | yes | – |
| url | string | yes | – |
No examples provided.
pseolint_explain_score Explain pseolint Verdict ~207
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 `isError`.
| Name | Type | Req | Description |
|---|---|---|---|
| authorityScore | integer | – | Bring-your-own domain authority (0-100). >=80 shifts the verdict one tier lenient; <=30 shifts one tier stricter. Raw risk unchanged. |
| sampleSeed | integer | – | Integer seed for deterministic stratified sampling. Same seed = same audit = same verdict. |
| source | string | yes | URL (e.g. http://localhost:3000) or local directory path (e.g. ./out) to audit |
| threshold | integer | – | Risk threshold for the pass/fail verdict (default: 40) |
| Name | Type | Req | Description |
|---|---|---|---|
| categories | object | yes | – |
| pageCount | number | yes | – |
| passed | boolean | yes | – |
| risk | number | yes | – |
| threshold | number | yes | – |
| topRules | array | yes | – |
| verdict | string | yes | – |
No examples provided.
pseolint_orchestrate_audit Orchestrate AI-Native pSEO Audit ~364
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. An LLM drives 25 tools (sitemap fetch, template clustering, per-page rule checks, AEO probes) and produces a fix manifest with structured patches, each validated against a deterministic schema. Costs real money (~$1-3 per audit on managed Anthropic). Capped at $2 / 60 tool calls / 180 seconds by default — adjust if the user asks for a deeper run. Returns a text summary plus a compact structured summary (structuredContent); pass format:'json' to also get the full manifest in the text content. The structured `reason` field reports why the run stopped — an incomplete run is not flagged via isError. The full manifest can be streamed via the CLI: `pseolint orchestrate <domain> --manifest-out manifest.json`.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | URL of the site to audit (e.g. https://example.com). The orchestrator's first tool call fetches the sitemap. |
| format | string | – | 'summary' = terse text for chat UI; 'json' = full manifest + validation + diff in the text content. |
| maxCostUsd | number | – | Hard USD cap for this session. Default $2 (conservative for MCP-invoked sessions). Min $0.10, max $50. |
| maxToolCalls | integer | – | Hard tool-call cap. Default 60. Max 500. |
| maxWallSeconds | integer | – | Hard wall-clock cap in seconds. Default 180 (3 minutes). Min 10, max 900. |
| Name | Type | Req | Description |
|---|---|---|---|
| categories | object | – | – |
| completed | boolean | yes | – |
| domainLevelCount | number | – | – |
| pageCount | number | – | – |
| patches | object | – | – |
| reason | string | yes | – |
| templateCount | number | – | – |
| usage | object | yes | – |
| verdict | string | – | – |
No examples provided.
What is the pseolint MCP server?
pseolint is an MCP server listed in the public MCP registry as io.github.ouranos-labs/pseolint. Penalty-risk audit for programmatic SEO sites: verdict, risk score, and a fix manifest. This page covers its npm package (@pseolint/mcp).
Is the pseolint MCP server safe to use?
pseolint scores 80 out of 100 on VerifyMCP. We recorded 12 known advisories against it as of 24 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the pseolint MCP server expose?
pseolint exposes 4 tools: pseolint_audit_site, pseolint_explain_score, pseolint_check_page_technical, pseolint_orchestrate_audit. Their descriptions and schemas cost roughly 1,141 tokens of context every time the server is loaded.
Is the pseolint MCP server still maintained?
pseolint is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the pseolint MCP server under?
pseolint declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.