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.

IMBA Agent Spend

REMOTE · IMBAWALLET.COM · 2 COMPONENTS

IMBA spend MCP: USDT TRC-20 deposit and catalog buy with your key. No withdraw.

0 this week 74 Trust /100

Last scanned (15 hours ago)

Scores higher than 61% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Finance and Payments

Recent critical change

Authorization (8 Nov 2026). See the changelog before you install this server.

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 Security57
Transport & Reachability100
Schema Quality & AI Usability66
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 1471 tokens (~77/item across 19 items; 19 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage68
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 5% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 19 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 19 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
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 11 Nov 26 0
    • Stability: 0.97 → pass security
  • 10 Nov 26 0
    • Stability: pass → 0.97 functional
  • 8 Nov 26 0
    • Authorization: unverified → fail ▼ critical
    • Stability: unverified → pass ▲ security
    • Injection markers: unverified → pass ▲ security
    • Transport: fail → pass ▲ security
    • Endpoint reachability: unreachable → reachable ▲ functional
    • MCP protocol: unverified → pass ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
  • 7 Nov 26 0
    • Endpoint reachability: reachable → unreachable ▼ security
    • Tool safety: pass → unverified ▼ security
    • Authorization: fail → unverified ▼ security
    • Stability: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Tool coverage: 100 → unverified ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 5 Nov 26 0
    • Stability: 0.97 → pass security
  • 4 Nov 26 0
    • Stability: pass → 0.97 functional
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 21 Nov 2026 · Probed https://imbawallet.com/mcp/spend

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=imbawallet.com CN=YE1,O=Let's Encrypt,C=US 24 Sept 2026 23 Dec 2026 ECDSA 256 ECDSA-SHA384 54b47e5af116e88ab0d4e760930bb14c30e
SANs: imbawallet.com, www.imbawallet.com
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of imbawallet.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
imbawallet.com. No DS 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
Header Value
content-security-policy default-src 'self' https: data: blob:; script-src 'self' 'unsafe-inline' 'unsafe-eval' 'wasm-unsafe-eval' https://cdn.techtg.space https://mc.yandex.ru https://mc.yandex.com https://yastatic.net https://top-fwz1.mail.ru https:; connect-src 'self' https: wss: https://go.atechspace.live https://cdn.techtg.space; img-src 'self' data: blob: https:; style-src 'self' 'unsafe-inline' https:; font-src 'self' data: https:; worker-src 'self' blob:; frame-ancestors 'self'; object-src 'none'; base-uri 'self'
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://imbawallet.com/mcp/spend Verified 200
http (plaintext) http://imbawallet.com/mcp/spend HTTPS enforced 301 https://imbawallet.com/mcp/spend
MCP tools · 19 exposed · ~1,471 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
create_card ~180

Issue a Visa/MasterCard prepaid from this agent 2401 USDT so the agent can pay merchants that require a card (airlines, hotels, SaaS, datacenter/GPU clouds). POST /api/pin/create_card. ext_id required. imba_product_id is core.card_product.id. Never payment_source=stars. Never pass client_id. IMBA does not create the booking.

NameTypeReqDescription
birth_datestring––
countrystring––
emailstring–Cardholder KYC email, not the agent 3DS mailbox.
ext_idstringyesIdempotency key. Reuse the same id to retry the same order.
first_namestring––
imba_product_idintegeryes–
last_namestring––
phonestring––

No output schema declared.

No examples provided.

get_balance ~23

GET /api/balance. USDT is the spendable catalog currency.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_card_details ~101

POST /api/pin/get_card_details for a card this agent owns. Needed to present PAN at merchant checkout (airline, datacenter, SaaS). PAN/CVV arrive as card_encrypted JWE when jwe_public_key is registered (PATCH webhook). Without that key the number is masked. Never logs raw PAN. cvv defaults true. Never pass client_id.

NameTypeReqDescription
card_idstringyes–
cvvboolean––

No output schema declared.

No examples provided.

get_deposit_address ~54

POST /api/deposit_address blockchain=tron. Address is issued for the authenticated agent only. Always re-fetch before send. Do not cache. USDT TRC-20 only. 24h unfunded hold.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_spend_policy ~38

Forbidden rails and tier rules. Allowed catalog: Visa prepaid, travel eSIM, gift cards, paid KYT address screen. Read-only.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

kyt_check ~133

Screen a crypto address for dirt (sanctions / mixer exposure). Use BEFORE you accept a TRC-20 send, or AFTER a wallet is blocked and the reason is unclear. POST /api/kyt_check. Body: network (tron_usdt | eth | btc) + address. Debits ~0.99 USDT from 2401. Returns a report — does not gate deposit, does not ban or unblock. TON is not in this catalog. Never pass client_id. Space ~1s.

NameTypeReqDescription
addressstringyes–
networkstringyes–
refreshboolean––

No output schema declared.

No examples provided.

kyt_check_get ~61

POST /api/kyt_check_get. Poll until the report is ready. Own check only (404 otherwise). Use after kyt_check when a wallet was blocked and you need the dirt report. Never pass client_id.

NameTypeReqDescription
idintegeryes–

No output schema declared.

No examples provided.

kyt_checks ~57

POST /api/kyt_checks. Own KYT history plus quote fields. Use to find a past address check. Space ~1s. Never pass client_id.

NameTypeReqDescription
last_idinteger––
limitinteger––

No output schema declared.

No examples provided.

kyt_quote ~82

POST /api/kyt_quote. Price for a paid crypto-address screen (Didit). Debit is on kyt_check (~0.99 USDT from 2401), not on quote. Off unless didit.enabled and didit.agent_api. Does not gate TRON deposit. Not /api/client/kyt_* and not partner. Space ~1s.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_card_products ~37

POST /api/card_products. Use id as imba_product_id for create_card (Visa prepaid). Space catalog calls ~1s apart.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_cards ~22

POST /api/cards for the authenticated agent. No client_id argument.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_esim_plans ~69

POST /api/esim/plans. Travel/data eSIM. esim_provider=yesim. Optional country ISO2. Use plan id with purchase_esim. Space catalog calls ~1s apart (agent catalog_gap).

NameTypeReqDescription
countrystring––
esim_providerstring––

No output schema declared.

No examples provided.

list_gift_offers ~79

POST /api/offers. Live gift catalog (~20k positions / ~2k unique: Apple, Google Play, Steam, games, travel, retail). Optional query string. Then purchase_gift with offer_id + ext_id. Space catalog calls ~1s apart. Do not assume a SKU.

NameTypeReqDescription
querystring––

No output schema declared.

No examples provided.

list_notifications ~102

POST /api/notifications. Poll this when a Visa payment asks for 3-D Secure. Agents keep payload.code (never SMS, never Telegram). category=codes for 3-D Secure OTP. Also delivered on webhook field otp if callback_url is set, and optional email. Space catalog calls ~1s apart.

NameTypeReqDescription
categorystring––
limitinteger––
prev_idinteger––
prev_tsnumber––

No output schema declared.

No examples provided.

purchase_esim ~97

POST /api/esim/new_plan5. Buy a travel/data eSIM plan from this agent 2401. Omit blank/null iccid so SQL takes the new-eSIM path. A set iccid must already belong to this agent. ext_id required. Never Stars.

NameTypeReqDescription
ext_idstringyes–
iccidstring––
payment_sourcestring––
plan_idstringyes–

No output schema declared.

No examples provided.

purchase_gift ~83

POST /api/purchase. Buy a brand gift code (Apple, Steam, Google Play, … — live list). ext_id required. Never payment_source=stars.

NameTypeReqDescription
expected_priceobject––
ext_idstringyes–
offer_idstringyes–
payment_sourcestring––
required_fieldsobject––

No output schema declared.

No examples provided.

rotate_hmac ~91

POST /auth/v1/agent/hmac/rotate. Previous HMAC dies immediately. Requires an existing callback_url (400 callback_url required before rotate otherwise). Pass callback_url here to PATCH webhook first. Plaintext HMAC is returned once — store it; never a Wallet JWT.

NameTypeReqDescription
callback_urlstring––
emailstring––
jwe_public_keystring––

No output schema declared.

No examples provided.

set_webhook ~93

PATCH /auth/v1/agent/webhook. Sets https callback_url (required before hmac/rotate), optional X25519 jwe_public_key for card_encrypted, optional email for 3DS OTP. Not SMS. HMAC plaintext is shown once when a URL is first accepted.

NameTypeReqDescription
callback_urlstring––
emailstring––
jwe_public_keystring––

No output schema declared.

No examples provided.

topup_card ~69

POST /api/pin/topup_card from this agent 2401 USDT. card_id must belong to the same agent (SQL owner guard). ext_id required. Never Stars.

NameTypeReqDescription
amountnumberyes–
card_idstringyes–
ext_idstringyes–

No output schema declared.

No examples provided.

Install

How do I install the IMBA Agent Spend MCP server?

IMBA Agent Spend is a hosted endpoint at https://imbawallet.com/mcp/spend, 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 · imbawallet.com

# add to Claude Code
claude mcp add --transport http com-imbawallet-agent 'https://imbawallet.com/mcp/spend'
Common questions

What is the IMBA Agent Spend MCP server?

IMBA Agent Spend is an MCP server listed in the public MCP registry as com.imbawallet/agent. IMBA spend MCP: USDT TRC-20 deposit and catalog buy with your key. No withdraw. This page covers its hosted endpoint (https://imbawallet.com/mcp/spend).

Is the IMBA Agent Spend MCP server safe to use?

IMBA Agent Spend scores 74 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 IMBA Agent Spend MCP server expose?

IMBA Agent Spend exposes 19 tools: get_spend_policy, get_deposit_address, get_balance, list_cards, list_card_products, and 14 more. Their descriptions and schemas cost roughly 1,471 tokens of context every time the server is loaded.

Does the IMBA Agent Spend MCP server require authentication?

No. We connected to IMBA Agent Spend without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the IMBA Agent Spend MCP server still maintained?

IMBA Agent Spend is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the IMBA Agent Spend MCP server?

VerifyMCP ran 13 checks on IMBA Agent Spend, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.