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.

CiteWire

NPM · CITEWIRE · SCANNED SEP 22

Attribution-first MCP server for free news sources and free article APIs.

Available components

npm · citewire 83
+3 this week 83 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 & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to Openly-Useful/citewire). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 29 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability69
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 39 tokens (~39/item across 0 items; 0 tools + 0 resources), lean.Pass
  • Nothing to assess: this server has no tools to check for usage examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage0
  • Nothing to assess: this server exposes no tools, so there are no tool definitions to check for coverage.Fail
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • Destructive-tool annotations not yet verified: our capture listed no tools, so there were no annotations to read.Unverified
  • An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Install

How do I install the CiteWire MCP server?

CiteWire runs locally as an npm package, launched with npx -y citewire. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · citewire

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

  • 22 Sept 26 0
    • Stability: 0.97 → pass security
  • 21 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.

  • 18 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

  • 8 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

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 22 Sept 2026 · Analysed npm/citewire@0.2.0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo Openly-Useful/citewire
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/Openly-Useful/citewire/.github/workflows/release.yml@refs/tags/v0.2.0
Rekor log index 2573714229
Predicate type https://slsa.dev/provenance/v1
Subject digest sha512:1fb838c499c373c6dd383b0356fa413622130f4960c14c261cc6682a5fb61ef7750fd6e9dd3f9fcbff4f42be9ae7fb361e8c2fb2dea1c523cf5ed1e33

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 CiteWire MCP server?

CiteWire is an MCP server listed in the public MCP registry as io.github.Openly-Useful/citewire. Attribution-first MCP server for free news sources and free article APIs. This page covers its npm package (citewire).

Is the CiteWire MCP server safe to use?

CiteWire scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 CiteWire MCP server expose?

CiteWire 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 CiteWire MCP server still maintained?

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

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