Analytics
escalake.com
Provides access to Escalake public government price and cost indices and computes price escalation adjustments between dates using weighted index data.
ENDPOINT 1
https://escalake.com/api/mcp
MCP server metadata
- Name
- escalake
- Version
- 1.0.0
Known tools 3
search_indicesSearch Escalake’s public index catalog: government-published price/cost indices (PPI, CPI, ECI, and similar series) commonly cited in price escalation and price adjustment clauses for parts, materials, labor, and services.
Inferred read-onlyget_index_observationsGet published data points for one Escalake public index over a date range (default: last 5 years, capped at 500 rows per call).
Inferred read-onlycompute_escalated_priceCompute a price escalation from one or more Escalake public indices: a base price, a base date, a target date, per-index weights (up to 5), an optional fixed non-escalating portion of the price, and an optional cap/floor on the resulting percentage change.
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.escalake]
url = "https://escalake.com/api/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"escalake": {
"type": "http",
"url": "https://escalake.com/api/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: escalake
Remote MCP URL: https://escalake.com/api/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": {
"escalake": {
"url": "https://escalake.com/api/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"escalake": {
"type": "http",
"url": "https://escalake.com/api/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "escalake",
"transport": "streamable-http",
"url": "https://escalake.com/api/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.