io.github.CloudCorpRecords/fedvendor vs GovCon API
io.github.CloudCorpRecords/fedvendor is an MCP server published by CloudCorpRecords. Marketplaces we read that list it: 1 (Official MCP Registry). GovCon API is an MCP server published by govconapi. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-07. 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
| Marketplace |  io.github.CloudCorpRecords/fedvendor |  GovCon API |
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 0.3.1 Downloads/month (PyPI): 2 614 Downloads/week (PyPI): 32 Forks (GitHub): 1 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
| Fact | io.github.CloudCorpRecords/fedvendor | GovCon API |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) | 0 | 0 |
| Forks (GitHub) (differs) | 0 (worse) | 1 (better) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (@reneturcios/fedvendor) | Remote server (mcp.govconapi.com/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 2, secrets among them: 1 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/cloudcorprecords/fedvendor | github.com/govconapi/govconapi-mcp |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-11-03 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 3 h ago, requires authentication |
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
io.github.CloudCorpRecords/fedvendor
SAM.gov data by API key: entities, exclusions, opportunities, awards, hierarchy, subawards.
GovCon API
Six tools over US federal procurement: SAM.gov, FPDS awards, entities, subawards, exclusions.
How to run each
io.github.CloudCorpRecords/fedvendor As a local MCP server: npm package
claude mcp add --transport stdio fedvendor -- npx -y @reneturcios/fedvendor mcpGovCon API As a remote MCP server
claude mcp add --transport http govconapi https://mcp.govconapi.com/mcpRequires: GOVCONAPI_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only GovCon API has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of io.github.CloudCorpRecords/fedvendor publish no settings it asks for, so we do not compare settings.
What it can do: io.github.CloudCorpRecords/fedvendor · What it can do: GovCon API · Compare two other plugins
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.