About Mcp Poi
Mcp Poi processes files and prepares Proof of Invention blockchain transaction requests. It is for users preparing on-chain proof data; transaction signing and submission are handled by other tools.
Key features
- 01Process file content supplied by the client
- 02Prepare a Proof of Invention transaction request
- 03Return destination, data, and value fields
- 04Load the API token from an environment variable
Use cases
- 01Prepare POI transaction data from an idea file
- 02Pass the resulting request to a wallet tool for signing
- 03Prepare file data for blockchain submission
MCP support
The MCP server provides the create_proof_of_invention_request tool, which accepts a file path and returns transaction request data. File content is supplied by the MCP client.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMEMCP POI Server
A Model Context Protocol server for processing files and preparing blockchain transactions. This server can be installed in Claude Desktop and provides a tool to process files and prepare them for blockchain transactions.
https://github.com/user-attachments/assets/6b2fbd68-4eca-4130-9594-d6720508e9c8
Setup
- Clone this repository
- Install dependencies:
npm install - Build the server:
npm run build
Environment Variables
API_TOKEN: Your API bearer token for authentication against the PoI API. You can request a new token on Molecule's Discord Server: https://discord.gg/k4ER7vZcj8
Usage
The server provides a tool called create_proof_of_invention_request that accepts a file path returns prepared transaction data suitable for blockchain execution. This can be reused by your favorite tool that can sign and submit transactions. The binary content should be provided by the MCP client (e.g., Claude Desktop or Cursor).
https://docs.molecule.to/documentation/proof-of-invention-poi/api-access-beta
Adding to Claude Desktop
"poi": {
"command": "npx",
"args": ["mcp-poi"],
"env": {
"API_TOKEN": "the api token"
}
}
Plays nicely with other MCP servers
- https://pypi.org/project/mcp-server-fetch/
- https://www.npmjs.com/package/@mcp-dockmaster/mcp-cryptowallet-evm
Our complete Claude desktop config looks:
{
"mcpServers": {
"mcp-cryptowallet-evm": {
"command": "npx",
"args": ["@mcp-dockmaster/mcp-cryptowallet-evm"],
"env": {
"PRIVATE_KEY": ""
}
},
"filesystem": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-filesystem",
"/Users/stadolf/Downloads",
"/Users/stadolf/Documents"
]
},
"poi": {
"command": "npx",
"args": ["-y", "mcp-poi"],
"env": {
"API_TOKEN": ""
}
}
}
}
Prompts
| Create a poi hash from the "idea.md" file in my Documents folder ... | send and Eth transation with the poi hash to the poi's to address on the base blockchain
Tool Schema
Input:
{
filepath: string; // A path of a binary
}
Output:
{
transaction_request: {
to: string, // a PoI anchoring address (usually starts with 0x1dea)
data: string, // the merkle root hash that represents the PoI
value: string, // 0
}
}
Running the Server
npm start
Development
For development with automatic rebuilding:
npm run dev
Error Handling
The server includes robust error handling for:
- Missing environment variables
- Invalid file content
- API communication errors
- Invalid response formats
Security
- API tokens are loaded from environment variables
- File contents are properly encoded before transmission
- Error messages are sanitized to prevent information leakage
- No filesystem access required - all content is provided by the MCP client
Comments
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.