In-depth architectural comparison of the Avp Sdk and Agentforge Trust MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Avp Sdk
Security · Local stdio
Quality: 52/100 (Good) | Auth: API Key required
Agentforge Trust MCP
Security · Local stdio
Quality: 55/100 (Good) | Auth: API Key required
Verdict Summary: Choose Avp Sdk if you need specialized Security tools running via a local process. Choose Agentforge Trust MCP if your workspace requires Security integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Avp Sdk when:
You need dedicated capabilities in the Security domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Free / Open Source).
You have access to required keys: AGENTVEIL_API_KEY, AGENTVEIL_PROJECT_ID, AGENTVEIL_LOG_LEVEL.
Primary tools included: Mediates native and routed MCP actions with allow, approval, redirect, or hard-block decisions, Supports W3C Decentralized Identifiers (DIDs) for identity, EigenTrust reputation system integration.
Trust, identity (W3C DID), and EigenTrust reputation for AI agents. Attestations, disputes, sybil detection, IPFS audit anchoring.
Query the AgentForge Trust Score (0-100 across five dimensions: security, code health, behavioral audit, community trust, EU compliance) for any MCP server before connecting. Exposes checktrust, evaluatepolicy, listtrusted, and recommend tools. 3,600+ servers audited, free public API.
Category & Scope
Tools & Capabilities Breakdown
Avp Sdk Tools (6)
Mediates native and routed MCP actions with allow, approval, redirect, or hard-block decisions
Supports W3C Decentralized Identifiers (DIDs) for identity
EigenTrust reputation system integration
Attestation and dispute management
Sybil detection mechanisms
Local bounded evidence recording with request IDs and hashes
Agentforge Trust MCP Tools (8)
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Avp Sdk is categorized under Security and uses a local stdio subprocess. In contrast, Agentforge Trust MCP belongs to Security using local stdio subprocess. Select Avp Sdk when you need capabilities focused on security and Agentforge Trust MCP when you require tools for security.
Fetch the AgentForge Trust Score for an MCP server. Returns the overall score (0-100), per-dimension breakdown (code_health, security_scan, behavioral_audit, community_trust, eu_compliance), and badges. Use before connecting to any MCP server.
evaluate_policy
Check whether a server passes a trust policy. Returns allowed:true/false plus individual check results. Example policy: {min_overall: 70, required_badges: ['actively_maintained']}. Use this to gate agent decisions like 'should I use this server for financial data?'.
list_trusted
Search AgentForge catalog for servers matching a category and minimum trust threshold. Returns up to 25 results sorted by trust score.
recommend
Given a natural-language use case, recommend MCP servers filtered by trust. Example: 'I need to validate Czech VAT IDs and convert ISDOC invoices'. Uses AgentForge semantic search + trust filter.
discover
Browse the AgentForge catalog of MCP servers. Supports full-text search, semantic search, and category filtering. No authentication required. Use this when you need to find servers offering a specific capability (e.g. 'GitHub PR automation', 'EU VAT validation'). Returns server metadata, tool counts, pricing tier, and trust scores. Each result carries TWO trust fields: `audit_score` (0-100, dynamic from the AgentForge audit pipeline — AUTHORITATIVE for policy gating, may be null if not yet audited) and `trust_score` (0-10, legacy community rating — for display fallback only). Always prefer audit_score when present; treat null audit_score as 'audit pending'.
broadcast_search
Search ACROSS multiple MCP servers in a single call. Returns relevant tools per server, sorted by relevance. Replaces N sequential discover+capabilities calls. Requires AGENTFORGE_API_KEY (set in env or call register_agent first). Use this when an agent needs to fan out a query like 'find me anything that can parse DICOM medical images' across the catalog.
call_tool
Invoke any tool on any MCP server in the AgentForge catalog. AgentForge proxies the call, applies rate limits, billing (per-call or wallet credits), and returns the result. Requires AGENTFORGE_API_KEY. Use this to actually USE a server's capability after discovery, e.g. call_tool(server='github-pro', tool='create_pr', input={...}).
register_agent
Self-register this agent with AgentForge. Returns an af_agent_* API key that unlocks broadcast_search and call_tool. Run once at agent startup, store the key in env as AGENTFORGE_API_KEY. No auth required for registration. Idempotent on slug — running twice produces a uniqued slug.