IMBA Agent Spend
REMOTE · IMBAWALLET.COM · 2 COMPONENTS · SCANNED SEP 22
IMBA spend MCP: USDT TRC-20 deposit and catalog buy with your key. No withdraw.
Available components
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
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (create_card). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
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 Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
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
claude mcp add --transport http com-imbawallet-agent 'https://imbawallet.com/mcp/spend'
{
"mcpServers": {
"com-imbawallet-agent": {
"url": "https://imbawallet.com/mcp/spend"
}
}
} {
"servers": {
"com-imbawallet-agent": {
"type": "http",
"url": "https://imbawallet.com/mcp/spend"
}
}
} [mcp_servers.com-imbawallet-agent] url = "https://imbawallet.com/mcp/spend"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-imbawallet-agent": {
"type": "remote",
"url": "https://imbawallet.com/mcp/spend",
"enabled": true
}
}
} openclaw mcp add com-imbawallet-agent --url 'https://imbawallet.com/mcp/spend' --transport streamable-http
mcp_servers:
com-imbawallet-agent:
url: "https://imbawallet.com/mcp/spend" {
"McpServers": {
"com-imbawallet-agent": {
"Transport": "http",
"Url": "https://imbawallet.com/mcp/spend"
}
}
} assistant mcp add com-imbawallet-agent -t streamable-http -u 'https://imbawallet.com/mcp/spend'
{
"mcpServers": {
"com-imbawallet-agent": {
"type": "http",
"url": "https://imbawallet.com/mcp/spend"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 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 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 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 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 5 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
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 Sept 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=YE2,O=Let's Encrypt,C=US | 26 Jul 2026 | 24 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 623fdd0c6c23d13e0a82ab430e21a50f9a0 |
| SANs: imbawallet.com, www.imbawallet.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| 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. | present | 19718 | 13 | Verified |
| imbawallet.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 |
| 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 |
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 →
create_card Buy a virtual 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.
| Name | Type | Req | Description |
|---|---|---|---|
| birth_date | string | – | – |
| country | string | – | – |
| string | – | Cardholder KYC email, not the agent 3DS mailbox. | |
| ext_id | string | yes | Idempotency key. Reuse the same id to retry the same order. |
| first_name | string | – | – |
| imba_product_id | integer | yes | – |
| last_name | string | – | – |
| phone | string | – | – |
No output schema declared.
No examples provided.
get_balance Ledger 2401 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 Card payment credentials ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| card_id | string | yes | – |
| cvv | boolean | – | – |
No output schema declared.
No examples provided.
get_deposit_address USDT TRC-20 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 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 Paid 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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | – |
| network | string | yes | – |
| refresh | boolean | – | – |
No output schema declared.
No examples provided.
kyt_check_get KYT check by id ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | integer | yes | – |
No output schema declared.
No examples provided.
kyt_checks KYT history ~57
POST /api/kyt_checks. Own KYT history plus quote fields. Use to find a past address check. Space ~1s. Never pass client_id.
| Name | Type | Req | Description |
|---|---|---|---|
| last_id | integer | – | – |
| limit | integer | – | – |
No output schema declared.
No examples provided.
kyt_quote KYT price ~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 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 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 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).
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | – |
| esim_provider | string | – | – |
No output schema declared.
No examples provided.
list_gift_offers 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.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | – | – |
No output schema declared.
No examples provided.
list_notifications Inbox and 3DS OTP ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
| limit | integer | – | – |
| prev_id | integer | – | – |
| prev_ts | number | – | – |
No output schema declared.
No examples provided.
purchase_esim Buy an eSIM plan ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| ext_id | string | yes | – |
| iccid | string | – | – |
| payment_source | string | – | – |
| plan_id | string | yes | – |
No output schema declared.
No examples provided.
purchase_gift Buy a gift card ~83
POST /api/purchase. Buy a brand gift code (Apple, Steam, Google Play, … — live list). ext_id required. Never payment_source=stars.
| Name | Type | Req | Description |
|---|---|---|---|
| expected_price | object | – | – |
| ext_id | string | yes | – |
| offer_id | string | yes | – |
| payment_source | string | – | – |
| required_fields | object | – | – |
No output schema declared.
No examples provided.
rotate_hmac Rotate webhook 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.
| Name | Type | Req | Description |
|---|---|---|---|
| callback_url | string | – | – |
| string | – | – | |
| jwe_public_key | string | – | – |
No output schema declared.
No examples provided.
set_webhook Set callback URL / JWE / OTP email ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| callback_url | string | – | – |
| string | – | – | |
| jwe_public_key | string | – | – |
No output schema declared.
No examples provided.
topup_card Top up a 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.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | – |
| card_id | string | yes | – |
| ext_id | string | yes | – |
No output schema declared.
No examples provided.
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 72 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 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.