mcpField
I

I, Pencil verification

Local
sotapop.xyzSecurity

About I, Pencil verification

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

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"xyz-sotapop-verify": {
"command": "npx",
"args": [
"-y",
"@ipopcil/mcp"
]
}
}
}
Run commandnpx -y @ipopcil/mcp

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npm@ipopcil/mcp1.1.0

Tools

3

Saved tool list · updated 5d ago

ParameterTypeRequiredDescription
proofobject|stringNoThe proof JSON, as an object or a JSON string.
networkenumNoBase network. Defaults to the proof's own registry.chain, else whichever network has a registry contract (currently Base Sepolia, a test network).sepolia | mainnet
filePathstringNoOptional. Path to the file the proof is said to describe. Hashed locally (streamed, any size) and compared byte-for-byte against every checkpoint.
filePhashstringNoOptional. 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.
proofPathstringNoPath to a local proof .json file. Use instead of `proof`.
checkRegistrybooleanNoQuery Base to confirm the proof's registration. Sends the chain head to a public Base RPC node.

Details

The maintainer has not added details yet. Check the README in the repository.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.