Ext Ops Panel
Open dashboard
Comparison

Plugged.in Proxy vs USASpending.gov

Plugged.in Proxy is an MCP server published by VeriTeknik. Marketplaces we read that list it: 1 (Docker MCP Catalog). USASpending.gov is an MCP server published by 1102tools.com. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). As of our marketplace pass on 2026-11-13. 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 ProxyUSASpending.gov
Docker MCP Catalog Listed
Version: sha256:b7c32590b270
Forks (GitHub): 29
Pulls (Docker Hub): 36 725
Stars (Docker Hub): 3
Stars (GitHub): 139
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.29
Downloads/month (PyPI): 2 153
Downloads/week (PyPI): 344
Forks (GitHub): 10
Stars (GitHub): 32
Not marked · First seen
PyPI (MCP servers) Not listed Listed
Version: 1.0.29
Downloads/month (PyPI): 2 153
Downloads/week (PyPI): 344
Forks (GitHub): 10
Stars (GitHub): 32
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 USASpending.gov
FactPlugged.in ProxyUSASpending.gov
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)139 (better)32 (worse)
Pulls (Docker Hub) (differs)36 725No figure on Docker Hub
Forks (GitHub) (differs)29 (better)10 (worse)
Last release (differs)Not published2026-11-03
Where it runs (differs)On your machine (mcp/pluggedin-mcp-proxy)Remote server or your machine
Transport (differs)stdioStreamable HTTP, stdio
Tools it declares (differs)6Not published
Environment variables it asks for (differs)2, secrets among them: 1Not published
Licence (differs)Apache-2.0MIT
Repository (differs)github.com/veriteknik/pluggedin-mcp-proxygithub.com/1102tools-dev/federal-contracting-mcps
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 10 h 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.

USASpending.gov

In its own words, on Official MCP Registry:

USAspending.gov contracts, grants, loans, subawards, recipients, agencies, and federal accounts.

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)

USASpending.gov As a remote MCP server

Claude Code
claude mcp add --transport http usaspending-gov-mcp https://usaspending.1102tools.com/mcp

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

Only USASpending.gov 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 USASpending.gov has

  • autocomplete_awarding_agency
  • autocomplete_cfda
  • autocomplete_funding_agency
  • autocomplete_glossary
  • autocomplete_naics
  • autocomplete_psc
  • autocomplete_recipient
  • awards_last_updated
  • get_agency_awards
  • get_agency_budgetary_resources
  • get_agency_federal_accounts
  • get_agency_object_classes
Show the remaining 43
  • get_agency_obligations_by_award_category
  • get_agency_overview
  • get_agency_program_activities
  • get_agency_sub_agencies
  • get_award_count
  • get_award_detail
  • get_award_federal_account_count
  • get_award_funding
  • get_award_funding_rollup
  • get_award_subaward_count
  • get_award_transaction_count
  • get_award_types_reference
  • get_def_codes_reference
  • get_federal_account_detail
  • get_federal_account_fy_snapshot
  • get_federal_account_object_classes
  • get_federal_account_program_activities
  • get_glossary
  • get_idv_activity
  • get_idv_amounts
  • get_idv_children
  • get_idv_funding
  • get_idv_funding_rollup
  • get_naics_details
  • get_psc_filter_tree
  • get_recipient_children
  • get_recipient_profile
  • get_state_profile
  • get_submission_periods
  • get_transactions
  • list_federal_accounts
  • list_states
  • list_toptier_agencies
  • lookup_piid
  • new_awards_over_time
  • search_awards
  • search_recipients
  • search_subawards
  • spending_by_category
  • spending_by_geography
  • spending_by_subaward_grouped
  • spending_by_transaction
  • spending_over_time

Both have

None

Tool names as the marketplaces declare them and as Ext Ops observed them on the endpoints (USASpending.gov as of 2026-11-01). More tools is not better in itself: compare what each needs for the job.

Settings each asks for

The marketplaces of USASpending.gov publish no settings it asks for, so we do not compare settings.

What it can do: Plugged.in Proxy · What it can do: USASpending.gov · 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. Package data comes from the Python Package Index (pypi.org). 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