Skip to main content
Glama
Sign In
IMBA Agent MCP

IMBA Agent MCP

by clnt2021
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

IMBA Agent MCP

Personal GitHub copy for catalogs that require the connected GitHub username to own the repository (LobeHub Marketplace). Same npm packages and hosted remotes as the org repo.

Canonical Docker / Glama / Official Registry source: IMBAwallet/agent-mcp

This repository does not contain API keys, Ed25519 private keys, or registry seeds.

File

npm

Registry name

What it does

Dockerfile / Dockerfile.docs

@imba_wallet/agent-mcp-docs

com.imbawallet/agent-docs

Policy, HowTo, what agents buy. Docs only.

Dockerfile.spend

@imba_wallet/agent-mcp

com.imbawallet/agent

USDT TRC-20 + Visa prepaid / eSIM / gift cards with your key.

Hosted remotes: docs · spend

Playbooks: what agents buy · HowTo · API docs

LobeHub: lhm.plugin.json (docs MCP, cloudEndpoint https://imbawallet.com/mcp/docs). Publish:

npx -y @lobehub/market-cli plugin publish https://github.com/clnt2021/imba_agent_mcp --dir .

What agents buy

IMBA issues the payment instrument:

  • Visa/MasterCard prepaid — airlines, hotels, SaaS, or a datacenter that bills a card

  • Travel eSIM — cheap mobile data

  • Gift cards — live catalog (~20,000 positions; Apple, Steam, Google Play — search, do not hard-code a SKU)

ChatGPT Actions must not call spend.

Related MCP server: Vaaya

Install (stdio)

Docs:

npx -y @imba_wallet/agent-mcp-docs@0.1.5
{
  "mcpServers": {
    "imba-agent-docs": {
      "command": "npx",
      "args": ["-y", "@imba_wallet/agent-mcp-docs@0.1.5"]
    }
  }
}

Spend (operator key):

{
  "mcpServers": {
    "imba-agent": {
      "command": "npx",
      "args": ["-y", "@imba_wallet/agent-mcp"],
      "env": {
        "IMBA_AGENT_CLIENT_ID": "YOUR_CLIENT_ID",
        "IMBA_AGENT_PRIVATE_KEY": "-----BEGIN PRIVATE KEY-----\\n...\\n-----END PRIVATE KEY-----"
      }
    }
  }
}

Claude Code:

/plugin marketplace add clnt2021/imba_agent_mcp
/plugin install imba-agent@imba-agent

Agent skill: npx skills add clnt2021/imba_agent_mcp --skill imba-agent

Keep in sync

When catalog packaging changes (plugin.json, mcp.json, skills/, llms-install.md, Dockerfiles, lhm.plugin.json), update this repo and IMBAwallet/agent-mcp. SSOT in Wallet: docs/features/agent_mcp.md.

Available Tools

6 tools
get_agent_factsAgent API factsA
Read-onlyIdempotent

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.

Inputs: no named parameters.

get_agent_use_casesWhat agents can buyA
Read-onlyIdempotent

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.

Inputs: no named parameters.

get_catalog_placementWhere to list each MCPA
Read-onlyIdempotent

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

Inputs: no named parameters.

get_public_urlFetch a public IMBA Agent URLA
Read-onlyIdempotent

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

Inputs: url (required).

get_tier_policyAgent tier policyC
Read-onlyIdempotent

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

Inputs: no named parameters.

list_docs_urlsList public Agent URLsC
Read-onlyIdempotent

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

Inputs: no named parameters.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 6 tools

    Disambiguation4/5

    Most tools have clearly distinct retrieval purposes, but get_agent_facts and get_tier_policy overlap somewhat since the facts tool explicitly includes tier policy. The remaining tools—use cases, catalog placement, public URL fetching, and URL listing—are well separated.

    Naming Consistency5/5

    Tool names consistently follow a verb_noun pattern with snake_case, using get_ for individual lookups and list_ for enumerating resources. This is predictable and readable across the entire set.

    Tool Count5/5

    Six tools is well-scoped for a documentation and policy retrieval server. Each tool covers a meaningful slice of the domain without unnecessary redundancy or bloat.

    Completeness5/5

    The set covers the main knowledge retrieval needs: facts, use cases, tier policy, catalog placement, URL discovery, and direct URL fetching. For a read-only docs/policy MCP, there are no obvious gaps that would block an agent from answering questions.

    Maintenance

    ActivityStale
    ResponsivenessNo recent community issues

    Resources

    Related MCP Connectors

    Related MCP Servers