emilia-mcp-server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ep_trust_profileA | Get an entity's full trust profile. This is the CANONICAL way to check trust in EP. Returns behavioral rates (completion, retry, abandon, dispute), signal breakdowns, provenance composition, consistency, anomaly alerts, current confidence, historical establishment, and dispute summary. Use this before transacting with any counterparty or installing any software. |
| ep_trust_evaluateA | Evaluate an entity against a trust policy. Returns a Trust Decision (allow/review/deny) with specific failure reasons. Built-in policies: "strict" (high-value), "standard" (normal), "permissive" (low-risk), "discovery" (allow unevaluated). Accepts optional context for context-aware evaluation. Use this to make routing and payment decisions. |
| ep_submit_receiptA | Submit a transaction receipt to the EP ledger. Requires an API key. Receipts are append-only, cryptographically hashed, and chain-linked. transaction_ref is REQUIRED. agent_behavior is the strongest signal. |
| ep_search_entitiesB | Search for entities by name, capability, or category. |
| ep_verify_receiptA | Verify a receipt against the on-chain Merkle root. |
| ep_register_entityC | Register a new entity. Public — returns the first API key. |
| ep_leaderboardB | Get top entities ranked by trust confidence. |
| ep_dispute_fileA | File a dispute against a receipt. Any affected party can challenge. Reasons: fraudulent_receipt, inaccurate_signals, identity_dispute, context_mismatch, duplicate_transaction, coerced_receipt, other. The receipt submitter has 7 days to respond. |
| ep_dispute_statusA | Check the status of a dispute. Public — transparency is a protocol value. |
| ep_report_trust_issueA | Report a trust issue as a human. No authentication required. For when someone is wrongly downgraded, harmed by a trusted entity, or sees fraud. EP must never make trust more powerful than appeal. |
| ep_appeal_disputeA | Appeal a dispute resolution. Only dispute participants can appeal. Requires the dispute to be in upheld, reversed, or dismissed state. "Trust must never be more powerful than appeal." |
| ep_install_preflightA | EP-SX: Should I install this plugin/app/package/extension? Evaluates a software entity against a software-specific trust policy with context. Returns allow/review/deny with specific reasons covering publisher, permissions, provenance, and trust history. |
| ep_principal_lookupA | Look up a principal — the enduring actor behind entities. Returns bindings, controlled entities, and continuity history. |
| ep_lineageA | View entity lineage — predecessors, successors, continuity decisions, and whitewashing flags. Use to check if an entity has suspicious continuity gaps. |
| ep_list_policiesA | List all available trust policies with their requirements and families. Use to discover which policy to evaluate against. |
| ep_create_delegationB | Create a delegation record: a human or principal authorizes an agent to act on their behalf. The delegation is recorded in the EP ledger with scope, expiry, and optional constraints. Every delegated action can reference this delegation to prove authorization. |
| ep_verify_delegationA | Verify that an agent currently holds a valid delegation from a principal for a specific action. Use this before accepting a task from an agent claiming to act on behalf of a human. Returns: valid/expired/not_found with scope details. |
| ep_trust_gateA | Trust gate: check if an entity meets the required trust threshold BEFORE executing a high-stakes action. This is the canonical pre-action check. Always call this before: payments, sending messages on behalf of users, installing software, or any irreversible action. Returns allow/review/deny with reason. |
| ep_batch_submitA | Submit multiple receipts atomically. All receipts share the same submitter (your API key). Useful for bulk reconciliation or recording a session of agent-entity interactions. Returns per-receipt success/failure. Max 50 receipts per batch. |
| ep_configure_auto_receiptA | Enable or disable automatic receipt generation for this session. When enabled, every EP tool call generates a behavioral receipt automatically. Privacy-preserving: sensitive fields (passwords, tokens, API keys) are redacted before storage. Receipts are marked unilateral — they cannot be bilateral without counterparty confirmation. Auto-receipt is opt-in and disabled by default. |
| ep_domain_scoreA | Get an entity's trust score broken down by behavioral domain. Trust is not a scalar — an agent excellent at financial transactions may be unreliable at creative tasks. Domains: financial, code_execution, communication, delegation, infrastructure, content_creation, data_access. Returns per-domain confidence, evidence count, and behavioral rates. |
| ep_generate_zk_proofA | Generate a privacy-preserving commitment proof. Proves a trust claim (e.g., score > 0.85 in the financial domain, or > 50 verified receipts) WITHOUT revealing receipt contents, counterparty identities, or transaction details. Uses HMAC-SHA256 commitments + Merkle trees. Returns a proof_id you can share publicly — verifiers call ep_verify_zk_proof with only the proof_id and learn nothing about your transaction history. Essential for privacy-sensitive contexts: healthcare (HIPAA), legal (privilege), finance (NDA/MNPI), and any situation where sharing transaction history is not possible. Requires your EP API key (you can only prove claims about your own entity). |
| ep_verify_zk_proofA | Verify a privacy-preserving commitment proof by proof_id. Returns whether the claim is currently valid — without revealing anything about the entity's transaction history, counterparties, or receipt contents. The proof holder shares only the proof_id. You verify without learning who they transacted with. Use this to accept trust claims from entities in privacy-sensitive industries (healthcare, legal, finance) who cannot share raw transaction history. |
| ep_delegation_judgmentA | Get a principal's delegation authority — how well they choose and authorize agents. High judgment principals consistently authorize well-behaved agents. Low judgment principals frequently authorize agents that fail, dispute, or abandon tasks. This signal is deliberately weak (0.15 weight per outcome): a single bad delegation should not define a principal, but a pattern of them should be legible. Returns: judgment_score (0–1), agents_authorized, good_outcome_rate, and signal counts. |
| ep_issue_commitA | Issue a signed EP Commit before a high-stakes action. Returns a commit_id, decision (allow/deny/review), expiry, scope, and appeal path. The commit binds the agent to a specific action type, entity, and policy before execution. |
| ep_verify_commitB | Verify a commit's signature, status, and validity. Returns valid/invalid, current status, decision, and expiry. |
| ep_get_commit_statusA | Get the current state of a commit (active, revoked, expired, fulfilled). |
| ep_revoke_commitA | Revoke an active commit before it is fulfilled or expires. |
| ep_bind_receipt_to_commitA | Bind a post-action receipt to a commit, completing the commit-execute-receipt cycle. Links the behavioral outcome back to the signed authorization token. |
| ep_initiate_handshakeA | Initiate an EP Handshake — a structured identity exchange between parties. The handshake coordinates mutual presentation of identity proofs before a trust decision. Requires at least 2 parties and a governing trust policy. |
| ep_add_presentationB | Add an identity presentation (proof) to an active handshake. Each party presents their identity claims for evaluation against the handshake policy. Supports full, selective, or zero-knowledge disclosure modes. |
| ep_verify_handshakeB | Evaluate all presentations in a handshake against the governing policy. Returns: accepted (all requirements met), rejected (policy violations), or partial (awaiting presentations). Includes reason_codes explaining the outcome. |
| ep_get_handshakeA | Get the full state of a handshake including parties, presentations, binding, and result. Use this to check handshake progress or review completed exchanges. |
| ep_revoke_handshakeA | Revoke an active handshake. Only parties to the handshake may revoke it. Revocation is terminal — the handshake cannot be reopened. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| trust_decision | Get a structured prompt for making a trust-based routing or payment decision about an entity. |
| receipt_quality_check | Get a prompt for evaluating the quality and accuracy of a receipt before submission. |
| install_decision | Get a structured prompt for deciding whether to install a software package or plugin. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Entity Trust Profile | Full trust profile for any entity by ID or slug. Equivalent to ep_trust_profile tool but as a resource. |
| Entity Trust Score | Current trust confidence and score breakdown for an entity. |
| Receipt | Full receipt data including hash, provenance, and verification status. |
| Delegation Record | Delegation details: principal, agent, scope, expiry, and status. |
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/emiliaprotocol/emilia-protocol'
If you have feedback or need assistance with the MCP directory API, please join our Discord server