I, Pencil verification
NPM · @IPOPCIL/MCP
Check Proof of Process chains: record, file match, timestamps, registry. Never one verdict.
Available components
Last scanned (2 hours ago)
Scores higher than 36% of npm servers
Category Crypto and Web3
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 Security97
- 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
- 1 of 1 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 3 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability59
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 875 tokens (~291/item across 3 items; 3 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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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.
- 20 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 19 Oct 26 47
First indexed and scored.
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 23 Oct 2026 · Analysed npm/@ipopcil/mcp@1.0.1
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 1 package
| Packages resolved | 1 |
|---|---|
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
check_registration Check a chain head on the registry ~197
Look up whether a chain head (64 hex chars, the `chain` of a proof's last checkpoint) was published to the I, Pencil registry on Base. With a pointer (the transaction hash a proof carries) this is one exact check at any age. Without one it searches recent blocks only, and a miss means 'not found in the blocks searched', never 'not registered'. A registration records publication by an address, not ownership or authorship.
| Name | Type | Req | Description |
|---|---|---|---|
| chainHead | string | yes | 64 hex characters, optionally 0x-prefixed. |
| maxRequests | integer | – | Search budget when there is no pointer. Default 24 (about 6 hours of history). |
| network | string | – | Base network. Defaults to the proof's own registry.chain, else whichever network has a registry contract (currently Base Sepolia, a test network). |
| txHash | string | – | Optional. The registration transaction the proof points to. |
No output schema declared.
No examples provided.
find_registrations_by_phash Find registrations by image fingerprint ~186
Reverse lookup: given only an image's 64-bit perceptual hash (16 hex chars), find registry entries whose final fingerprint is EXACTLY that value. Searches recent blocks only (no index exists yet), so a miss is not evidence of absence, and a resized or re-compressed copy may have a slightly different hash and not match. Returns every match: 64-bit hashes can collide, so several works may share one. A match locates a published chain head; obtain and verify that proof before drawing any conclusion.
| Name | Type | Req | Description |
|---|---|---|---|
| maxRequests | integer | – | Search budget. Default 24 (about 6 hours of history). |
| network | string | – | Base network. Defaults to the proof's own registry.chain, else whichever network has a registry contract (currently Base Sepolia, a test network). |
| phash | string | yes | 16 hex characters. |
No output schema declared.
No examples provided.
verify_proof Verify an I, Pencil proof ~320
Verify an I, Pencil (ipencil-chain) process proof and, optionally, check a file against it. Returns the ipencil-verification/1 result plus `statements`: one pre-scoped sentence per question. There is deliberately NO single valid/invalid verdict — the result answers four separate questions (record unaltered, file matches, time established, authorship) with different strengths of evidence. When reporting to a person, quote the statements rather than summarising them as 'verified'. Offline by default; set checkRegistry to also confirm the proof's registration on Base.
| Name | Type | Req | Description |
|---|---|---|---|
| checkRegistry | boolean | – | Query Base to confirm the proof's registration. Sends the chain head to a public Base RPC node. |
| filePath | string | – | Optional. Path to the file the proof is said to describe. Hashed locally (streamed, any size) and compared byte-for-byte against every checkpoint. |
| filePhash | string | – | Optional. 16-hex-character perceptual hash (64-bit dHash, as register.html computes it) of that file, enabling a visual-similarity comparison when the bytes differ. This server does not decode images. |
| network | string | – | Base network. Defaults to the proof's own registry.chain, else whichever network has a registry contract (currently Base Sepolia, a test network). |
| proof | object|string | – | The proof JSON, as an object or a JSON string. |
| proofPath | string | – | Path to a local proof .json file. Use instead of `proof`. |
No output schema declared.
No examples provided.
How do I install the I, Pencil verification MCP server?
I, Pencil verification runs locally as an npm package, launched with npx -y @ipopcil/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 · @ipopcil/mcp
claude mcp add xyz-sotapop-verify -- npx -y @ipopcil/mcp
What is the I, Pencil verification MCP server?
I, Pencil verification is an MCP server listed in the public MCP registry as xyz.sotapop/verify. Check Proof of Process chains: record, file match, timestamps, registry. Never one verdict. This page covers its npm package (@ipopcil/mcp).
Is the I, Pencil verification MCP server safe to use?
I, Pencil verification scores 62 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 23 October 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 I, Pencil verification MCP server expose?
I, Pencil verification exposes 3 tools: verify_proof, check_registration, find_registrations_by_phash. Their descriptions and schemas cost roughly 703 tokens of context every time the server is loaded.
Is the I, Pencil verification MCP server still maintained?
I, Pencil verification is still listed as active in the MCP registry. We last reached this channel on 23 October 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 I, Pencil verification MCP server under?
I, Pencil verification declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.