Ext Ops Panel
Open dashboard
Comparison

Brex vs dev.workers.sebastiaan-ba3.payverify/tools

Brex is a plugin bundle for AI coding tools published by Cursor. Marketplaces we read that list it: 1 (Cursor: cursor/plugins). dev.workers.sebastiaan-ba3.payverify/tools is an MCP server published by payverify.sebastiaan-ba3.workers.dev. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-15. 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
MarketplaceBrexdev.workers.sebastiaan-ba3.payverify/tools
Cursor: cursor/plugins Listed
Version: 1.0.0
Forks (GitHub): 1 107
Stars (GitHub): 11 352
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.0
No figure published
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

Brex vs dev.workers.sebastiaan-ba3.payverify/tools
FactBrexdev.workers.sebastiaan-ba3.payverify/tools
Marketplaces that list it11
Stars (GitHub) (differs)11 352No figure on GitHub
Forks (GitHub) (differs)1 107No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Remote server (api.brex.com/mcp)Remote server (payverify.sebastiaan-ba3.workers.dev/mcp)
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)1Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/cursor/pluginsNot stated
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-10-15
Endpoint at the last check (differs)Responded 30 h ago, requires a keynot checked yet

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

Brex

In its own words, on Cursor: cursor/plugins:

Query expenses, receipts, bills, cards, and travel.

dev.workers.sebastiaan-ba3.payverify/tools

In its own words, on Official MCP Registry:

Verify a Base USDC transaction or x402 settlement landed. Free, no account needed.

How to run each

Brex

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

dev.workers.sebastiaan-ba3.payverify/tools As a remote MCP server

Claude Code
claude mcp add --transport http tools https://payverify.sebastiaan-ba3.workers.dev/mcp

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

Only Brex 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: Brex · What it can do: dev.workers.sebastiaan-ba3.payverify/tools · Compare two other plugins

Data comes from the public marketplace file https://github.com/cursor/plugins/blob/HEAD/.cursor-plugin/marketplace.json. 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