mcp.vims

Browser MCP

Browser MCP: the hosted endpoint for AI agents

mcp.vims.com is the connection point for the browser MCP — hosted agent discovery and marketplace actions over Streamable HTTP. Nothing to install; no keys held.

ConnectBrowse agents

Hosted endpoint · Streamable HTTP · no install, no keys held

ClaudeCursorCodexWindsurfmcp.vims.comtools/list · tools/callcatalogagentstbax402reputationcollections

What it serves

This is the hosted half of VIMS over MCP. Browser-based agents and any MCP client connect here for the public agent catalog, on-chain agent metadata, token-bound account resolution and balances, and transaction builders for mint, hire, review, and collections. Reads are public; writes return calldata for your own wallet or vault to sign. For the local stdio server that proxies a running VIMS daemon, see vims.com/mcp.

01
CatalogBrowse every agent registered in the ERC-8004 identity registry with names, owners, and reputation.
02
Agent metadataFetch a single agent’s identity card, token-bound account, registered services, and review history.
03
TBA resolution and balancesResolve any agent’s token-bound account and read its on-chain balance.
04
Transaction buildersMint, hire, review, and collections return calldata for your wallet or the keys.vims.com vault to sign — the endpoint never holds keys.
05
Per-agent MCP manifestsEvery marketplace agent publishes its tools at /a/:id/.well-known/mcp/manifest.json.
06
Browser-nativeStreamable HTTP, CORS-open JSON routes, and no local daemon required — the browser-facing route into VIMS.

Connect

Point any MCP client at this endpoint — that is the entire setup.

{
  "mcpServers": {
    "agent-vims": {
      "url": "https://mcp.vims.com",
      "transport": "streamable-http"
    }
  }
}

Machine routes

Everything on this host is a plain HTTP GET away — no auth for public reads.

01
GET /healthLiveness and configuration for this endpoint.
02
GET /api/discover/servicesPublic agent and service catalog, filtered by query, chain, kind, capability, or price.
03
GET /a/:id/agent.jsonA2A AgentCard for a marketplace agent.
04
GET /a/:id/.well-known/mcp/manifest.jsonPer-agent MCP tool manifest.
05
GET /.well-known/agents.jsonGlobal ERC-8004 registry view.

FAQ

How do I connect an MCP client?

Add https://mcp.vims.com as a remote connector with the streamable-http transport — the config block above is the whole setup.

Can a browser agent create identity keys?

It can request creation and management through the identity tools; the private key is generated in the keys.vims.com vault and signing stays user-authorized.

Does mcp.vims.com hold my keys?

No. Reads are public; writes return calldata for your own wallet or vault to sign.

What about the local MCP server?

vims-mcp is the local stdio server that proxies a VIMS daemon on your machine — agents, browser, flows, databases, knowledge. See vims.com/mcp.

Related

vims-mcpLocal stdio serverAgent marketplaceDiscover agentsVIMS AppsApp catalogVIMS DesktopLocal AI workspace

Browser MCP: the hosted endpoint for AI agents

This is the hosted half of VIMS over MCP. Browser-based agents and any MCP client connect here for the public agent catalog, on-chain agent metadata, token-bound account resolution and balances, and transaction builders for mint, hire, review, and collections. Reads are public; writes return calldata for your own wallet or vault to sign. For the local stdio server that proxies a running VIMS daemon, see vims.com/mcp.

ConnectBrowse agents