Ext Ops Panel
Open dashboard
Comparison

Plugged.in Proxy vs TWZRD Agent Intelligence

Plugged.in Proxy is an MCP server published by VeriTeknik. Marketplaces we read that list it: 1 (Docker MCP Catalog). TWZRD Agent Intelligence is an MCP server published by twzrd-sol. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-23. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplacePlugged.in ProxyTWZRD Agent Intelligence
Docker MCP Catalog Listed
Version: sha256:b7c32590b270
Forks (GitHub): 30
Pulls (Docker Hub): 36 011
Stars (Docker Hub): 3
Stars (GitHub): 136
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.5.13
Downloads/month (PyPI): 538
Downloads/week (PyPI): 93
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

Plugged.in Proxy vs TWZRD Agent Intelligence
FactPlugged.in ProxyTWZRD Agent Intelligence
Marketplaces that list it11
Stars (GitHub) (differs)136 (better)0 (worse)
Pulls (Docker Hub) (differs)36 011No figure on Docker Hub
Forks (GitHub) (differs)30 (better)0 (worse)
Last release (differs)Not published2026-10-20
Where it runs (differs)On your machine (mcp/pluggedin-mcp-proxy)Remote server or your machine
Transport (differs)stdiostdio, Streamable HTTP
Tools it declares (differs)6Not published
Environment variables it asks for (differs)2, secrets among them: 11, secrets among them: 0
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/veriteknik/pluggedin-mcp-proxygithub.com/twzrd-sol/twzrd-trust
Changes in the last 7 days (differs)01
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 4 days ago

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

Plugged.in Proxy

In its own words, on Docker MCP Catalog:

A unified MCP proxy that aggregates multiple MCP servers into one interface, enabling seamless tool discovery and management across all your AI interactions. Manage all your MCP servers from a single connection point with RAG capabilities and real-time notifications.

TWZRD Agent Intelligence

In its own words, on Official MCP Registry:

Pre-spend trust for AI agents that buy: check x402 services and product listings before paying.

How to run each

Plugged.in Proxy As a local MCP server: Docker image

Claude Code
claude mcp add --env "PLUGGEDIN_API_KEY=<YOUR_PLUGGEDIN_API_KEY>" --transport stdio pluggedin-mcp-proxy -- docker run -i --rm -e PLUGGEDIN_API_KEY mcp/pluggedin-mcp-proxy

Requires: PLUGGEDIN_API_KEY (secret)

TWZRD Agent Intelligence As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio twzrd-agent-intel -- uvx twzrd-agent-intel

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only TWZRD Agent Intelligence has a remote endpoint we check. How we check endpoints

Tools each declares

Only Plugged.in Proxy has

  • pluggedin_ask_knowledge_base
  • pluggedin_delete_notification
  • pluggedin_discover_tools
  • pluggedin_list_notifications
  • pluggedin_mark_notification_done
  • pluggedin_send_notification

Only TWZRD Agent Intelligence has

  • check_listing
  • compare_wallets
  • evaluate_x402_resource
  • get_claim
  • get_counterparties
  • get_evidence
  • get_facilitator_footprint
  • get_merchant_card
  • get_poec_score
  • get_provider_reputation
  • get_publication
  • get_readiness_card_tool
Show the remaining 16
  • get_shopping_check
  • get_solana_market_status
  • get_top_intel_agents
  • get_x402_directory
  • is_wash_fleet
  • low_level_preflight
  • score_wallet_for_intel
  • score_wallets_batch
  • submit_contribution_claims
  • twzrd_demo_gate
  • twzrd_watch_add
  • twzrd_watch_list
  • twzrd_watch_remove
  • verify_receipt
  • verify_root_inputs
  • verify_x402_settled_claim

Both have

None

Tool names as the marketplaces declare them and as Ext Ops observed them on the endpoints (TWZRD Agent Intelligence as of 2026-10-13). More tools is not better in itself: compare what each needs for the job.

Settings each asks for

Only Plugged.in Proxy asks for

  • PLUGGEDIN_API_BASE_URL
  • PLUGGEDIN_API_KEY (secret)

Only TWZRD Agent Intelligence asks for

  • TWZRD_SIGNAL_SOURCE

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: Plugged.in Proxy · What it can do: TWZRD Agent Intelligence · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built