ODEI MCP Server
OfficialRelated Servers
Alternatives to ODEI MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceEnables agentic retrieval over governed enterprise documents via a knowledge graph, with cross-silo orchestration, conflict detection, and audit trails. Exposes MCP tools like query_knowledge_graph, list_detected_conflicts, and get_audit_trail for use by other agents.-
- AlicenseAqualityAmaintenanceProvides advisory AI-governance checks for MCP hosts and coding agents, enabling policy verdicts, PII masking, and audit traces before executing tool calls.345 npmMIT

telos-mcpofficial
AlicenseAqualityBmaintenanceExposes TELOS governance primitives—action scoring, receipt verification, Purpose Anchor inspection, audit-chain queries, and CCRS counterfactual replay—as MCP tools, resources, and prompts for any MCP-compatible client.519 PyPIApache 2.0- AlicenseAqualityBmaintenanceEnables MCP-compatible agents to query security checklists, protocols, and framework mappings to safely build and operate AI agents, with tools for checklist runs, protocol lookup, mapping lookup, and threat search.9CC BY-4.0

evav-gatewayofficial
AlicenseNot gradedqualityBmaintenanceGoverned MCP gateway that lets AI agents call tools with policy enforcement, prompt-injection screening, a kill-switch, and tamper-evident signed audit logs.Apache 2.0- FlicenseNot gradedqualityCmaintenanceProvides trust infrastructure for AI agents by enabling reputation lookup, website trust scanning, and identity verification via MCP tools.1-
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.