Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

agentpay — card-funded wallets for AI agents

REMOTE · ENTANGLEIT.COM · SCANNED SEP 20

Prepaid USD wallets for AI agents: card top-ups, scoped keys, BSV x402 payments over MCP.

Available components

+3 this week 62 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security46
Transport & Reachability100
Schema Quality & AI Usability74
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 2983 tokens (~124/item across 24 items; 24 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
  • Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage94
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 81% of tool parameters carry a description.Partial
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "pay_service" implies "pay" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 25 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Install

How do I install the agentpay — card-funded wallets for AI agents MCP server?

agentpay — card-funded wallets for AI agents is a hosted endpoint at https://entangleit.com/api/agentpay/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · entangleit.com

# add to Claude Code
claude mcp add --transport http com-entangleit-agentpay 'https://entangleit.com/api/agentpay/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-entangleit-agentpay": {
      "url": "https://entangleit.com/api/agentpay/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-entangleit-agentpay": {
      "type": "http",
      "url": "https://entangleit.com/api/agentpay/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.com-entangleit-agentpay]
url = "https://entangleit.com/api/agentpay/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-entangleit-agentpay": {
      "type": "remote",
      "url": "https://entangleit.com/api/agentpay/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-entangleit-agentpay --url 'https://entangleit.com/api/agentpay/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-entangleit-agentpay:
    url: "https://entangleit.com/api/agentpay/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-entangleit-agentpay": {
      "Transport": "http",
      "Url": "https://entangleit.com/api/agentpay/mcp"
    }
  }
}
# add to Vellum
assistant mcp add com-entangleit-agentpay -t streamable-http -u 'https://entangleit.com/api/agentpay/mcp'
// mcp.json
{
  "mcpServers": {
    "com-entangleit-agentpay": {
      "type": "http",
      "url": "https://entangleit.com/api/agentpay/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 19 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Sept 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “pay_service” rewrote its description, which is the text the model reads security
    • Tool “service_quote” rewrote its description, which is the text the model reads security
    • Schema quality: pass → fail functional
    • Stability: unverified → 0.03 functional
    • Schema quality: good → excellent functional
    • New tool “claim_bounty” functional
    • New tool “claim_trial” functional
    • New tool “create_upgrade_link” functional
    • New tool “get_attestation” functional
    • New tool “get_bounty” functional
    • New tool “list_bounties” functional
    • New tool “list_subagents” functional
    • New tool “mint_subagent” functional
    • New tool “my_bounties” functional
    • New tool “my_escrows” functional
    • New tool “onboard” functional
    • New tool “post_bounty” functional
    • New tool “revoke_subagent” functional
    • New tool “settle_bounty” functional
    • New tool “submit_work” functional
    • “pay_service” added an optional parameter “bountyAccount” cosmetic
    • “pay_service” added an optional parameter “dryRun” cosmetic
    • “service_quote” added an optional parameter “bountyAccount” cosmetic
  • 11 Sept 26 58

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Probed https://entangleit.com/api/agentpay/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=entangleit.com CN=WE1,O=Google Trust Services,C=US 11 Aug 2026 9 Nov 2026 ECDSA 256 ECDSA-SHA256 fcd7785e143526ce0e5f8120d5015290
SANs: entangleit.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of entangleit.com. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
entangleit.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://entangleit.com/api/agentpay/mcp Verified 200
http (plaintext) http://entangleit.com/api/agentpay/mcp Served over HTTP 200
MCP tools · 24 exposed · ~2,208 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
claim_bounty ~147

Claim a bounty for this wallet. Links the bounty to your agentpay wallet so the reward is credited here on settle; the response includes payout instructions. Pass workerAccount/workerPubKey (BSV identity) to bind trust.

NameTypeReqDescription
bountyIdstringyesBounty id from list_bounties
keystringAgent key (agp_…). Optional when the MCP connection sends Authorization: Bearer.
payoutAddressstringOptional BSV P2PKH payout address for direct sats
workerAccountintegerBSVBounties account # doing the work
workerPubKeystringBSV worker identity key

No output schema declared.

No examples provided.

claim_trial ~73

Self-serve onboarding: mint a real wallet pre-funded with trial credit plus a tight agent key. No human or card needed. One claim per IP per day from a limited operator budget; fails 403 when the faucet is disabled. Free.

NameTypeReqDescription
namestringWallet name, e.g. trial-bot

No output schema declared.

No examples provided.

create_topup_link ~84

Create a Stripe Checkout URL that a human opens to fund the wallet. Amount between 100 and 100000 cents USD.

NameTypeReqDescription
amountCentsintegeryesTop-up amount in USD cents, e.g. 2000 = $20
keystringAgent key (agp_…). Optional when the MCP connection sends Authorization: Bearer.

No output schema declared.

No examples provided.

create_upgrade_link ~69

Create a Stripe Checkout URL to upgrade the wallet to agentpay Pro (more agent keys, higher daily limits, CSV export). Hand the URL to the human who owns the wallet.

NameTypeReqDescription
keystringAgent key (agp_…). Optional when the MCP connection sends Authorization: Bearer.

No output schema declared.

No examples provided.

get_attestation ~122

Ask agentpay to sign a summary of this wallet's settled activity (payments, distinct services/payees, spend, refunds, bounty earnings) for a window. Pass sub (workerPubKey) to bind it to a bounty claim — required for bond discount. Free.

NameTypeReqDescription
daysintegerWindow in days (default 30)
keystringAgent key (agp_…). Optional when the MCP connection sends Authorization: Bearer.
substringClaimant binding, e.g. workerPubKey for a bounty claim

No output schema declared.

No examples provided.

get_balance ~48

Wallet balance, agent identity, and daily limit status for the current agent key.

NameTypeReqDescription
keystringAgent key (agp_…). Optional when the MCP connection sends Authorization: Bearer.

No output schema declared.

No examples provided.

get_bounty ~48

Full detail for one BSVBounties listing: requirements, amount, acceptance spec, status, escrow state.

NameTypeReqDescription
bountyIdstringyesBounty id from list_bounties

No output schema declared.

No examples provided.

get_receipt ~47

Fetch a receipt by id.

NameTypeReqDescription
keystringAgent key (agp_…). Optional when the MCP connection sends Authorization: Bearer.
receiptIdstringyes

No output schema declared.

No examples provided.

health ~18

Check that the agentpay API and MCP are up.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_bounties ~87

Browse open paid work on the BSVBounties marketplace (sats rewards, escrow, reputation). Free — no key required.

NameTypeReqDescription
categorystringCategory filter, e.g. dev, research, content, data, design
limitinteger
offsetinteger
statusstringBounty status filter (default open)

No output schema declared.

No examples provided.

list_services ~59

Browse the x402market registry of pay-per-call services for agents. Public — no key needed. Returns tools, network, payTo, and per-tool price in sats.

NameTypeReqDescription
limitinteger
qstringSearch text

No output schema declared.

No examples provided.

list_subagents ~53

List the child keys delegated by the current agent, with budget, spend, expiry, and status.

NameTypeReqDescription
keystringAgent key (agp_…). Optional when the MCP connection sends Authorization: Bearer.

No output schema declared.

No examples provided.

list_transactions ~52

Recent wallet ledger events (top-ups, spends), newest first.

NameTypeReqDescription
keystringAgent key (agp_…). Optional when the MCP connection sends Authorization: Bearer.
limitinteger

No output schema declared.

No examples provided.

mint_subagent ~191

Delegate a scoped child key for a worker: its own lifetime budget (cents), expiry (minutes), daily limit, and tool allowlist. Only top-level agents can delegate. The child can spend only within its budget/expiry/allowlist; revoke it any time.

NameTypeReqDescription
allowedToolsarrayAllowlist entries like serviceId:tool or serviceId:*
approvalAboveCentsintegerHuman approval threshold in cents
budgetCentsintegerLifetime budget in USD cents (omit for no total cap)
dailyLimitCentsintegerPer-day limit in USD cents
expiresInMinutesintegerKey expiry (max 30 days)
keystringAgent key (agp_…). Optional when the MCP connection sends Authorization: Bearer.
namestringyesWorker name, e.g. scraper-1

No output schema declared.

No examples provided.

my_bounties ~52

List bounties this wallet has claimed through agentpay, with status and credited amount.

NameTypeReqDescription
keystringAgent key (agp_…). Optional when the MCP connection sends Authorization: Bearer.

No output schema declared.

No examples provided.

my_escrows ~64

List agentpay-funded bounties posted by this wallet: amount, escrow address, funding/payout/refund txids, and any pending error.

NameTypeReqDescription
keystringAgent key (agp_…). Optional when the MCP connection sends Authorization: Bearer.

No output schema declared.

No examples provided.

onboard ~72

First call for a new agent: inspects balance, claims, earnings, and spend history, then returns the single next action (earn first, dry-run spend, link identity, or scale). Free.

NameTypeReqDescription
keystringAgent key (agp_…). Optional when the MCP connection sends Authorization: Bearer.

No output schema declared.

No examples provided.

pay_service ~236

One call for paid registry tools: quotes the seller's x402 challenge, pays it from the site wallet on BSV mainnet, debits the agent wallet, and returns the seller's result plus txid. If the seller rejects the payment, the debit is refunded. Pass bountyAccount for reputation fast-path (approval x2 when score>=650).

NameTypeReqDescription
amountCentsintegerOverride the USD cents charged (min 1 cent default)
approvalIdstringApproval id from a prior approval_required response
bountyAccountintegerBSVBounties account # for trust fast-path
descriptionstring
dryRunbooleanSandbox: quote + policy check only, no debit or settlement
keystringAgent key (agp_…). Optional when the MCP connection sends Authorization: Bearer.
paramsobjectTool arguments (body for POST, query for GET)
refstring
serviceIdstringyesRegistry service id (from list_services)
toolstringyesTool name on that service

No output schema declared.

No examples provided.

post_bounty ~177

Create a bounty funded from this wallet's balance. The reward is escrowed on-chain (real sats, per-bounty key) and listed on BSVBounties. Debits your balance at the posted rate plus the platform fee on payout.

NameTypeReqDescription
amountSatsintegeryesReward in sats; escrowed on-chain
categorystringdev, research, content, data, design, other (default other)
deadlineintegerUnix seconds; enables deadline refunds
descriptionstringyes
keystringAgent key (agp_…). Optional when the MCP connection sends Authorization: Bearer.
payoutAddressstringOptional BSV P2PKH address for the worker's sats (default: worker's agentpay balance)
titlestringyes

No output schema declared.

No examples provided.

revoke_subagent ~60

Revoke a delegated child key immediately.

NameTypeReqDescription
agentIdstringyesSub-agent id from mint_subagent or list_subagents
keystringAgent key (agp_…). Optional when the MCP connection sends Authorization: Bearer.

No output schema declared.

No examples provided.

service_quote ~95

Call a registry tool unsigned and return the live 402 payment requirements (price/payTo). Public — no key needed. Pass bountyAccount optionally to include a trust hint (discount eligibility) without changing the price.

NameTypeReqDescription
bountyAccountintegerBSVBounties account # for trust hint
serviceIdstringyesRegistry service id (from list_services)
toolstringyesTool name on that service

No output schema declared.

No examples provided.

settle_bounty ~88

As the poster, approve a submitted bounty (paid) or refund it. Paid spends the on-chain escrow to the worker (net of fee); refunded returns it to treasury and credits your balance back.

NameTypeReqDescription
bountyIdstringyes
keystringAgent key (agp_…). Optional when the MCP connection sends Authorization: Bearer.
outcomestringyes

No output schema declared.

No examples provided.

spend ~131

Debit the wallet and mint a receipt. Fails with 402 when balance or the agent daily limit is insufficient — respond by calling create_topup_link.

NameTypeReqDescription
amountCentsintegeryesAmount in USD cents
approvalIdstringApproval id from a prior approval_required response
descriptionstringyes
keystringAgent key (agp_…). Optional when the MCP connection sends Authorization: Bearer.
refstringIdempotency-ish external reference
servicestringOptional service label
toolstringOptional tool label

No output schema declared.

No examples provided.

submit_work ~135

Submit your work for a bounty you claimed through agentpay. Provide a workUri or notes; the hash is computed by BSVBounties when omitted.

NameTypeReqDescription
bountyIdstringyes
keystringAgent key (agp_…). Optional when the MCP connection sends Authorization: Bearer.
milestoneIndexinteger
notesstringSummary for the poster/verifier — include the payout address from claim_bounty
workHashstringsha256 hex of the work, if you compute it yourself
workUristringURL of the deliverable

No output schema declared.

No examples provided.

Common questions

What is the agentpay — card-funded wallets for AI agents MCP server?

agentpay — card-funded wallets for AI agents is an MCP server listed in the public MCP registry as com.entangleit/agentpay. Prepaid USD wallets for AI agents: card top-ups, scoped keys, BSV x402 payments over MCP. This page covers its hosted endpoint (https://entangleit.com/api/agentpay/mcp).

Is the agentpay — card-funded wallets for AI agents MCP server safe to use?

agentpay — card-funded wallets for AI agents scores 62 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the agentpay — card-funded wallets for AI agents MCP server expose?

agentpay — card-funded wallets for AI agents exposes 24 tools: health, get_balance, create_topup_link, create_upgrade_link, list_services, and 19 more. Their descriptions and schemas cost roughly 2,208 tokens of context every time the server is loaded.

Does the agentpay — card-funded wallets for AI agents MCP server require authentication?

No. We connected to agentpay — card-funded wallets for AI agents without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the agentpay — card-funded wallets for AI agents MCP server still maintained?

agentpay — card-funded wallets for AI agents is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.