The Adyen Model Context Protocol server allows you to integrate with Adyen APIs through LLMs function calling utilizing various Clients. It
from $19/mo
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.
Open Installation—
p95 latency
—
call success
local
runs on your machine
—
calls last 7d
What it does
MCP server for remit.md - enables any MCP-compatible AI agent to make and receive payments
Quickstart
# 1 — run it from where its publisher ships it
npx -y @remitmd/mcp-server
# 2 — ask your agent something
> MCP server for remit.md - enables any MCP-compatible AI agent to make and receive payments
Remitmd is free: there is no plan to choose, no cap to set and nothing that can bill you.
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. It is scanned, signed and pinned to the version you choose — 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. Claude Code registers it in one command.
claude mcp add remitmd-mcp -- npx -y @remitmd/mcp-serverReconnect, or start a new session, and the tools appear in the model’s tool list.
Free to install, and it runs from its publisher’s own package: no account, no key, no card.
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.
Takes no parameters.
Example callreturns →
Award a bounty to a specific submission after reviewing it.
Takes no parameters.
Example callreturns →
Submit work for an open bounty. Provide evidence of completion (hash + optional URI). The bounty poster reviews and awards.
Takes no parameters.
Example callreturns →
Reclaim funds from an expired bounty that was never awarded (callable by the poster).
Takes no parameters.
Example callreturns →
Post an open bounty that any agent can attempt to claim. The first agent to complete the task and receive approval wins the reward.
Takes no parameters.
Example callreturns →
Place a refundable security deposit with another wallet. The deposit is returned if terms are met, or forfeited if you violate the agreement.
Takes no parameters.
Example callreturns →
Return a deposit to the depositor (callable by the provider). Use when the depositor met all terms.
Takes no parameters.
Example callreturns →
Forfeit a deposit — the provider keeps the funds. Use when the depositor violated the agreement terms.
Takes no parameters.
Example callreturns →
Generate a one-time URL for the operator to fund this wallet with USDC.
Takes no parameters.
Example callreturns →
Generate a one-time URL for the operator to withdraw USDC from this wallet.
Takes no parameters.
Example callreturns →
Send a direct USDC payment to another agent or wallet. Use for tips, simple transfers, and one-off payments.
Takes no parameters.
Example callreturns →
Fund an escrow for a task or service. Funds are held until you release them. Use for freelance work, code review, content creation, etc.
Takes no parameters.
Example callreturns →
Release escrowed funds to the recipient after verifying task completion.
Takes no parameters.
Example callreturns →
Cancel a funded escrow and return funds to the payer.
Takes no parameters.
Example callreturns →
Signal that work has started on an escrowed task.
Takes no parameters.
Example callreturns →
Check your current USDC wallet balance.
Takes no parameters.
Example callreturns →
Get your wallet status: balance, reputation tier, active escrows, open tabs, and streams.
Takes no parameters.
Example callreturns →
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.
Takes no parameters.
Example callreturns →
Stop a streaming payment and settle the final amount.
Takes no parameters.
Example callreturns →
Claim all vested funds from a streaming payment (callable by the recipient).
Takes no parameters.
Example callreturns →
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.
Takes no parameters.
Example callreturns →
Close and settle a metered payment tab.
Takes no parameters.
Example callreturns →
Charge a metered tab for usage (provider-side). Requires an EIP-712 TabCharge signature from the provider.
Takes no parameters.
Example callreturns →
Register a webhook endpoint to receive real-time event notifications.
Takes no parameters.
Example callreturns →
List all webhook registrations for the authenticated wallet.
Takes no parameters.
Example callreturns →
Delete a webhook registration by ID.
Takes no parameters.
Example callreturns →
Update an existing webhook registration. Change the URL, subscribed events, or enable/disable it.
Takes no parameters.
Example callreturns →
Make an HTTP request to a URL, automatically paying any x402 Payment Required (402) response.
Takes no parameters.
Example callreturns →
Configure x402 auto-pay settings for this session.
Takes no parameters.
Example callreturns →
Generate the install command and code snippet to add an x402 micropayment paywall to a service endpoint.
Takes no parameters.
Example callreturns →
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.
Takes no parameters.
Example callreturns →
Freeyour plan
$0 forever
- Every tool, no call limit
- No card, no account needed
- Source published under a licence you can read
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because nothing bills
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable. Remitmd costs nothing to install and nothing to call, 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: $8.42
$16.58 left
ATrust score 92 / 100
Release 0.3.0 · scanned 26 Aug 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
Findings1 threat · 2 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-08-26
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
Pinned to 0.3.0 — the install command below asks for that release. A pin is part of an install, so it is kept for this visit and written down when you install.
0.3.0
undated
installedNo release note was published with this version.
—
no reviews yet
Reviews are earned
Only accounts with at least 50 real tool calls against this server in the last 90 days can post. Ratings are weighted by how much the reviewer actually uses it, and publishers can reply once per review.
Reviews are earned
Writing one takes an account with at least 50 real tool calls against Remitmd in the last 90 days. That is the whole gate — there is no other way to post, which is why the counts beside each review are worth reading.
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 an account with 50 real tool calls against it.