# I, Pencil verification (npm · @ipopcil/mcp)

Check Proof of Process chains: record, file match, timestamps, registry. Never one verdict.

- Trust score: 62/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-23

## Components

- npm · `@ipopcil/mcp`: 62/100 (this document), [markdown](https://verifymcp.io/servers/xyz-sotapop-verify/ipopcil-mcp.md), [page](https://verifymcp.io/servers/xyz-sotapop-verify/ipopcil-mcp)

## Channel facts

- Registry: `npm`
- Package: `@ipopcil/mcp`
- Version: `1.0.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-23.

- **Supply Chain Security**: 97/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 1 of 1 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 19/100
  - Repository check failed: no source repository is declared.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 3 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 59/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**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.

## Install

### 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.

### Claude

```bash
claude mcp add xyz-sotapop-verify -- npx -y @ipopcil/mcp
```

### Cursor

```json
{
  "mcpServers": {
    "xyz-sotapop-verify": {
      "command": "npx",
      "args": [
        "-y",
        "@ipopcil/mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "xyz-sotapop-verify": {
      "command": "npx",
      "args": [
        "-y",
        "@ipopcil/mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add xyz-sotapop-verify -- npx -y @ipopcil/mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "xyz-sotapop-verify": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@ipopcil/mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add xyz-sotapop-verify --command npx --arg -y --arg @ipopcil/mcp
```

### Hermes

```yaml
mcp_servers:
  xyz-sotapop-verify:
    command: "npx"
    args: ["-y", "@ipopcil/mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "xyz-sotapop-verify": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@ipopcil/mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add xyz-sotapop-verify -t stdio -c npx -a -y @ipopcil/mcp
```

### Other

```json
{
  "mcpServers": {
    "xyz-sotapop-verify": {
      "command": "npx",
      "args": [
        "-y",
        "@ipopcil/mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-20 (score 62, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-10-19 (score 47)

First indexed and scored.

## MCP tools (3)

### `verify_proof` (~320 tokens)

Verify an I, Pencil proof

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.

Input parameters:

- `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`.

### `check_registration` (~197 tokens)

Check a chain head on the registry

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.

Input parameters:

- `chainHead` (string, required): 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.

### `find_registrations_by_phash` (~186 tokens)

Find registrations by image fingerprint

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.

Input parameters:

- `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, required): 16 hex characters.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/xyz-sotapop-verify/ipopcil-mcp#diagnostics

## Score history

- 2026-10-23: 62
- 2026-10-22: 62
- 2026-10-21: 62
- 2026-10-20: 62
- 2026-10-19: 47

## Common questions

### 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.

## Links

- npm package: https://www.npmjs.com/package/@ipopcil/mcp
- Socket report: https://socket.dev/npm/package/@ipopcil/mcp
- Website: https://sotapop.xyz/
- Changelog RSS feed: https://verifymcp.io/servers/xyz-sotapop-verify/ipopcil-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/xyz-sotapop-verify/ipopcil-mcp.json
- HTML version of this page: https://verifymcp.io/servers/xyz-sotapop-verify/ipopcil-mcp
