Governed MCP routing: every agent call spend-capped, metered, sealed with a verifiable receipt.
Connect Remote server
claude mcp add --transport http conduit-router https://router.pipavia.com/mcp
{
"mcpServers": {
"conduit-router": {
"url": "https://router.pipavia.com/mcp"
}
}
}
{
"servers": {
"conduit-router": {
"type": "http",
"url": "https://router.pipavia.com/mcp"
}
}
}
Settings > Connectors > Add custom connector
URL: https://router.pipavia.com/mcp
Tools 6 found in our last check
route_chatSend a chat completion through Conduit Router: policy-checked, budget-checked, metered, and audit-receipted. Uses your own stored provider keys (BYOK). Pin a model as "provider:model" or let your standing terms choose.
list_modelsThe public model catalog: every model the router can serve, with provider, free-tier flag, task profiles, and pricing source/as-of.
get_usageYour cumulative meter (requests, tokens, provider cost, router charge), today's spend against your daily budget, and which providers you have keys stored for.
get_receiptOne of your calls' audit receipts (id like "rcpt_12") with its hash-chain proof: record hash validity, successor linkage, and the current chain head.
verify_receiptCryptographically verify a receipt record (yours or anyone's) against the router's audit chain: the record hash must recompute and the stored record at that sequence must match.
get_policyYour key's standing terms (mandate): task profile, per-request and daily budgets, model allowlist, fallback chain, region — plus kill-switch state.
Details
| Endpoint | https://router.pipavia.com/mcp (Streamable HTTP) |
| First published | 11 Nov 2026 |
| Last updated | 11 Nov 2026 |
| Registry name | org.aimlds/conduit-router |
More ai and media servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
