Agntor MCP vs Aegis

A side-by-side look at the Agntor MCP and Aegis MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Agntor MCP logoAgntor MCPSecurity · Local subprocess (stdio)MCP audit server for agent discovery and certification. Provides trust and payment rail for AI agents including identity verification, escrow, settlement, and reputation management.56GoodAuth: api key requiredAegis logoAegisSecurity · Local subprocess (stdio)Credential isolation proxy for AI agents. Injects secrets at the network boundary with domain restrictions, agent authentication, and audit logging. No SDK required — works as a transparent HTTP proxy or MCP server.53GoodAuth: not declared

Verdict: choose Agntor MCP for security work as a local process; choose Aegis for security as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Agntor MCP logoChoose 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.
Explore Agntor MCP

Aegis logoChoose Aegis when

  • You need dedicated capabilities in the Security domain.
  • You prefer a local stdio subprocess transport.
Explore Aegis

Feature & specification comparison

Rows where the two servers differ are marked.

SpecAgntor MCP logoAgntor MCPAegis logoAegis
CategorySecuritySecurity
Quality signal56/100 · Good53/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthAPI key requiredNot declared
PricingBYOK (pay the provider)Not declared
Required env varsAGNTOR_API_KEYAGNTOR_MCP_AUTH_KEYAGNTOR_SECRET_KEYAGNTOR_API_URLPORTMCP_TRANSPORTNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars114
Directory activity 4 views 0 installs 0 upvotes 3 views 0 installs 0 upvotes
Tools14Not listed

Tools & capabilities

Agntor MCP tools 14

  • get_agent_cardRetrieve the verifiable AgentCard (Passport) for an agent
  • get_agent_registrationGet EIP-8004 compatible registration file for agent discovery
  • check_agent_pulseGet real-time health and behavioral metrics
  • is_agent_certifiedQuick boolean check if an agent has valid certification
  • get_trust_scoreCalculate comprehensive trust score with behavioral factors
  • register_agentRegister a new AI agent in the Agntor trust network
  • verify_agent_identityTrigger verification (red-team probes) via the SDK
  • guard_inputScan incoming prompts for prompt injection and unsafe instructions
  • redact_outputRedact PII, secrets, and sensitive content from outputs
  • guard_toolAuthorize or block tool execution with allow/deny policies
  • create_escrowCreate a new escrow task for agent-to-agent payment
  • issue_audit_ticketGenerate signed JWT ticket for x402 transactions
  • +2 more on the listing page

Aegis tools

No tool names declared yet. Check the project README from the listing page.

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 (Claude Desktop / Cursor)
{
  "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"
      }
    }
  }
}

Aegis

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "getaegis-aegis": {
      "command": "npx",
      "args": [
        "-y",
        "@getaegis/cli"
      ]
    }
  }
}

Frequently asked questions

Agntor MCP is categorized under Security and uses a local stdio subprocess. Aegis belongs to Security and uses a local stdio subprocess. Pick Agntor MCP for security work and Aegis 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. Aegis has no declared pricing — check the project's own site. 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 getaegis-aegis 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. Aegis has 53/100 (Good) with 3 views, 0 installs and 14 GitHub stars.