DEVELOPER PROTOCOL & SPECS

Build, connect, and execute with LitEngine MCP.

LitEngine implements the standard Model Context Protocol (MCP) specification to provide AI models with deterministic access to UK corporate registries, operational CRMs, and email dispatchers.

PROTOCOL SPECIFICATION

JSON-RPC 2.0 Streamable HTTP Transport

LitEngine is built on the official Model Context Protocol transport specification (spec versions 2025-06-18, 2025-03-26, 2024-11-05).

Stateless & Serverless Resilient:

Per the MCP transport spec, requests are answered with Content-Type: application/json. Every request carries its own authentication context, eliminating fragile websocket drops.

DNS Rebinding Protection:

Enforces origin validation against hostile browser attacks, allowing authenticated calls from Claude server-to-server or authorized web clients.

mcp-spec-compliance.jsonSTRICT
{
  "protocol": "Model Context Protocol (MCP)",
  "jsonrpc": "2.0",
  "supportedVersions": [
    "2025-06-18",
    "2025-03-26",
    "2024-11-05"
  ],
  "transports": [
    "HTTP POST (stateless)",
    "stdio (cli runtime)"
  ],
  "authentication": [
    "OAuth 2.0 Bearer Token",
    "URL-Secret SHA-256 (60-day grant)"
  ],
  "safetyGates": [
    "Human Approval Queue",
    "6-digit one-time confirmation codes"
  ]
}
AUTHENTICATION & ENDPOINTS

Official connection front doors

LitEngine exposes two production connection routes to accommodate both modern OAuth connectors and token-based environments.

RECOMMENDED • OAUTH 2.0POST

Claude OAuth Front Door

https://litengine.in/api/mcp/server

The primary endpoint used in Claude's connector dialog. If called without credentials, it returns an authenticated 401 with standard WWW-Authenticate pointing to the discovery metadata trailhead.

Header: Authorization: Bearer <access_token>
DIRECT CONNECTOR • TOKENPOST

Workspace URL Token Endpoint

https://litengine.in/api/mcp/s/{WORKSPACE_SECRET_TOKEN}

Designed for clients that accept a single connection URL without custom header configuration. The token is hashed with SHA-256 and expires automatically after 60 days.

Security: Constant-time hash verification with automatic token rotation.

Claude Desktop Configuration

Add this to your local claude_desktop_config.json

macOS / Windows / Linux
{
  "mcpServers": {
    "litengine": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-fetch",
        "https://litengine.in/api/mcp/s/YOUR_WORKSPACE_TOKEN"
      ]
    }
  }
}
EXPOSED CAPABILITIES

Verified MCP Tool Catalog

Every tool below is implemented in production and workspace-isolated. AI clients discover these tools dynamically via tools/list.

Corporate Intelligence & Distress Screening

distress_screen_search()JSON-RPC 2.0

Searches UK Companies House filings, parses XBRL accounts, and calculates net asset / working capital distress scores.

Input Arguments:
{ "sectorCode": "SIC 41202", "minAgeYears": 3, "distressOnly": true }
find_contact()JSON-RPC 2.0

Retrieves a contact and their associated company profile, statutory status, and outstanding charges.

Input Arguments:
{ "query": "patric.cassidy@cassidygroupltd.com" }

CRM Pipeline & Relationship Queries

who_is_waiting()JSON-RPC 2.0

Surfaces high-priority contacts who reached out or require immediate advisor follow-up.

Input Arguments:
{ "limit": 10 }
list_hot_leads()JSON-RPC 2.0

Lists active leads scored by high distress indicators, open email signals, and response state.

Input Arguments:
{ "stage": "qualified", "limit": 25 }
pipeline_summary()JSON-RPC 2.0

Returns aggregated counts of contacts across all stages (New, Qualified, Sequence Active, Review, Closed).

Input Arguments:
{}
search_contacts()JSON-RPC 2.0

Performs workspace-scoped search with tag filtering, domain matching, and status constraints.

Input Arguments:
{ "filter": { "tag": "priority_distress", "hasEmail": true } }

Intelligent Sequences & Approval Gates

create_sequence()JSON-RPC 2.0

Creates a draft multi-step email sequence with custom step delays and tone guardrails.

Input Arguments:
{ "name": "Distress Follow-up", "stepCount": 3, "intervalDays": 4 }
preview_sequence()JSON-RPC 2.0

Generates rendered previews of all emails for an approved list, including verified financial figures.

Input Arguments:
{ "sequenceId": "seq_9481a" }
approve_sequence()JSON-RPC 2.0

Requires a 6-digit server-minted verification code to release messages into the approved send queue.

Input Arguments:
{ "sequenceId": "seq_9481a", "confirmCode": "582914" }
review_outbox()JSON-RPC 2.0

Inspects currently pending messages in the operator approval queue.

Input Arguments:
{ "status": "pending_approval" }
DEVELOPER ACCESS

Request Sandbox API Tokens

Connect your development team to test corporate XBRL parsing and CRM execution directly in your local environment.

Request API credentials