bidrock vs Vivid MCP
bidrock is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑15.
bidrock is a plugin bundle for AI coding tools published by UAB Bidrock. No marketplace we read lists it any more. Vivid MCP is an MCP server published by vivid-money. Marketplaces we read that list it: 3 (Official MCP Registry, Claude Code: claude-plugins-community, Community GitHub marketplaces). As of our marketplace pass on 2026-10-18. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace | ||
|---|---|---|
| Community marketplace bidrock/agent-plugin | Removed on 2026-10-15 Version: 0.1.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.1.0 Forks (GitHub): 2 Stars (GitHub): 9 Not marked · First seen |
| Claude Code: claude-plugins-community | Not listed | Listed Version: 0.1.0 Forks (GitHub): 2 Stars (GitHub): 9 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 | bidrockno longer listed · | Vivid MCP |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 3 |
| Stars (GitHub) (differs) | 0 | 9 |
| Forks (GitHub) (differs) | 0 | 2 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (mcp.bidrock.io/mcp) | Remote server (api.prime.vivid.money/mcp) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle | 2 | 2 |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/bidrock/agent-plugin | github.com/vivid-money/vivid-mcp |
| Changes in the last 7 days (differs) | 4 | 2 |
| First seen (differs) | 2026-10-14 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Answered with HTTP 400 (5 days ago) |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of bidrock
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Helvabase — Governed response dossiers
Connect your AI assistant to governed tender and RFP dossiers: sources, versions, decisions.
-
Government contracting research and capture workflows in Claude: opportunity and pipeline briefs, bid/no-bid and competitor analysis, price-to-win and proposal prep, powered by…
-
Search AU/NZ government tenders and rank a shortlist against company capabilities.
-
free-blueprints io.github.agent-blueprint/free-blueprints
Free AI agent blueprints for procurement and onboarding. No signup, no API key.
-
Find, score and track public-sector bids, RFPs, grants and tenders from 100+ official sources.
-
AI-powered consulting tools for proposals, client management, and business development.
What each says it does
bidrock
Search procurement and collaborate in your authorized Bidrock workspace.
Vivid MCP
Open a Vivid Business account from your AI chat via MCP.
How to run each
bidrock
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Vivid MCP As a remote MCP server
claude mcp add --transport http vivid-mcp https://api.prime.vivid.money/mcp
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Vivid MCP 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
Neither one's marketplaces publish the settings it asks for.
What it can do: bidrock · What it can do: Vivid MCP · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.