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.

Refract

NPM · @REFRACT-ORG/CLI

git log for Wikipedia: typed events for changed sentences, citations, and structure on any page.

Available components

+28 this week 82 Trust /100

Last scanned (22 hours ago)

Scores higher than 71% of npm servers

Category Education and Research

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 Security98
  • 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
  • 5 of 11 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to zz-plant/refract). View diagnostics → Pass
  • Clear OSI-approved license (AGPL-3.0).Pass
  • Actively maintained (last published 1 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability66
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1126 tokens (~140/item across 8 items; 8 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 Management30
  • Stability observed for 9 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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 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
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

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.

  • 21 Nov 26 +1

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

  • 19 Nov 26 0
    • Schema quality: 124 → 140 ▼ functional
    • Package version: 0.6.2 → 0.7.0 functional
  • 17 Nov 26 +1

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

  • 15 Nov 26 +26
    • Malware scan: unverified → pass ▲ security
    • Known CVEs: unverified → pass ▲ security
    • Dependency health: unverified → 0.83 ▲ functional
  • 14 Nov 26 −24
    • Malware scan: pass → unverified ▼ security
    • Known CVEs: pass → unverified ▼ security
    • Dependency health: 0.83 → unverified ▼ functional
    • Schema quality: pass → fail ▼ functional
    • Stability: unverified → 0.07 ▲ functional
    • Package version: 0.6.1 → 0.6.2 functional
  • 13 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
    • Security disclosure: unverified → pass ▲ functional
  • 12 Nov 26 63

    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 21 Nov 2026 · Analysed npm/@refract-org/cli@0.7.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 zz-plant/refract
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/zz-plant/refract/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3998925151
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:76ede61d80c12e1376d5da1e20f9ca3d2b6a238ada8e7e229522b7f11d59e7af5a749796de205f475aca08c2a3c6b58db1d534f2ad82be4312d2c82aa

Background: How many MCP packages publish verified provenance →

Dependencies 11 packages
Packages resolved 11
Stale 5
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 8 exposed · ~1,126 tokens

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 →

Tool Tokens
analyze ~157

Analyze a MediaWiki page's full edit history. Returns a structured event stream: claims, citations, sections, templates, categories, wikilinks, and reverts — all provenance-tagged with revision IDs and timestamps.

NameTypeReqDescription
apistring–MediaWiki API base URL. Defaults to English Wikipedia.
configobject–Analyzer configuration overrides
depthstring–Analysis depth: brief (event metadata only), detailed (text included), forensic (full wikitext)
fromstring–Start revision ID
pagestringyesPage title (e.g. 'Bitcoin', 'Climate change')
sincestring–Re-observe from ISO timestamp
tostring–End revision ID

No output schema declared.

No examples provided.

claim ~74

Track a specific sentence's provenance across revisions. Shows when a sentence first appeared, was removed, or was reintroduced — with section context and revision IDs.

NameTypeReqDescription
apistring–MediaWiki API base URL
pagestringyesPage title
textstringyesSentence text to track (partial match supported)

No output schema declared.

No examples provided.

classify ~138

Ask a model to classify a single observation boundary — revert detection, sentence similarity, edit type, template signal, or activity spike. Uses MCP sampling if no API key is configured, otherwise calls the configured provider.

NameTypeReqDescription
apiKeystring–API key for the inference provider (optional; falls back to MCP sampling)
boundarystringyesWhich inference boundary to classify
endpointstring–Inference provider endpoint URL (default: OpenAI-compatible)
inputobjectyesInput data for the boundary (field names vary by boundary type)
modelstring–Model name (default: gpt-4o-mini)

No output schema declared.

No examples provided.

cron ~45

One-shot re-observation for cron: reads a pages file, runs analysis, reports new events.

NameTypeReqDescription
pagesFilestringyesPath to file with page titles (one per line)

No output schema declared.

No examples provided.

export ~69

Export page analysis as structured JSON. Returns all events with revision, section, and timestamp provenance.

NameTypeReqDescription
apistring–MediaWiki API base URL
depthstring–Analysis depth
pagestringyesPage title
sincestring–Re-observe from ISO timestamp

No output schema declared.

No examples provided.

get_statement_history ~259

Track a statement's trajectory across a page's revisions. A revision matches when its text contains the statement after lowercasing and collapsing whitespace, or else, partially, when one sentence holds at least 70% of the statement's words longer than three characters (at least three such words); a partial match does not establish the same meaning. Returns each transition (first seen, wording changed, removed, reintroduced) with the fetched revisions it lies between, revert evidence, how many revisions the result held, and the nearest remaining sentence on a removal; plus matched revisions, an overall status, and a short change summary.

NameTypeReqDescription
apistring–MediaWiki API base URL. Defaults to English Wikipedia.
contextstring–Optional use-context slug for scoped analysis
depthstring–History depth: brief, detailed, or forensic
fromnumber–Read forward from this revision ID
limitnumber–Revisions to read (default 50, or the whole range when both from and to are given)
pagestringyesMediaWiki page title to ground against
statementstringyesRaw text statement to track
tonumber–Read back from this revision ID

No output schema declared.

No examples provided.

review ~236

Observe changes to a list of pages since their last acknowledged review and return the saved review report as JSON. Saves revisions and the report under stateDir. Never acknowledges: a person inspects the report and acknowledges it with the CLI command the result gives, and an incomplete report cannot be acknowledged.

NameTypeReqDescription
apistring–MediaWiki API base URL. Defaults to English Wikipedia.
eventTypesarray–Show only these event types in view; the saved report stays unfiltered
fromnumber–Initial comparison baseline revision ID for a page with no acknowledged review
limitnumber–New revisions per page per call (default 200); call again to resume
pagesarray–Page titles to review
sampleboolean–Review the bundled fictional history offline instead of pages
sectionstring–Show only events in this section in view
stateDirstringyesAbsolute path of the review state directory. All state and saved reports are written here; use the same directory the person acknowledges with.
textstring–Show only events whose text contains this in view

No output schema declared.

No examples provided.

snapshot ~148

Return the revision of a MediaWiki page that was live at a date: the newest revision at or before it, with its revision ID, timestamp, section headings, and text.

NameTypeReqDescription
apistring–MediaWiki API base URL. Defaults to English Wikipedia.
atstring–Target date or timestamp, ISO 8601 (e.g. '2024-01-15'). Defaults to the current time.
contentstring–Page text to include: plain (markup stripped, default), wikitext, or none
pagestringyesPage title
revisionLimitnumber–Max revisions to fetch at or before the date (default 500)

No output schema declared.

No examples provided.

Install

How do I install the Refract MCP server?

Refract runs locally as an npm package, launched with npx -y @refract-org/cli 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 · @refract-org/cli

# add to Claude Code
claude mcp add zz-plant-refract -- npx -y @refract-org/cli mcp
Common questions

What is the Refract MCP server?

Refract is an MCP server listed in the public MCP registry as io.github.zz-plant/refract. git log for Wikipedia: typed events for changed sentences, citations, and structure on any page. This page covers its npm package (@refract-org/cli).

Is the Refract MCP server safe to use?

Refract scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 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 Refract MCP server expose?

Refract exposes 8 tools: analyze, claim, export, cron, classify, and 3 more. Their descriptions and schemas cost roughly 1,126 tokens of context every time the server is loaded.

Is the Refract MCP server still maintained?

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

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

What did VerifyMCP test on the Refract MCP server?

VerifyMCP ran 16 checks on Refract, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.