MCP server

Endpoints

• POST https://mcp.answerline.dev/mcp with Authorization: Bearer <key>.
• POST https://mcp.answerline.dev/<API_KEY>/mcp for clients that cannot send headers. The URL contains your key: treat it as a secret.

The server speaks Streamable HTTP over POST and supports protocol revisions 2024-11-05 through 2025-11-25 and 2026-07-28. Clients that accept text/event-stream get tool calls streamed with keep-alive comments, so long calls survive proxies. GET and DELETE answer 405. Browser requests from origins not on the server's allow list are refused with 403.

Connecting a client

Claude Code

claude mcp add --transport http answerline https://mcp.answerline.dev/mcp --header "Authorization: Bearer $API_KEY"

Clients configured with an mcpServers JSON file that supports remote servers

{
  "mcpServers": {
    "answerline": {
      "url": "https://mcp.answerline.dev/mcp",
      "headers": {
        "Authorization": "Bearer sk_..."
      }
    }
  }
}

For clients that only take a URL, use the path form with your key in it.

Tools

One tool per engine your account can use, plus credits. Each engine tool's input schema is that endpoint's request schema, so its arguments are the request body listed on the engine page.

A tool result is the API's response. API errors come back as results marked isError with the error body, so the model can read its code. Credit and rate-limit headers and the request id are in the result's _meta.

Costs and timeouts

An engine tool call is a synchronous API call: it costs the engine's price plus 2 credits, holds a concurrency slot and can take up to five minutes, so raise your client's tool timeout where it is configurable. For recurring or large runs, use async tasks and batches instead.