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.

PubLedge

NPM · PUBLEDGE

Open recordkeeping protocol for JIAs, RMAs, no-action letters, and analogous instruments.

Available components

npm · publedge 86
0 this week 86 Trust /100

Last scanned (15 hours ago)

Scores higher than 90% of npm servers

Category Health and Science

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 & Transparency48
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (Apache-2.0).Pass
  • Actively maintained (last published 54 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability79
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 940 tokens (~72/item across 13 items; 13 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
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 13 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
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.

  • 2 Nov 26 +1
    • Stability: 0.97 → pass security
  • 1 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 26 Oct 26 +1
    • Stability: 0.97 → pass security
  • 25 Oct 26 −1
    • Stability: pass → 0.97 functional
    • Package version: 0.2.1 → 0.2.5 functional
  • 19 Oct 26 +1
    • Stability: 0.97 → pass security
  • 17 Oct 26 +1

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

  • 15 Oct 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.

  • 13 Oct 26 −3
    • Stability: pass → 0.80 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 6 Nov 2026 · Analysed npm/publedge@0.2.5

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 · 13 exposed · ~694 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
fetch_by_url ~103

Look up a bundled legal instrument by its canonical URL (e.g. https://publedge.org/us/utah/oaip/rma/2025-001/ or /us/utah/oaip/rma/2025-001/). Returns the same complete record as get_legal-instrument, including source and editorial fields where recorded. Does not fetch the URL over the network.

NameTypeReqDescription
urlstringyesCanonical hierarchical URL or path.

No output schema declared.

No examples provided.

get_authority ~41

Get a single authority by its ID. Returns all frontmatter fields and body content.

NameTypeReqDescription
idstringyesThe authority ID (filename without .md)

No output schema declared.

No examples provided.

get_legal-instrument ~71

Get a bundled legal instrument by its ID. Returns frontmatter, timeline, provisions, and body, including source, draft or demonstration labels, provenance, and reliance limits where recorded. This is not a live authority lookup.

NameTypeReqDescription
idstringyesThe legal instrument ID (filename without .md)

No output schema declared.

No examples provided.

get_mappings ~20

All mapping entries connecting legal instruments to obligations via terms.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_matrix ~20

Coverage matrix showing which obligations are addressed by which legal instruments.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_obligation ~41

Get a single obligation by its ID. Returns all frontmatter fields and body content.

NameTypeReqDescription
idstringyesThe obligation ID (filename without .md)

No output schema declared.

No examples provided.

get_recently_changed ~42

Return legal instruments sorted by last_verified or last changelog entry, most recent first.

NameTypeReqDescription
limitnumber–Max results to return (default 20).

No output schema declared.

No examples provided.

get_upcoming ~47

Return legal instruments with upcoming milestones (enacted, effective, expires dates in the future). Sorted by date ascending.

NameTypeReqDescription
limitnumber–Max results to return (default 20).

No output schema declared.

No examples provided.

list_authorities ~17

List all authorities in the knowledge base.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_legal-instruments ~175

List bundled legal instruments. Optional filters: jurisdiction, authority, type, status. Returns id, title, status, authority, type, jurisdiction, and canonical url for each match. Summaries omit source and editorial fields; use get_legal-instrument before interpreting legal effect.

NameTypeReqDescription
authoritystring–Filter by authority slug (e.g. "utah-oaip", "cfpb").
jurisdictionstring–Filter by jurisdiction slug (e.g. "us-ut", "us").
statusstring–Filter by status (e.g. "enforcing", "executed", "enacted").
typestring–Filter by instrument type (e.g. "statute", "rma", "jia", "ao", "nal", "plr", "il").

No output schema declared.

No examples provided.

list_obligations ~28

List all obligations in the knowledge base. Returns id, title, and group for each.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search ~42

Full-text search across all entities in the knowledge base. Searches titles, IDs, and body content.

NameTypeReqDescription
querystringyesSearch query (case-insensitive substring match)

No output schema declared.

No examples provided.

search_obligations ~47

Search only within obligations (obligation titles, IDs, body text). Same query semantics as search but scoped.

NameTypeReqDescription
querystringyesSearch query (case-insensitive substring match)

No output schema declared.

No examples provided.

Install

How do I install the PubLedge MCP server?

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

npm · publedge

# add to Claude Code
claude mcp add snapsynapse-publedge -- npx -y publedge
Common questions

What is the PubLedge MCP server?

PubLedge is an MCP server listed in the public MCP registry as io.github.snapsynapse/publedge. Open recordkeeping protocol for JIAs, RMAs, no-action letters, and analogous instruments. This page covers its npm package (publedge).

Is the PubLedge MCP server safe to use?

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

PubLedge exposes 13 tools: list_obligations, get_obligation, list_legal-instruments, get_legal-instrument, list_authorities, and 8 more. Their descriptions and schemas cost roughly 694 tokens of context every time the server is loaded.

Is the PubLedge MCP server still maintained?

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

PubLedge declares the Apache-2.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 PubLedge MCP server?

VerifyMCP ran 16 checks on PubLedge, 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.