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 Docs

REMOTE · IMBAWALLET.COM · 2 COMPONENTS

Read-only IMBA Agent API docs MCP. No register, deposit, buy, or withdraw.

0 this week 91 Trust /100

Last scanned (18 hours ago)

Scores higher than 98% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Crypto and Web3

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 Security91
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server, and every tool looks verifiably read-only (it declares readOnlyHint: true, starts its name with a read verb and describes no write), so an anonymous caller can read but cannot change anything. We can't see whether a tool returns data specific to one caller, so keep any per-user data behind authorisation. View diagnostics → Pass
  • 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
Schema Quality & AI Usability69
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 274 tokens (~45/item across 6 items; 6 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 Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 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 +1
    • Stability: 0.97 → pass security
  • 10 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 8 Nov 26 +1
    • Stability: 0.97 → pass security
  • 7 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 6 Nov 26 +7
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → 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
  • 25 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
  • 2 Sept 26 0
    • Tool “get_public_url” rewrote its description, which is the text the model reads security
    • Tool “get_agent_facts” rewrote its description, which is the text the model reads security
    • Tool “list_docs_urls” rewrote its description, which is the text the model reads security
    • Schema quality: 39 → 45 ▼ functional
    • Server version: 0.1.4 → 0.1.5 functional
    • New tool “get_agent_use_cases” functional
    • “get_public_url” reworded the description of “url” cosmetic
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/docs

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/docs Verified 200
http (plaintext) http://imbawallet.com/mcp/docs HTTPS enforced 301 https://imbawallet.com/mcp/docs
MCP tools · 6 exposed · ~274 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
get_agent_facts ~53

Canonical prepaid-agent policy and catalog: Visa prepaid, eSIM, gift cards, KYT address screen, USDT TRC-20, forbidden rails, tiers. Cite as-is. Does not move money.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_agent_use_cases ~53

Playbook: Visa prepaid (flights, datacenter bills), travel eSIM, ~20k gift cards, paid KYT address screen. MCP tools per job. Cite as-is. Does not move money.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_catalog_placement ~27

Which directories take the docs MCP vs the spend MCP. OpenAI is docs-only.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_public_url ~78

HTTP GET of an allowlisted public docs URL (HowTo, use cases, discovery JSON, llms-agent). Never calls register/deposit/buy.

NameTypeReqDescription
urlstringyesAbsolute https://imbawallet.com URL from the allowlist (HowTo, use cases, tiers, well-known, openapi discovery, llms-agent).

No output schema declared.

No examples provided.

get_tier_policy ~38

Tier 0 vs 1+. Convert closed at 0 (AML). Convert at 1 is a separate request. Withdraw stays closed.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_docs_urls ~25

HowTo, use cases, tiers, discovery, OpenAPI, MCP endpoints.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the IMBA Agent Docs MCP server?

IMBA Agent Docs is a hosted endpoint at https://imbawallet.com/mcp/docs, 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-docs 'https://imbawallet.com/mcp/docs'
Common questions

What is the IMBA Agent Docs MCP server?

IMBA Agent Docs is an MCP server listed in the public MCP registry as com.imbawallet/agent-docs. Read-only IMBA Agent API docs MCP. No register, deposit, buy, or withdraw. This page covers its hosted endpoint (https://imbawallet.com/mcp/docs).

Is the IMBA Agent Docs MCP server safe to use?

IMBA Agent Docs scores 91 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 Docs MCP server expose?

IMBA Agent Docs exposes 6 tools: get_agent_facts, get_agent_use_cases, get_tier_policy, get_catalog_placement, get_public_url, list_docs_urls. Their descriptions and schemas cost roughly 274 tokens of context every time the server is loaded.

Does the IMBA Agent Docs MCP server require authentication?

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

Is the IMBA Agent Docs MCP server still maintained?

IMBA Agent Docs 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 Docs MCP server?

VerifyMCP ran 13 checks on IMBA Agent Docs, 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.