Overview
POST /v2/mcp is DocketLayer’s remote MCP server. It implements the MCP Streamable HTTP transport (protocol version 2025-11-25) over JSON-RPC 2.0. Any MCP-compatible client can connect directly using the endpoint URL.
Endpoint: https://api.docketlayer.ai/v2/mcp
Transport: MCP Streamable HTTP — POST only. GET returns 405.
Price: Free tools are free. Paid tools cost 0.99 × N cases. Payment is passed as a payment_tx argument (or payment_tx_keys/payment_tx_deliveries for docketlayer_wallet_info) — see below.
Client configuration
Claude Code
Claude Desktop
payment_tx.
Tools
Free tools
These tools require no payment and no wallet.docketlayer_status
Returns DocketLayer’s current operational status, covered courts, planned coverage, and API version. Equivalent to GET /v2/status.
No parameters.
docketlayer_court_list
Lists all courts DocketLayer covers or plans to cover, with court codes, names, jurisdictions, and case ID format patterns.
docketlayer_pricing
Returns the pricing model — per-query cost, free endpoints, and payment protocol.
No parameters.
Paid tools
Paid tools require apayment_tx argument: a base64-encoded signed Solana USDC transaction for $0.99 sent to DocketLayer’s settlement address.
If payment_tx is omitted, the tool returns structured payment instructions — the recipient address and required amount — which an AI assistant can use to guide the user through payment.
docketlayer_case_query
Queries a case for current context and recent docket activity. Equivalent to GET /v2/case. Costs $0.99.
docketlayer_case_monitor
Lightweight change check. Returns whether a case has new filings since last_checked. Equivalent to GET /v2/monitor. Costs $0.99.
docketlayer_case_batch
Queries up to 50 cases in a single call. Costs $0.99 × N cases — the payment transaction must cover the full batch. Equivalent to POST /v2/cases/batch.
docketlayer_wallet_info
Returns the wallet’s signing key state and optionally recent callback delivery history. Keys lookup costs 0.99 (requires a second payment transaction). Default is keys only.
Request format
The endpoint accepts standard JSON-RPC 2.0 requests:Responses
Tool-level errors (payment missing, case not found, rate limited) are returned as JSON-RPC errors within a 200 response, not as HTTP error codes.