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.

Cite42

NPM · @CITE42/MCP · 2 COMPONENTS · SCANNED OCT 9

AI visibility and SEO data for AI agents: citations, keywords, trends, and scheduled trackers.

Available components

remote · mcp.cite42.dev 38 npm · @cite42/mcp 31
−2 this week 31 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 Security89
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects @modelcontextprotocol/client 2.0.0, reached via @mastra/mcp > @modelcontextprotocol/client. A fixed version is available.Fail
  • No install/post-install scripts declared.Pass
  • 85 of 242 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency19
Schema Quality & AI Usability0
  • Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.Unverified
Stability & Change Management0
  • Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.Unverified
Tool Coverage0
  • Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet.Unverified
Tool Safety0
  • Tool safety not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet.Unverified
Capabilities0
  • Protocol version not yet verified: we do not have a sandbox capture of the MCP handshake this version of the package performs yet.Unverified

Unverified: 5 categories

Categories scored 0 because our sandbox 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

How do I install the Cite42 MCP server?

Cite42 runs locally as an npm package, launched with npx -y @cite42/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 · @cite42/mcp

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

  • 7 Oct 26 −2
    • CVE-2026-104850 affects this package: high ▼ security
    • Known CVEs: pass → fail ▼ 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 safety: Tool safety not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. security
    • Capabilities: Protocol version not yet verified: we do not have a sandbox capture of the MCP handshake this version of the package performs yet. functional
    • Tool coverage: Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. functional
    • Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. functional
    • Package version: 0.7.0 → 0.8.0 functional
  • 30 Sept 26 0
    • Package version: 0.6.2 → 0.7.0 functional
  • 29 Sept 26 +10
    • Known CVEs: unverified → pass ▲ security
    • Dependency health: unverified → 0.84 ▲ functional
  • 28 Sept 26 −10
    • Known CVEs: pass → unverified ▼ security
    • Dependency health: 0.83 → unverified ▼ functional
    • Package version: 0.5.0 → 0.6.2 functional
    • Package version: 0.5.0 → 0.6.1 functional
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 12 Sept 26 +25
    • Malware scan: unverified → pass ▲ security
    • Known CVEs: unverified → pass ▲ security
    • Dependency health: unverified → 0.83 ▲ functional
  • 11 Sept 26 −25
    • Known CVEs: pass → unverified ▼ security
    • Malware scan: pass → unverified ▼ security
    • Dependency health: 0.83 → unverified ▼ functional
    • Package version: 0.4.0 → 0.5.0 functional
  • 4 Sept 26 0
    • Stability: Stability not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to compare. security
    • Tool safety: Tool safety not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool text to scan. security
    • Capabilities: Protocol version not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we never saw its MCP handshake. functional
    • Tool coverage: Tool coverage not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool definitions to assess. functional
    • Schema quality: Schema quality not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to assess. functional
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 9 Oct 2026 · Analysed npm/@cite42/mcp@0.8.0

Provenance Inconclusive

We could not complete the check, so nothing is claimed either way. This is a gap on our side, not a finding about the package.

Result Inconclusive
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 222 packages
Packages resolved 222
Stale 80
Tree resolution Partial

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

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 →

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.

Common questions

What is the Cite42 MCP server?

Cite42 is an MCP server listed in the public MCP registry as dev.cite42/mcp. AI visibility and SEO data for AI agents: citations, keywords, trends, and scheduled trackers. This page covers its npm package (@cite42/mcp).

Is the Cite42 MCP server safe to use?

Cite42 scores 31 out of 100 on VerifyMCP. 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.

Is the Cite42 MCP server still maintained?

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

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