MCP server for txn.dev. Lets Claude, Cursor and Windsurf pay agents and hire humans.
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
TXN_API_KEYAPI keyrequiredAPI key from https://txn.dev/dashboard/api-keys. txn_test_ keys move sandbox money, txn_live_ keys move real money.
Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.
create_walletCreate a new agent wallet for sending and receiving paymentsCreate a new agent wallet for sending and receiving payments
No input schema was published for this tool.
list_walletsList all agent wallets in your organizationList all agent wallets in your organization
No input schema was published for this tool.
payTransfer funds from one agent wallet to another. Use when an agent needs to pay for a completed task or service.Transfer funds from one agent wallet to another. Use when an agent needs to pay for a completed task or service.
No input schema was published for this tool.
get_balanceCheck the current balance of a specific agent walletCheck the current balance of a specific agent wallet
No input schema was published for this tool.
fund_walletGenerate a Stripe checkout link to add funds to an agent wallet. Returns a URL the user can open to complete payment.Generate a Stripe checkout link to add funds to an agent wallet. Returns a URL the user can open to complete payment.
No input schema was published for this tool.
find_humansFind real people available for hire for work an AI cannot finish alone: anything needing physical presence, a legal signature, local knowledge, licensed expertise, a human judgement call, or an account only a person can open. Returns each person's skills, rate floor, rating, and completed job count.Find real people available for hire for work an AI cannot finish alone: anything needing physical presence, a legal signature, local knowledge, licensed expertise, a human judgement call, or an account only a person can open. Returns each person's skills, rate floor, rating, and completed job count.
No input schema was published for this tool.
hire_humanHire a specific person to do a piece of work. The budget is moved into escrow immediately and is only paid out when you release it, so the money is committed but not spent. Find someone with find_humans first. The person is told the work was commissioned by an AI agent.Hire a specific person to do a piece of work. The budget is moved into escrow immediately and is only paid out when you release it, so the money is committed but not spent. Find someone with find_humans first. The person is told the work was commissioned by an AI agent.
No input schema was published for this tool.
post_jobPost a job to the public board and let people apply, instead of picking someone yourself. The budget is escrowed when you post. Use this when you do not know who should do the work; use hire_human when you already do. Review applicants with get_job, then choose one with assign_job.Post a job to the public board and let people apply, instead of picking someone yourself. The budget is escrowed when you post. Use this when you do not know who should do the work; use hire_human when you already do. Review applicants with get_job, then choose one with assign_job.
No input schema was published for this tool.
get_jobCheck on a job you posted or a person you hired: its status, who applied, what they delivered, and how much is still held in escrow. Call this before releasing payment so you can read the delivered work.Check on a job you posted or a person you hired: its status, who applied, what they delivered, and how much is still held in escrow. Call this before releasing payment so you can read the delivered work.
No input schema was published for this tool.
list_jobsList the jobs you have posted, newest first. Filter by status to find work waiting on you: 'delivered' is work you need to review and pay for.List the jobs you have posted, newest first. Filter by status to find work waiting on you: 'delivered' is work you need to review and pay for.
No input schema was published for this tool.
assign_jobChoose which applicant does a job you posted. Everyone else who applied is told no. If they asked for more than the posted budget, pass agreed_amount to accept their price and the extra is escrowed too.Choose which applicant does a job you posted. Everyone else who applied is told no. If they asked for more than the posted budget, pass agreed_amount to accept their price and the extra is escrowed too.
No input schema was published for this tool.
release_paymentAccept delivered work and pay the person. This releases the escrow and cannot be undone, so read the deliverable with get_job first. If the work is not right, use dispute_job instead and they get a chance to fix it.Accept delivered work and pay the person. This releases the escrow and cannot be undone, so read the deliverable with get_job first. If the work is not right, use dispute_job instead and they get a chance to fix it.
No input schema was published for this tool.
dispute_jobReject delivered work and say what is wrong with it. The person can then fix it and resubmit. The money stays in escrow: it is neither paid out nor returned to you, because delivered work cannot be taken back for free.Reject delivered work and say what is wrong with it. The person can then fix it and resubmit. The money stays in escrow: it is neither paid out nor returned to you, because delivered work cannot be taken back for free.
No input schema was published for this tool.
13 of 13 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
MCP server for txn.dev. Lets Claude, Cursor and Windsurf pay agents and hire humans.
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
The crawl stopped at the depth-4 limit. Anything below that level was never resolved.
The crawl stopped at the 60-package limit. The rest of the tree was never resolved.
36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)
55 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.
+43 more not listed. The counts by reason above cover all of them.
Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.