1 findingStatic scanned
Lets your agent look up Japanese laws article by article, with the law number and an e-Gov link.
No reviews yetMIT
Pdf Verify MCP
shuji-bonji · MCP server
Checks the authenticity and conformance of PDF documents for your AI assistant. It verifies digital signatures cryptographically, evaluates the trust chain against trust anchors you supply, checks revocation and timestamps, detects changes made after signing, including breaches of the changes a certification permits, and identifies the PAdES baseline level. It also validates PDF/A and PDF/UA conformance, using veraPDF when it is installed and a built-in rule subset otherwise, and can reduce the findings to one of four outcomes with a fixed rule table.
Written by ooruby from the README of @shuji-bonji/pdf-verify-mcp 0.29.1.
Not claimed by its maker. Is this yours? Prove it and answer the findings
Why it's useful
Your agent can test a PDF's signatures and later changes directly, instead of judging the file from its extracted text alone.
What you could do with it
- Ask whether the signatures in a contract PDF verify and whether it was altered after it was signed.
- Find out which PAdES level a signature reaches and whether it carries long-term validation data.
- Validate a document against PDF/A or PDF/UA and see which rules it fails.
Written from its documentation: what it says it can do, not what our checks found.
Maintenance
Not measuredNo release date is on record for this package yet. The nightly publisher check records one as it reaches each npm package, about once every ten nights.
Release activity only: it says nothing about quality or safety, and a finished small package can be fine without releases. How it is measured
- Command execution is bounded
- inventory
- eval (CHANGELOG.md:1165)
- An inventory of where the code starts another program, not a verdict on this row: whether each one runs a fixed program or whatever it is handed takes a reading by hand.
Published because it was found. A finding is information about where the limits are, not a verdict that the software is unsafe.
What this does not cover
- Everything. Treat it as you would software from anywhere else.
Receipt history: every signed receipt for every version of this listing, and what changed between them.
In its maker's words
MCP server for PDF authenticity verification - cryptographic signature verification, tamper detection, PAdES level detection
Compare with
Compare all 4How far this has been checked
Static scanned
- What it establishes
- Its published package, or for a hosted server its source repository at a recorded commit, was read file by file, without running it, by every check in our current scan.
- What it does not
- How it behaves when it runs, or anything the scan does not read yet: several rubric checks, the repository's history, and compiled code in folders named dist or build. For a hosted server, that the endpoint runs the code that was read. The ooruby Index sets out exactly what was read.
- Exactly what was read
- Version 0.29.1, the file with digest sha512-opxkbFhauMJupxoxVSyoW4ShJd3jWKlXg1SiXj1VBFlBn6aDwavuzs7eDnJA/al4POVZ2M+flKI6orfnKVmLOw==, as the registry publishes it. A published version cannot be replaced, so this names the same bytes for anyone who checks.
- Authentication
- Runs locally. No hosted endpoint is listed for this package. You run it on your own machine, so there is no endpoint of ours to authenticate against.
Adding it
Paste this into your client's MCP configuration.
{
"mcpServers": {
"pdf-verify-mcp": {
"command": "npx",
"args": [
"-y",
"@shuji-bonji/pdf-verify-mcp@0.29.1"
]
}
}
}Or run it directly.
npx -y @shuji-bonji/pdf-verify-mcp@0.29.1Pinned to 0.29.1, which is the version the findings above were found in. Drop the version to take whatever is newest, and the report on this page stops describing what you installed.
Where this came from
- Registry
- npm
- Package
- @shuji-bonji/pdf-verify-mcp
- Version read
- 0.29.1
- Resolved
- 2026-10-10
Built from source, attested
npm publishes a signed statement that this exact package was built from the repository below, at this commit. It is verifiable without taking our word for it.
- Repository
- github.com/shuji-bonji/pdf-verify-mcp
- Commit
- 43e5502c2303
- Built by
- github.com/actions/runner/github-hosted
- Registry publish attestation
- signed by npm · 2026-10-10
- Checked
- 2026-10-10
The badge, if this is your listing
It renders the current rung (static scanned) and links back here, where what that does and does not establish is one click away. It updates itself as the evidence deepens.
[](https://ooruby.com/market/shuji-bonji-pdf-verify-mcp)About this listing
- Kind
- MCP server
- Category
- Data & analytics
- Pricing
- Free
- Sandbox
- No
- Hosted
- No
- Updated
- 2026-10-10
More from shuji-bonji
See the storefrontSimilar MCP servers
All MCP serversClean scanStatic scanned
Lets your agent query, update and manage MongoDB databases and set up MongoDB Atlas clusters.
458.4k installs/moApache-2.0
1 findingStatic scanned
Lets your agent manage tables, fetch configuration and query data in your Supabase projects.
440.5k installs/moApache-2.0
2 findingsStatic scanned
Lets your AI assistant remember facts about you across chats in a local knowledge graph.
364.5k installs/moSEE LICENSE IN LICENSE
Verification records what our published tests found on a specific version at a specific date. It is not a warranty, and it does not certify that software is free of defects.