PubLedge MCP server
Open recordkeeping protocol for JIAs, RMAs, no-action letters, and analogous instruments.
0 stars62 downloads/wk
Reviews
Write oneNobody has reviewed PubLedge yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
PubLedge tools (7)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
fetch_by_urlLook up a bundled … 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_…, including source and editorial fields where recorded. Does not fetch the URL over the network.
get_mappingsAll mapping entries connecting … to … via ….
get_matrixCoverage matrix showing which … are addressed by which ….
get_recently_changedReturn … sorted by last_verified or last changelog entry, most recent first.
get_upcomingReturn … with upcoming milestones (enacted, effective, expires dates in the future). Sorted by date ascending.
searchFull-text search across all entities in the knowledge base. Searches titles, IDs, and body content.
search_obligationsSearch only within … (… titles, IDs, body text). Same query semantics as search but scoped.
Public scan report
scanner v0.1.10 · 2026-10-03 · same rubric, same numbers if you re-run it
- Code scan5 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 0 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How PubLedge compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 92/100
- higher than 93% of 48,243 servers
- Tools
- 7
- the typical server has 7
- Tools that change things
- 0%
- typical: 0%. Fewer write tools means less an agent can break
- Downloads a week
- 62
- more than 49% of 12,306 servers with a package
What its tools let an agent do: 7 read
Install PubLedge in Claude Code, Cursor or VS Code
Runs npx -y publedge on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add publedge -- npx -y publedge
What the publisher says
From the PubLedge repository's README, as published. We do not edit it. Read it on GitHub
PubLedge
Open recordkeeping protocol for fact-specific written interpretations between two parties — Joint Interpretation Agreements (JIAs), Regulatory Mitigation Agreements (RMAs), no-action letters, private letter rulings, advisory opinions, and analogous civic instruments (HOA decision logs, co-op governance records, flying-club asset agreements, and the like).
Plain markdown with structured frontmatter. SHA-256 manifest checks provide source-to-manifest consistency. Bound to the Semantic Arts gist upper ontology so records from different authorities can be queried together.
Public and maintained. Package v0.2.5; protocol specification v0.2.0. The MCP server supports the MCP 2026-07-28 stateless core plus the legacy 2024-11-05 handshake. Current npm, MCP Registry, GitHub tag, and GitHub Release observations are recorded in the publication state. Standalone product expansion is parked pending a concrete legal-graph or adopter demand signal.
Who this is for
Regulators, regulated parties, and civic bodies that issue or rely on fact-specific written interpretations and need them recorded in a portable, queryable form.
What problem it solves
Fact-specific interpretations (no-action letters, private rulings, JIAs, HOA decisions) live in scattered, unstructured records that can't be compared across authorities. PubLedge is an open protocol that records them as manifest-checked markdown bound to a shared ontology.
Canonical URL
https://publedge.org/
Part of the PAICE legal graph
PubLedge is one component of the PAICE legal graph (with EveryAILaw, AI Incident Law, and Obligation First). It is intentionally open: code under Apache 2.0, protocol and content under CC BY 4.0, commercial use permitted with attribution. The open siblings are funded by EveryAILaw Pro, the graph's single restricted layer; openness here is a deliberate PBC-charter choice. The canonical model is in the PAICE Foundation INTENT.
What this repo is
Three things in one place:
- The protocol — the PROTOCOL.md specification and the PRIOR-ART.md survey that motivates it.
- Utah-shaped reference content — 5 JIA/RMA templates anchored to Utah's AI Policy Act (Utah Code §13-72a) and GenAI safe-harbor (§13-75-104), plus 18 demonstration instruments under data/examples/instruments/ spanning 8 authorities (Utah OAIP, Utah Legislature, Colorado Legislature, SEC, CFPB, IRS Chief Counsel, IRS TEGE, CFTC) and 7 instrument types (JIA, RMA, no-action letter, advisory opinion, private letter ruling, interpretive letter, statute). 35 first-class obligation records under data/examples/obligations/ are mapped to the instruments via data/examples/mapping/index.yml; legal lifecycle is tracked separately from editorial maturity.
- The published site — rendered HTML under docs/, served by GitHub Pages from main /docs. Regenerate with node scripts/build.js && node scripts/build-extras.js before committing; CI fails if docs/ drifts from sources.
Maintenance scope
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
PubLedge: common questions
- Is PubLedge MCP server safe?
- Yes, by our scan: it is graded A (92/100). Read the PubLedge safety report
- How do I install PubLedge?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does PubLedge need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is PubLedge maintained?
- The last commit was 33 days ago (2026-10-03). The latest release is v0.2.5.
- How does PubLedge compare with other MCP servers?
- safety score 92/100 (higher than 93% of 48,243 servers); tools 7 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.