Agntor MCP vs Emilia Protocol
A side-by-side look at the Agntor MCP and Emilia Protocol MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Agntor MCP for security work as a local process; choose Emilia Protocol for security as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Agntor MCP when
- You need dedicated capabilities in the Security domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
AGNTOR_API_KEY, AGNTOR_MCP_AUTH_KEY, AGNTOR_SECRET_KEY, AGNTOR_API_URL, PORT, MCP_TRANSPORT. - You want tools like
get_agent_card, get_agent_registration, check_agent_pulse.
Choose Emilia Protocol when
- You need dedicated capabilities in the Security domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
ep_guard_action, ep_check_signoff, ep_verify_receipt.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Security | Security |
| Quality signal | 56/100 · Good | 71/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | No auth required |
| Pricing | BYOK (pay the provider) | Free |
| Required env vars | AGNTOR_API_KEYAGNTOR_MCP_AUTH_KEYAGNTOR_SECRET_KEYAGNTOR_API_URLPORTMCP_TRANSPORT | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 599 |
| Directory activity | 4 views 0 installs 0 upvotes | 6 views 0 installs 0 upvotes |
| Tools | 14 | 3 |
| Full listing | View Agntor MCP | View Emilia Protocol |
Tools & capabilities
Agntor MCP tools 14
get_agent_cardRetrieve the verifiable AgentCard (Passport) for an agentget_agent_registrationGet EIP-8004 compatible registration file for agent discoverycheck_agent_pulseGet real-time health and behavioral metricsis_agent_certifiedQuick boolean check if an agent has valid certificationget_trust_scoreCalculate comprehensive trust score with behavioral factorsregister_agentRegister a new AI agent in the Agntor trust networkverify_agent_identityTrigger verification (red-team probes) via the SDKguard_inputScan incoming prompts for prompt injection and unsafe instructionsredact_outputRedact PII, secrets, and sensitive content from outputsguard_toolAuthorize or block tool execution with allow/deny policiescreate_escrowCreate a new escrow task for agent-to-agent paymentissue_audit_ticketGenerate signed JWT ticket for x402 transactions- +2 more on the listing page
Emilia Protocol tools 3
ep_guard_actionRequest authorization before an irreversible action: payments, wire transfers, fund releases, deletions, record or account changes, or sending messages with real-world effect. Submits the exact action for policy evaluation and human authorization. This MCP tool does not itself sit at the executor choke point: even after approval, the executor MUST match the returned action_hash and atomically consume the receipt before effect. If BLOCKED, poll ep_check_signoff with the receipt_id.ep_check_signoffPoll a pending authorization after ep_guard_action returns BLOCKED. Pass the receipt_id. Returns PENDING, APPROVED_PENDING_CONSUME, CONSUMED, or DENIED. Approval alone is not permission to execute: the executor must match action_hash and atomically consume the receipt at its own choke point.ep_verify_receiptAsk the configured EMILIA service to verify a stored trust receipt and report its hash and anchor status. Read-only, but not an offline verifier: the result is the service response for the supplied receipt_id.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Agntor MCP
{
"mcpServers": {
"agntor-mcp": {
"command": "npx",
"args": [
"-y",
"@agntor/mcp"
],
"env": {
"AGNTOR_API_KEY": "YOUR_AGNTOR_API_KEY_HERE",
"AGNTOR_MCP_AUTH_KEY": "YOUR_AGNTOR_MCP_AUTH_KEY_HERE",
"AGNTOR_SECRET_KEY": "YOUR_AGNTOR_SECRET_KEY_HERE",
"AGNTOR_API_URL": "YOUR_AGNTOR_API_URL_HERE",
"PORT": "YOUR_PORT_HERE",
"MCP_TRANSPORT": "YOUR_MCP_TRANSPORT_HERE"
}
}
}
}
Emilia Protocol
{
"mcpServers": {
"emiliaprotocol-emilia-protocol": {
"command": "npx",
"args": [
"-y",
"@emilia-protocol/mcp-server"
]
}
}
}
Frequently asked questions
Agntor MCP is categorized under Security and uses a local stdio subprocess. Emilia Protocol belongs to Security and uses a local stdio subprocess. Pick Agntor MCP for security work and Emilia Protocol for security.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Agntor MCP is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. Emilia Protocol is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add agntor-mcp and emiliaprotocol-emilia-protocol as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Agntor MCP has a quality signal of 56/100 (Good) with 4 views, 0 installs and 1 GitHub stars. Emilia Protocol has 71/100 (Great) with 6 views, 0 installs and 599 GitHub stars.