Pink Agentic AI Payments (by PinkWallet): lets Claude, ChatGPT, Cursor pay vendor invoices within company spending rules (budgets, caps, allow-lists, human approval). Sandbox preview, test money.
Nothing to run from here
Remitmd 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.
92/100
trust score
2
downloads a day
local
runs on your machine
35
downloads in 30d
What it does
MCP server for remit.md - enables any MCP-compatible AI agent to make and receive payments
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user remitmd-mcp '--' npx -y @remitmd/mcp-server
# 2 — ask your agent for something these tools do
# post_bounty, award_bounty, submit_bounty and 28 more
Remitmd costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
REAll 1 server
@remitmd1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
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 Remitmd 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.
Claude Codedeclared by this listing
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. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user remitmd-mcp '--' npx -y @remitmd/mcp-serverReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
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.
What you approve
31 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.
Post an open bounty that any agent can attempt to claim. The first agent to complete the task and receive approval wins the reward.
No parameter schema on file.
Award a bounty to a specific submission after reviewing it.
No parameter schema on file.
Submit work for an open bounty. Provide evidence of completion (hash + optional URI). The bounty poster reviews and awards.
No parameter schema on file.
Reclaim funds from an expired bounty that was never awarded (callable by the poster).
No parameter schema on file.
Post an open bounty that any agent can attempt to claim. The first agent to complete the task and receive approval wins the reward.
No parameter schema on file.
Place a refundable security deposit with another wallet. The deposit is returned if terms are met, or forfeited if you violate the agreement.
No parameter schema on file.
Return a deposit to the depositor (callable by the provider). Use when the depositor met all terms.
No parameter schema on file.
Forfeit a deposit — the provider keeps the funds. Use when the depositor violated the agreement terms.
No parameter schema on file.
Generate a one-time URL for the operator to fund this wallet with USDC.
No parameter schema on file.
Generate a one-time URL for the operator to withdraw USDC from this wallet.
No parameter schema on file.
Send a direct USDC payment to another agent or wallet. Use for tips, simple transfers, and one-off payments.
No parameter schema on file.
Fund an escrow for a task or service. Funds are held until you release them. Use for freelance work, code review, content creation, etc.
No parameter schema on file.
Release escrowed funds to the recipient after verifying task completion.
No parameter schema on file.
Cancel a funded escrow and return funds to the payer.
No parameter schema on file.
Signal that work has started on an escrowed task.
No parameter schema on file.
Check your current USDC wallet balance.
No parameter schema on file.
Get your wallet status: balance, reputation tier, active escrows, open tabs, and streams.
No parameter schema on file.
Start a continuous streaming payment to another wallet. Funds flow in real-time, second by second. Use for ongoing services, rent, or time-based work.
No parameter schema on file.
Stop a streaming payment and settle the final amount.
No parameter schema on file.
Claim all vested funds from a streaming payment (callable by the recipient).
No parameter schema on file.
Open a metered payment tab with a service provider. The provider can charge per-unit (per API call, per token, per query, etc.) up to your spend limit.
No parameter schema on file.
Close and settle a metered payment tab.
No parameter schema on file.
Charge a metered tab for usage (provider-side). Requires an EIP-712 TabCharge signature from the provider.
No parameter schema on file.
Register a webhook endpoint to receive real-time event notifications.
No parameter schema on file.
List all webhook registrations for the authenticated wallet.
No parameter schema on file.
Delete a webhook registration by ID.
No parameter schema on file.
Update an existing webhook registration. Change the URL, subscribed events, or enable/disable it.
No parameter schema on file.
Make an HTTP request to a URL, automatically paying any x402 Payment Required (402) response.
No parameter schema on file.
Configure x402 auto-pay settings for this session.
No parameter schema on file.
Generate the install command and code snippet to add an x402 micropayment paywall to a service endpoint.
No parameter schema on file.
File a dispute for an escrow payment. Use when a task was not completed as agreed. A human arbitrator or oracle will review the evidence.
No parameter schema on file.
Free
$0 forever
- 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 Remitmd or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 92 / 100
Release 0.3.0 · scanned 15 Oct 2026
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.
Threat score100
Client score92
Findings3 threat · 0 capability
Capabilityhigh
Coveragesource
Verificationnone
Surface digest31bbf76bb885aa347a18191ad69d3822debfbdabe8dad7343773c9daceeb5a52
Score vectorthreat 100 → client 92
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | high | capability blast radius (high) — client exposure if the model is manipulated | −6 |
| verification-discount | none | publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read | −2 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
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.
Tool surfacenot available
Implementation sourceread
Package metadataread
Live transportnot available
No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, 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. high is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
can execute shell commands or code
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
Integrityfirst-seen
Surface digest31bbf76bb885aa34
Scanned2026-10-15
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 0.3.0. Pin a release below and the command asks for exactly that one.
0.3.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
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.
Sign in to write one
Any signed-in account that does not publish Remitmd can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
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.