MCP tools and lifecycle

The txcast endpoint is remote Streamable HTTP MCP:

https://api.txcast.com/mcp

Every request requires the bearer credential. The server supports modern and legacy-stateless clients, so callers must not depend on one persistent process or session.

Tool discovery

tools/list is filtered by credential scopes. Tool inputs and structured outputs use the same authoritative schemas as REST. The server validates graph refinements again when a tool is called.

All annotations are explicit. Write tools remain marked non-idempotent for conservative host prompts even though txcast enforces an idempotency key.

Mutation fields

Every mutating tool requires:

{
    "caller": {
        "name": "Codex",
        "version": "client version"
    },
    "idempotencyKey": "stable-key-for-this-exact-operation"
}

Caller strings are printable, 1–64 characters, and self-reported. Modern per-request MCP host metadata may be recorded separately but does not replace caller and is never authorization input.

Confirmation boundary

The server marks sensitive operations for interaction, but the MCP host controls whether it actually prompts. Always keep local confirmation on for writes. Safe/EOA handoffs still require a separate wallet to sign or broadcast.

Reconnect and retry

If the host reconnects, it can call tools/list again and continue from freshly read resource versions. Do not cache run, step, attempt, workflow revision, or draft versions across unrelated sessions.

For failed mutations, follow idempotency and retry guidance rather than inventing a new key automatically.