Onboarding request - IMBA Wallet MCP: agentic wallets with virtual bank cards, eSIM, gift cards purchase

[clnt2021]

Request

Please onboard these two Official MCP Registry servers to the GitHub MCP Registry (github.com/mcp, api.mcp.github.com) so they appear in Copilot, the VS Code @mcp gallery, and Enterprise allowlists.

Per discussion #1257 (trent-j): Official Registry publish is required first; initial github.com/mcp onboarding is still manual curation; versions sync after onboard.

Servers

Field	Docs (read-only)	Spend (operator key)
Official name	com.imbawallet/agent-docs	com.imbawallet/agent
Title	IMBA Agent Docs	IMBA Agent Spend
Latest version	0.1.4 (active, isLatest)	0.1.4 (active, isLatest)
HTTP	https://imbawallet.com/mcp/docs (streamable-http, no auth)	https://imbawallet.com/mcp/spend (streamable-http)
npm	@imba_wallet/agent-mcp-docs@0.1.4	@imba_wallet/agent-mcp@0.1.4
Website	https://imbawallet.com/agent_api_about_en.html	same

Spend uses operator Ed25519 headers X-IMBA-Agent-Client-Id and X-IMBA-Agent-Private-Key (per-operator key; IMBA does not host a shared spend wallet). Docs has no auth. Default well-known discovery is docs-only.

Evidence — Official Registry (live)

curl -sS "https://registry.modelcontextprotocol.io/v0.1/servers?search=imbawallet&version=latest"

Returns com.imbawallet/agent-docs@0.1.4 and com.imbawallet/agent@0.1.4.

Direct:

• https://registry.modelcontextprotocol.io/v0.1/servers/com.imbawallet%2Fagent-docs/versions/latest
• https://registry.modelcontextprotocol.io/v0.1/servers/com.imbawallet%2Fagent/versions/latest

DNS namespace proof: https://imbawallet.com/.well-known/mcp-registry-auth

Evidence — GitHub MCP Registry (checked 2026-09-01)

curl -sS "https://api.mcp.github.com/v0.1/servers?search=imbawallet&limit=20"

Returns {"servers":[],"metadata":{"count":0,"total":0}}.

Same empty result for IMBA, IMBAwallet, com.imbawallet.

curl -sS -o /dev/null -w "%{http_code}" "https://api.mcp.github.com/v0.1/servers/com.imbawallet%2Fagent-docs/versions/latest"

Returns 404.

UI:

• https://github.com/mcp?q=imbawallet — not listed
• https://github.com/mcp/com.imbawallet/agent-docs — 404
• https://github.com/mcp/com.imbawallet/agent — 404

Repositories

• Public source / Docker / catalog README: https://github.com/IMBAwallet/agent-mcp
• Official server.json currently cites https://github.com/IMBAwallet/IMBA_front (private Flutter host that also ships the HTTP MCP image). Happy to point GitHub cards at the public IMBAwallet/agent-mcp repo if that is required for listing.

Why two entries

Docs is the crawler-safe, unauthenticated server. Spend is a separate server and must not be the default well-known target. Please list both names; do not collapse them into one gallery card that points at spend by default.

Happy to provide extra metadata, a public README install snippet, or a probe of the HTTP endpoints. Thank you.

[masumtanjim7]

Hi @clnt2021,

Reviewing your onboarding request and curl probes against both registries:

1. Verification of the 404 on api.mcp.github.com

The 404 response you are seeing when curling https://api.mcp.github.com/v0.1/servers/com.imbawallet%2Fagent.docs/versions/latest is expected at this stage:

• The GitHub MCP Registry integration uses a curated staging and indexing pipeline.
• Even after being published to the official MCP Registry (registry.modelcontextprotocol.io), external servers do not automatically propagate or reflect immediately on GitHub’s endpoints without manual curation/allowlisting from the GitHub team.

2. Schema and Two-Entry Structuring

Having two distinct registry entries (com.imbawallet/agent.docs for unauthenticated read-only crawler documentation and com.imbawallet/agent for authenticated private transactions) conforms with security best practices:

• Splitting tool definitions reduces unnecessary token overhead during standard documentation queries.
• It cleanly separates endpoints requiring operator authorization (X-IMBA-Agent-Client-Id / X-IMBA-Agent-Private-Key) from public reads, preventing execution risk during automated agent tool selection.

3. Next Steps for Onboarding

Because ingestion into api.mcp.github.com and Copilot gallery indexing requires maintainer approval:

• Repository maintainers review requests in batches according to the catalog intake schedule.
• Ensure that the public Docker image and repository README remain publicly accessible without requiring credentials for automated health checks.

Maintainers will review and confirm once the upstream synchronization job includes your endpoints.

---

If this clarifies the 404 behavior and ingestion lifecycle, feel free to mark this as the accepted answer!