General Tools
cascadepump.app
Provides tools to list Cascade vertical turbine pump models and select pumps for a design flow and head.
ENDPOINT 1
https://cascadepump.app/mcp
MCP server metadata
- Name
- pump-performance-pro
- Version
- 0.1.0
Cascade vertical turbine pump selection. Use `select_pumps` to find pump models for a design duty point (flow and head; optional units, RPM, specific gravity) — it returns ranked selections with speed, stages, impeller diameter, efficiency, brake horsepower and NPSHr in US units. Use `list_models` to browse the full catalog with published ranges. Selections are preliminary; quote and submittal data must be created by Cascade staff.
Known tools 2
select_pumpsFind Cascade vertical turbine pump selections for a design flow and head.
Inferred read-onlylist_modelsList every pump model in the Cascade catalog with impeller diameter range, available speeds, published flow range, stage count and NPSHr limits.
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.pump-performance-pro]
url = "https://cascadepump.app/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"pump-performance-pro": {
"type": "http",
"url": "https://cascadepump.app/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: pump-performance-pro
Remote MCP URL: https://cascadepump.app/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": {
"pump-performance-pro": {
"url": "https://cascadepump.app/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"pump-performance-pro": {
"type": "http",
"url": "https://cascadepump.app/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "pump-performance-pro",
"transport": "streamable-http",
"url": "https://cascadepump.app/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.