Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

pseolint

NPM · @PSEOLINT/MCP · SCANNED AUG 3

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

Available components

npm · @pseolint/mcp 33
−9 this week 33 Trust /100
Trust breakdown (6 categories)

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 →

Supply Chain Security79
  • 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
  • Only part of the dependency tree could be resolved (127 of 132), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability0
  • Schema quality not yet verified: our sandbox run of this package did not complete, so we have no schema to assess.Unverified
Stability & Change Management0
  • Stability not yet verified: our sandbox run of this package did not complete, so we have no schema to compare.Unverified
Tool Coverage0
  • Tool coverage not yet verified: our sandbox run of this package did not complete, so we have no tool definitions to assess.Unverified
Capabilities0
  • Protocol version not yet verified: our sandbox run of this package did not complete, so we never saw its MCP handshake.Unverified

Unverified: 4 categories

Categories scored 0 because our sandbox run of this package has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · @pseolint/mcp

# add to Claude Code
claude mcp add ouranos-labs-pseolint -- npx -y @pseolint/mcp
# add to Codex CLI
codex mcp add ouranos-labs-pseolint -- npx -y @pseolint/mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ouranos-labs-pseolint": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pseolint/mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add ouranos-labs-pseolint --command npx --arg -y --arg @pseolint/mcp
# ~/.hermes/config.yaml
mcp_servers:
  ouranos-labs-pseolint:
    command: "npx"
    args: ["-y", "@pseolint/mcp"]
// mcp.json
{
  "mcpServers": {
    "ouranos-labs-pseolint": {
      "command": "npx",
      "args": [
        "-y",
        "@pseolint/mcp"
      ]
    }
  }
}
Changelog

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.

  • 2 Aug 26 +10
    • CVE-2026-1526 affects this package: high ▼ security
    • CVE-2026-11525 affects this package: high ▼ security
    • CVE-2026-1527 affects this package: high ▼ security
    • CVE-2026-9679 affects this package: high ▼ security
    • CVE-2026-1525 affects this package: high ▼ security
    • CVE-2026-6733 affects this package: high ▼ security
    • CVE-2026-22036 affects this package: high ▼ security
    • CVE-2026-12151 affects this package: high ▼ security
    • CVE-2026-2229 affects this package: high ▼ security
    • Known CVEs: unverified → fail ▼ security
    • Provenance: unverified → fail ▼ security
    • Install scripts: unverified → pass ▲ security
    • Malware scan: unverified → pass ▲ security
    • Stability: Stability not yet verified: our sandbox run of this package did not complete, so we have no schema to compare. security
    • Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
    • Tool coverage: 100 → unverified ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • License: unverified → pass ▲ functional
    • Dependency health: unverified → partial ▲ functional
    • Maintenance: unverified → pass ▲ functional
    • First check of Schema quality: unverified functional
    • First check of Schema quality: unverified functional
    • Licence: MIT functional
  • 1 Aug 26 +5
    • Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
    • MCP protocol: unverified → pass ▲ functional
  • 31 Jul 26 −24
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Jul 26 42

    First indexed and scored.

Diagnostics

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 3 Aug 2026 · Analysed npm/@pseolint/[email protected]

Provenance none

Ecosystem: npm · Outcome: none

Vulnerabilities 10 findings
ID CVE Severity Vector Fix available
GHSA-866g-f22w-33x8 CVE-2026-8769 medium CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L no
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-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-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-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
Dependencies 127 packages

127 packages in the resolved dependency tree · 125 deprecated · 32 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools

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.

Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.