Data Collection
ltc.supply
Provides current Litecoin blockchain and market data including price, block height, network statistics, privacy layer stats, and universal search.
ENDPOINT 1
https://ltc.supply/mcp
MCP server metadata
- Name
- ltc-supply
- Version
- 1.0.0
Known tools 9
get_ltc_priceCurrent Litecoin price and market data (USD, EUR, GBP, JPY, market cap, volume)
Inferred read-onlyget_network_statsLitecoin network statistics: block height, hashrate, difficulty, supply
Inferred read-onlyget_mweb_statsCurrent MWEB (MimbleWimble Extension Blocks) privacy layer statistics
Inferred read-onlysearchUniversal search: Litecoin address, transaction hash, block hash, or block height
Inferred read-onlyverify_paymentCheck whether a pay-per-request LTC payment has confirmed on-chain.
Potential side effectsmweb_locked_historyFull historical MWEB locked-supply dataset (daily snapshots since collection began).
Inferred read-onlymining_pool_historyFull mining pool distribution history (4-hour snapshots since collection began).
Inferred read-onlyCONNECT 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.ltc-supply]
url = "https://ltc.supply/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"ltc-supply": {
"type": "http",
"url": "https://ltc.supply/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: ltc-supply
Remote MCP URL: https://ltc.supply/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": {
"ltc-supply": {
"url": "https://ltc.supply/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"ltc-supply": {
"type": "http",
"url": "https://ltc.supply/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "ltc-supply",
"transport": "streamable-http",
"url": "https://ltc.supply/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.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.