API Tools

lightrail.tech

Provides tools to list supported chains and tokens, get cross-chain swap quotes, build unsigned transactions, and check transfer settlement status via the LightRail API.

1 endpoint6 known toolsFirst detected September 13, 2026Last detected September 13, 2026

ENDPOINT 1

https://www.lightrail.tech/api/agent/mcp

No auth detected

MCP server metadata

Name: lightrail
Version: 1.0.0

Capabilities

tools

Server instructions

LightRail routes swaps, bridges and stakes across every applicable liquidity source and returns the best. It is non-custodial: it never holds funds and never signs. lightrail_build_transaction returns an UNSIGNED transaction that the caller must sign and broadcast with its own key. Normal flow: lightrail_get_quotes -> pick a quote -> lightrail_build_transaction with that quote's `source` and `execution.build` passed back unchanged -> if approval.required is true, send approval.transaction first, then send transaction -> for cross-chain routes, poll lightrail_get_transfer_status. Amounts are always smallest-unit integer strings (wei-scale), never decimals. Use the zero address for a chain's native coin. Resolve token addresses with lightrail_list_tokens rather than from memory — a wrong address routes funds to the wrong contract.

Known tools 6

lightrail_list_chains

List the chains LightRail can route between.

Inferred read-only

lightrail_list_tokens

Ranked token lists for up to 20 chains, with verified addresses and decimals.

Inferred read-only

lightrail_get_quotes

Quote across every applicable source in parallel and rank by output; the best is tagged BEST RETURN.

Inferred read-only

lightrail_build_transaction

Turn a chosen quote into an UNSIGNED transaction.

Inferred read-only

lightrail_get_transfer_status

Settlement status of a cross-chain transfer: DONE, PENDING or FAILED.

Potential side effects

lightrail_get_portfolio

Per-chain balance breakdown for an address, to size a trade against what the wallet actually holds.

Potential side effects

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.lightrail]
url = "https://www.lightrail.tech/api/agent/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "lightrail": {
      "type": "http",
      "url": "https://www.lightrail.tech/api/agent/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: lightrail
Remote MCP URL: https://www.lightrail.tech/api/agent/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "lightrail": {
      "url": "https://www.lightrail.tech/api/agent/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "lightrail": {
      "type": "http",
      "url": "https://www.lightrail.tech/api/agent/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "lightrail",
  "transport": "streamable-http",
  "url": "https://www.lightrail.tech/api/agent/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.