Vibes-Coded Agent Security and Commerce Tools vs three.ws Agent Payments
Vibes-Coded Agent Security and Commerce Tools is an MCP server published by doteyeso-ops. Marketplaces we read that list it: 1 (Official MCP Registry). three.ws Agent Payments is an MCP server published by nirholas. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-24. 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 |  Vibes-Coded Agent Security and Commerce Tools |  three.ws Agent Payments |
|---|---|---|
| Official MCP Registry | Listed Version: 1.6.1 Forks (GitHub): 0 Stars (GitHub): 3 Not marked · First seen |
Listed Version: 0.1.5 Downloads/month (npm): 207 Downloads/week (npm): 47 Forks (GitHub): 69 Stars (GitHub): 246 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 | Vibes-Coded Agent Security and Commerce Tools | three.ws Agent Payments |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 3 (worse) | 246 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 69 (better) |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (vibes-coded-mcp-production.up.railway.app/mcp) | On your machine (@three-ws/agentcore-payments-mcp) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 4, secrets among them: 2 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/doteyeso-ops/mcp-server-vibes-coded | github.com/nirholas/three.ws |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 6 days ago | no remote endpoint we check |
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
Vibes-Coded Agent Security and Commerce Tools
Agent supply-chain security, scanner consensus, x402 reliability, and commerce MCP tools.
three.ws Agent Payments
Governed x402 payment sessions: pay any endpoint with budget, allowlist & per-tx caps, no key.
How to run each
Vibes-Coded Agent Security and Commerce Tools As a remote MCP server
claude mcp add --transport http mcp-server-vibes-coded https://vibes-coded-mcp-production.up.railway.app/mcpthree.ws Agent Payments As a local MCP server: npm package
claude mcp add --env "PAYMENT_SESSION_TOKEN=<YOUR_PAYMENT_SESSION_TOKEN>" --env "THREE_WS_SESSION=<YOUR_THREE_WS_SESSION>" --transport stdio agentcore-payments-mcp -- npx -y @three-ws/agentcore-payments-mcpRequires: PAYMENT_SESSION_TOKEN (secret), THREE_WS_SESSION (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Vibes-Coded Agent Security and Commerce Tools 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 Vibes-Coded Agent Security and Commerce Tools publish no settings it asks for, so we do not compare settings.
What it can do: Vibes-Coded Agent Security and Commerce Tools · What it can do: three.ws Agent Payments · 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.