Skip to documentation

MCP.

Connect a client

Use Streamable HTTP at https://tovahub.com/mcp with the same Bearer token. Client configuration formats differ; the example is a generic configuration, not a promise that every client accepts it.

Request example
{
  "mcpServers": {
    "tovahub": {
      "url": "https://tovahub.com/mcp",
      "headers": { "Authorization": "Bearer <YOUR_TOKEN>" }
    }
  }
}

Discover tools

Use tools/list for the tools and parameters available to the current session. Anonymous access covers service information, plans, regions and wallet authentication; team tools require authentication. Resources and prompts are not provided.

Payment boundary

pay_quote and deposit_usd are MCP-only. x402 payment authorization belongs in _meta["x402/payment"], not tool arguments. Clients need explicit signing and payment support. Human tokens can use sufficient team USD; wallet payment requires an AI identity.

Read results

Ordinary tool results include JSON text and structuredContent.data. x402 uses its own result structure; payment requirements can arrive with HTTP 200 and isError:true. Inspect the tool result, not just the transport status.

Client connection guide