Avp Sdk vs Aegis

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

Avp Sdk logoAvp SdkSecurity · Local subprocess (stdio)Trust, identity (W3C DID), and EigenTrust reputation for AI agents. Attestations, disputes, sybil detection, IPFS audit anchoring.52GoodAuth: 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 Avp Sdk 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?

Avp Sdk logoChoose Avp Sdk when

  • You need dedicated capabilities in the Security domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: API key required.
Explore Avp Sdk

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.

SpecAvp Sdk logoAvp SdkAegis logoAegis
CategorySecuritySecurity
Quality signal52/100 · Good53/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthAPI key requiredNot declared
PricingFreeNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars1514
Directory activity 3 views 0 installs 0 upvotes 2 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

Avp Sdk tools

No tool names declared yet. Check the project README from 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.

Avp Sdk

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "creatorrmode-lead-avp-sdk": {
      "command": "uvx",
      "args": [
        "agentveil-mcp-proxy"
      ]
    }
  }
}

Aegis

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

Frequently asked questions

Avp Sdk is categorized under Security and uses a local stdio subprocess. Aegis belongs to Security and uses a local stdio subprocess. Pick Avp Sdk 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.

Avp Sdk is listed as free. 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 creatorrmode-lead-avp-sdk and getaegis-aegis as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Avp Sdk has a quality signal of 52/100 (Good) with 3 views, 0 installs and 15 GitHub stars. Aegis has 53/100 (Good) with 2 views, 0 installs and 14 GitHub stars.