PTERI Intelligence and MCP
A planned tool-namespace model for Model Context Protocol clients — conceptual, not yet a running integration.
MCP (Model Context Protocol) is an emerging standard for connecting AI assistants to external tools. PTERI Intelligence's published direction is to expose its capabilities through MCP using five tool namespaces:
wallet.*— address discovery, balance queries, UTXO inspectiontx.*— transaction construction, signing, broadcastingmweb.*— confidential/privacy-preserving transfersmessage.*— message signing and verificationobserve.*— status and confirmation tracking
The stated design goals: strict input schemas, tools that require explicit authority to invoke, deterministic output that can be logged and audited, and no path for a tool call to escalate permissions, touch a private key, or act outside its declared scope.
What's not available yet
As of this writing there's no published MCP server URL, no installable package, no client configuration file, and no tool-call examples or schema definitions — this is a named model for future tooling, not a connectable integration today. If MCP support is central to your evaluation of PTERI, please open a ticket (Technical / API category) so we can point you to the current state.