Conduit Router — Governed MCP Routing

org.aimldsPublished by aimlds.orgv1.5.1Updated Nov 12, 2026

Governed MCP routing: every agent call spend-capped, metered, sealed with a verifiable receipt.

The publisher's own server: 370.ai — AI Gateway: 100+ Chat Models, Image & Speech Generation

VerifiedStreamable HTTPWeb executableSecurity & MonitoringData & AnalyticsAI & ML

Overview

AI-generated overview

A remote MCP routing endpoint that governs agent calls with spend caps, metering and verifiable receipts.

What you can do
  • Routes agent tool calls through a governed endpoint
  • Applies spend caps to each agent call
  • Meters usage of routed calls
  • Issues a verifiable receipt for each call
  • No tool list, instructions or README is published, so the exact tools are not documented.
When to use it
Consider it when you want agent or MCP tool calls to pass through a layer that limits spending, tracks usage and produces receipts for auditing. Little public detail is available, so evaluate it against your own requirements first.
Requirements
A remote streamable HTTP endpoint; no local runtime, packages, environment variables or headers are declared. The manifest declares no authentication, and no account or key setup is documented.
Before you install
The service sits between your assistant and its tool calls, so routed requests and their content pass through a third party. It applies spend caps, which implies paid usage, but pricing is not documented. No authentication is declared, so verify how access is controlled before relying on it.

Installation

In SourceWeft

  1. Open Conduit Router — Governed MCP Routing in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/org.aimlds%2Fconduit-router/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "conduit-router-governed-routing": {
      "type": "http",
      "url": "https://router.pipavia.com/mcp"
    }
  }
}

README

Conduit Router — Governed MCP Routing

[mcptry]

The public listing face of the Conduit Router. The Router's source is proprietary and lives in a private repository; this repo is its public home for directory listings — the same pattern as nrupala/conduit-filings-fundamentals for the filings connector.

Governed MCP routing: every agent call spend-capped, metered, sealed with a verifiable receipt.

  • Endpoint: https://router.pipavia.com/mcp (streamable HTTP)
  • Discovery is open: any client may call initialize, ping, and tools/list without a credential and evaluate the server first.
  • Execution is keyed: every tool call requires a Conduit key. Get one at pipavia.com.
  • Registry: org.aimlds/conduit-router on the Official MCP Registry — the server.json in this repo is the published record.
  • Release log: pipavia.com/releases
  • Verify a receipt: router.pipavia.com/verify

Tools (6): route_chat · list_models · get_usage · get_receipt · verify_receipt · get_policy — each carries a title, a plain description, a described argument schema, and read/write annotations.

Sold by 2351485 ALBERTA INC. (AIMLDS) · Contact: [email protected]

Copyright © 2026 2351485 ALBERTA INC.

Source: README.md at commit 2235a72

Tools

0
SourceWeft has not read this server's tools yet.

Version history

2
  1. v1.5.1LatestNov 12, 2026
  2. v1.4.0Nov 11, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Router integrations

370.ai — AI Gateway: 100+ Chat Models, Image & Speech Generation

ai.routerOfficial publisher

Remote AI gateway MCP server that lets an assistant call 100+ chat models, generate images, and convert text to speech through one 370.ai API key.

Streamable HTTPWeb executableAuth
Media & Design4 toolsOct 24, 2026

KRouter

Published by GitHub account 398894496-arch

A local Markdown memory for coding agents: it recalls what was settled before, cites the page, and says when it does not know.

STDIODesktop only
Files & StorageNot validated · the package type cannot run in the sandboxNov 11, 2026

SentioGate FinOps & LLM Router

Published by GitHub account SentioGate

SentioGate MCP server for a BYOK LLM router: audit token waste, check tool-call safety, rank models, and delegate prompts.

Streamable HTTPWeb executable
Security & Monitoring6 toolsNov 11, 2026

SentioGate FinOps & LLM Router

Published by GitHub account HISHAMJOTTERREV

A BYOK AI router and FinOps gateway that lets an assistant audit token waste, check tool-call safety, optimize payloads, and pick cost-optimal models.

Streamable HTTPWeb executable
Security & Monitoring6 toolsNov 8, 2026

AI Media Router

Published by GitHub account jutsuhq

Generates images and videos through 40+ provider APIs using your own keys, and keeps a local asset library.

STDIODesktop only
Media & DesignNot validated · the package type cannot run in the sandboxNov 8, 2026