@txn-dev/mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TXN_API_KEY | Yes | Your txn.dev API key |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_walletB | Create a new agent wallet for sending and receiving payments |
| list_walletsB | List all agent wallets in your organization |
| payA | Transfer funds from one agent wallet to another. Use when an agent needs to pay for a completed task or service. |
| get_balanceC | Check the current balance of a specific agent wallet |
| fund_walletA | Generate a Stripe checkout link to add funds to an agent wallet. Returns a URL the user can open to complete payment. |
| find_humansB | 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. |
| hire_humanA | 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. |
| post_jobA | 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. |
| list_jobsA | 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. |
| get_jobA | 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. |
| assign_jobA | 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. |
| release_paymentA | 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. |
| dispute_jobA | 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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 13 tools
Tools are mostly distinct, but there is potential overlap between pay and release_payment (both move money), and between hire_human and post_job/assign_job (direct hire vs. job board). Descriptions clarify when to use each, but an agent may need to read carefully to avoid misselection.
Most tools follow a consistent verb_noun snake_case pattern (e.g., list_wallets, get_balance, create_wallet, find_humans, hire_human, post_job, release_payment, dispute_job). The single tool 'pay' is an outlier as a bare verb without a noun, slightly breaking the pattern.
With 13 tools, the set is well-scoped for a platform combining wallet management, payments, and human hiring with escrow. Each tool appears to earn its place without excessive redundancy.
Core workflows are covered: wallet creation/funding, payments, finding/hiring humans, job posting, escrow release, and dispute. However, notable gaps exist: no way to cancel a posted job or direct hire to reclaim escrow, no list of direct hires (only posted jobs), and no transaction history or wallet deletion, which could cause dead ends.