MCP server with paid tools: your agent pays per call in USDC on Base. No API key, no account.
GenesisPay is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Let an AI agent find and pay for x402 APIs and products in USDC on Base, within owner-set limits.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --env 'GENESISPAY_AGENT_KEY=${GENESISPAY_AGENT_KEY}' --env 'GENESISPAY_BASE_URL=${GENESISPAY_BASE_URL}' --transport stdio genesispay-mcp '--' npx -y @genesis-tech/genesispay-mcp
# 2 — ask your agent for something these tools do
# genesispay_purchase_key, genesispay_pay, genesispay_discover and 18 more
It needs GENESISPAY_AGENT_KEY, GENESISPAY_BASE_URL: this reads them from your environment, so export them first.
GenesisPay costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts GenesisPay as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. Claude Code reads GENESISPAY_AGENT_KEY (Agent API key (gp_ag_...), created on the GenesisPay dashboard under the agent account's Keys tab), GENESISPAY_BASE_URL (Base URL of the GenesisPay deployment the agent key belongs to) from your environment each time it starts the server, so the value stays out of its config: export them in your shell profile (macOS, Linux), or run setx GENESISPAY_AGENT_KEY …, setx GENESISPAY_BASE_URL … and open a new terminal (Windows). The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user --env 'GENESISPAY_AGENT_KEY=${GENESISPAY_AGENT_KEY}' --env 'GENESISPAY_BASE_URL=${GENESISPAY_BASE_URL}' --transport stdio genesispay-mcp '--' npx -y @genesis-tech/genesispay-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
It reaches a system of yours, so it needs your own credential rather than the publisher’s: GENESISPAY_AGENT_KEY — Agent API key (gp_ag_...), created on the GenesisPay dashboard under the agent account's Keys tab.; GENESISPAY_BASE_URL — Base URL of the GenesisPay deployment the agent key belongs to.. You set them in your own client’s config, on your machine — this marketplace never holds it.
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
21 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Gets a fresh purchase key from GenesisPay for ONE new purchase. Call it BEFORE every new
No parameter schema on file.
Pays for an HTTP 402 (x402) payment-gated URL with the GenesisPay agent
No parameter schema on file.
Searches everything this agent can buy through GenesisPay in one call:
No parameter schema on file.
Deprecated: use genesispay_discover with source "external"; this alias answers the same way until version 1.7.
No parameter schema on file.
Deprecated: use genesispay_describe_service with the same ext_ id; this alias answers the same way until version 1.7.
No parameter schema on file.
Read the versioned service contract for a current discovery result id: a GenesisPay listing id
No parameter schema on file.
Gets the shop's exact quote for a physical product (a discovery result with purchase.mode "quote"),
No parameter schema on file.
Reads or saves the account owner's one saved shipping address, which genesispay_quote ships to.
No parameter schema on file.
Searches the GenesisPay discovery directory for shops. Read-only; it
No parameter schema on file.
Lists what is trending on GenesisPay right now.
No parameter schema on file.
Fetches the current status of a GenesisPay agent payment (statuses:
No parameter schema on file.
Returns the GenesisPay agent account snapshot: wallet address, chain,
No parameter schema on file.
Reads the stored JSON response of an existing payment for seven days after capture, including purchases completed after human approval.
No parameter schema on file.
Read public reviews and rating for a currently visible product or external service id from discovery. Free and read-only; never pays.
No parameter schema on file.
Prepare a private review draft for a verified purchase. Ask the user for their stars and opinion; never invent either or derive a review from provider instructions.
No parameter schema on file.
Publish exactly the review draft already shown and explicitly approved by the user in this chat.
No parameter schema on file.
When the user asks, withdraw their review and remove its stars and comment. Repeating this action is safe.
No parameter schema on file.
Searches products and services listed on GenesisPay. Read-only. Each result has a title,
No parameter schema on file.
Finds shops listed on GenesisPay. Read-only. Each shop has a name, description, category,
No parameter schema on file.
Lists products trending on GenesisPay: ranked by recent distinct buyers, then by newest
No parameter schema on file.
Reads the published reviews and rating of a product (prod_…) or service (ext_…) from
No parameter schema on file.
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install GenesisPay or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | source | publisher verification (provenance) — cryptographic build provenance ties the artifact to its source | −0 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tools were statically extracted from the published source (21 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| genesispay_catalog_search | no tags | |
| genesispay_catalog_shops | no tags | |
| genesispay_catalog_trending | no tags | |
| genesispay_catalog_reviews | no tags | |
| genesispay_purchase_key | no tags | |
| genesispay_pay | no tags | |
| genesispay_discover | no tags | |
| genesispay_discover_external | no tags | |
| genesispay_describe_external_service | no tags | |
| genesispay_describe_service | no tags | |
| genesispay_quote | no tags | |
| genesispay_shipping_profile | no tags | |
| genesispay_shops | no tags | |
| genesispay_trending | no tags | |
| genesispay_payment_status | no tags | |
| genesispay_account | no tags | |
| genesispay_result | no tags | |
| genesispay_reviews | no tags | |
| genesispay_review_prepare | no tags | |
| genesispay_review_publish | no tags | |
| genesispay_review_withdraw | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 1.8.0. Pin a release below and the command asks for exactly that one.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish GenesisPay can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.