ODEI MCP Server
Official# MCP for ODEI
Public Model Context Protocol interface notes for ODEI integrations.
ODEI is an operational decision engine for individuals: a local-first personal operating layer, semantic world model, and agent control surface designed around user agency.
## Public Boundary
This repository is intentionally minimal. It exists to publish the project surface, security contact, and integration direction without exposing production infrastructure or private runtime code.
Published here:
- High-level project context
- Public interface notes
- Security reporting instructions
- Non-operational examples or documentation
Not published here:
- Production credentials or environment files
- Deployment automation for live infrastructure
- Private worker, VPN, oracle, or operator code
- Internal keys, tokens, state, or telemetry
## Contact
Security reports: security@odei.ai
Product: https://odei.ai
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: guardrail validation, smart contract auditing, world model querying, and trust scoring. There is no overlap in functionality, and the descriptions clearly differentiate their use cases, making misselection unlikely.
All tool names follow a consistent 'odei_' prefix with descriptive snake_case suffixes (e.g., guardrail_check, smart_contract_audit). This pattern is uniform across all four tools, enhancing predictability and readability.
Four tools is a reasonable count for an MCP server focused on AI safety and blockchain security, but it feels slightly thin given the broad scope implied by the descriptions. Each tool earns its place, but additional tools might be expected for more comprehensive coverage in these domains.
The tools cover key areas like guardrails, smart contracts, and world model interactions, but there are notable gaps. For example, there are no tools for updating or managing the world model, executing actions post-guardrail approval, or handling non-EVM blockchains, which could limit agent workflows in this domain.