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

SEO Content Machine

NPM · SEO-CONTENT-MACHINE-MCP · SCANNED OCT 2

Run SEO Content Machine tasks from an MCP client: scraping, crawls, Google Maps, Workspace pages.

Available components

npm · seo-content-machine-mcp 40
40 Trust /100
Trust breakdown (7 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 → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency45
Schema Quality & AI Usability0
  • Instruction-quality not yet verified: the AI judgement didn't run.Unverified
  • Nothing to assess: this server exposes no tool/resource definitions to measure a footprint for. See how to fix → Fail
  • Nothing to assess: this server has no tools to check for usage examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Nothing to assess: this server exposes no tools, so there are no tool definitions to check for coverage.Fail
Tool Safety0
  • Injection markers not yet verified: our capture carried no server instructions, tool names or descriptions for the scan to read.Unverified
  • Destructive-tool annotations not yet verified: our capture listed no tools, so there were no annotations to read.Unverified
  • Manipulation not yet verified: our capture carried no tool text for a judge to read, so we will not certify text no model has read as clean.Unverified
Capabilities20
  • Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail

Unverified: 2 categories

Categories scored 0 because we could not verify them: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Install

How do I install the SEO Content Machine MCP server?

SEO Content Machine runs locally as an npm package, launched with npx -y seo-content-machine-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 · seo-content-machine-mcp

# add to Claude Code
claude mcp add com-seocontentmachine-scm -- npx -y seo-content-machine-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "com-seocontentmachine-scm": {
      "command": "npx",
      "args": [
        "-y",
        "seo-content-machine-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-seocontentmachine-scm": {
      "command": "npx",
      "args": [
        "-y",
        "seo-content-machine-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add com-seocontentmachine-scm -- npx -y seo-content-machine-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-seocontentmachine-scm": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "seo-content-machine-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-seocontentmachine-scm --command npx --arg -y --arg seo-content-machine-mcp
# ~/.hermes/config.yaml
mcp_servers:
  com-seocontentmachine-scm:
    command: "npx"
    args: ["-y", "seo-content-machine-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-seocontentmachine-scm": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "seo-content-machine-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add com-seocontentmachine-scm -t stdio -c npx -a -y seo-content-machine-mcp
// mcp.json
{
  "mcpServers": {
    "com-seocontentmachine-scm": {
      "command": "npx",
      "args": [
        "-y",
        "seo-content-machine-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.

  • 1 Oct 26 +26
    • Malware scan: unverified → pass ▲ security
    • Known CVEs: unverified → pass ▲ security
    • Dependency health: unverified → pass ▲ functional
  • 30 Sept 26 14

    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 2 Oct 2026 · Analysed npm/seo-content-machine-mcp@1.1.0

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 →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

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. 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 →

The sandbox run completed and this package exposed no tools.

Common questions

What is the SEO Content Machine MCP server?

SEO Content Machine is an MCP server listed in the public MCP registry as com.seocontentmachine/scm. Run SEO Content Machine tasks from an MCP client: scraping, crawls, Google Maps, Workspace pages. This page covers its npm package (seo-content-machine-mcp).

Is the SEO Content Machine MCP server safe to use?

SEO Content Machine scores 40 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 2 October 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 SEO Content Machine MCP server expose?

SEO Content Machine exposes no tools. We connected to it and read its tool list, and it was empty, so it offers an MCP client nothing to call.

Is the SEO Content Machine MCP server still maintained?

SEO Content Machine is still listed as active in the MCP registry. We last reached this channel on 2 October 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 SEO Content Machine MCP server under?

SEO Content Machine declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.