# Conduit Router — Governed MCP Routing (remote · router.pipavia.com)

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

- Trust score: 79/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `router.pipavia.com`: 79/100 (this document), [markdown](https://verifymcp.io/servers/org-aimlds-conduit-router/router.md), [page](https://verifymcp.io/servers/org-aimlds-conduit-router/router)

## Channel facts

- Endpoint: `https://router.pipavia.com/mcp`
- Transports: `streamable-http`
- Auth: `required (not validated)`
- Version: `1.5.1`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 89/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 72/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 428 tokens (~71/item across 6 items; 6 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Conduit Router — Governed MCP Routing server?

Conduit Router — Governed MCP Routing is a hosted endpoint at https://router.pipavia.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http org-aimlds-conduit-router 'https://router.pipavia.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "org-aimlds-conduit-router": {
      "url": "https://router.pipavia.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "org-aimlds-conduit-router": {
      "type": "http",
      "url": "https://router.pipavia.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.org-aimlds-conduit-router]
url = "https://router.pipavia.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "org-aimlds-conduit-router": {
      "type": "remote",
      "url": "https://router.pipavia.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add org-aimlds-conduit-router --url 'https://router.pipavia.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  org-aimlds-conduit-router:
    url: "https://router.pipavia.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "org-aimlds-conduit-router": {
      "Transport": "http",
      "Url": "https://router.pipavia.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add org-aimlds-conduit-router -t streamable-http -u 'https://router.pipavia.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "org-aimlds-conduit-router": {
      "type": "http",
      "url": "https://router.pipavia.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-20 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-18 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-16 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-14 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-13 (score 75, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-12 (score 75, +39)

- [security improvement] Transport: unverified → pass
- [security improvement] Injection markers: unverified → pass
- [security] First check of Judged manipulation: pass
- [security] Authorization: Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
- [functional regression] MCP protocol: unverified → fail
- [functional improvement] Tool coverage: unverified → 100
- [functional] First check of Schema quality: fail
- [functional] First check of Destructive annotations: 100
- [functional] First check of Schema quality: pass
- [functional] First check of Schema quality: good
- [functional] First check of Tool coverage: 100

### 2026-11-11 (score 36)

First indexed and scored.

## MCP tools (6)

### `route_chat` (~186 tokens)

Route a chat completion

Send 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.

Input parameters:

- `max_tokens` (number): Optional cap on the completion's output tokens.
- `messages` (array, required): OpenAI-shaped messages: [{role, content}] with role system|user|assistant|tool.
- `model` (string): Optional pin: "provider:model" (e.g. "groq:llama-3.3-70b-versatile"), "custom:<endpoint_id>:<model>", or a bare catalog model id.
- `task_profile` (string): Optional routing profile: reasoning (deepest models), tool-use, or bulk (cheapest/fastest). Defaults to your standing terms.

### `list_models` (~36 tokens)

List routable models

The public model catalog: every model the router can serve, with provider, free-tier flag, task profiles, and pricing source/as-of.

### `get_usage` (~38 tokens)

Check usage and budget headroom

Your cumulative meter (requests, tokens, provider cost, router charge), today's spend against your daily budget, and which providers you have keys stored for.

### `get_receipt` (~68 tokens)

Fetch a call receipt

One of your calls' audit receipts (id like "rcpt_12") with its hash-chain proof: record hash validity, successor linkage, and the current chain head.

Input parameters:

- `receipt_id` (string, required): The receipt id from a routed call, e.g. "rcpt_12".

### `verify_receipt` (~60 tokens)

Verify a receipt record

Cryptographically 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.

Input parameters:

- `receipt` (object, required): The full audit record object from a receipt.

### `get_policy` (~40 tokens)

Read your standing terms

Your key's standing terms (mandate): task profile, per-request and daily budgets, model allowlist, fallback chain, region — plus kill-switch state.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/org-aimlds-conduit-router/router#diagnostics

## Score history

- 2026-11-21: 79
- 2026-11-20: 79
- 2026-11-19: 78
- 2026-11-18: 78
- 2026-11-17: 77
- 2026-11-16: 77
- 2026-11-15: 76
- 2026-11-14: 76
- 2026-11-13: 75
- 2026-11-12: 75
- 2026-11-11: 36

## Common questions

### What is the Conduit Router — Governed MCP Routing server?

Conduit Router — Governed MCP Routing is listed in the public MCP registry as org.aimlds/conduit-router. Governed MCP routing: every agent call spend-capped, metered, sealed with a verifiable receipt. This page covers its hosted endpoint (https://router.pipavia.com/mcp).

### Is the Conduit Router — Governed MCP Routing server safe to use?

Conduit Router — Governed MCP Routing scores 79 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Conduit Router — Governed MCP Routing server expose?

Conduit Router — Governed MCP Routing exposes 6 tools: route_chat, list_models, get_usage, get_receipt, verify_receipt, get_policy. Their descriptions and schemas cost roughly 428 tokens of context every time the server is loaded.

### Does the Conduit Router — Governed MCP Routing server require authentication?

Yes. Conduit Router — Governed MCP Routing asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the Conduit Router — Governed MCP Routing server still maintained?

Conduit Router — Governed MCP Routing is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Conduit Router — Governed MCP Routing server?

VerifyMCP ran 13 checks on Conduit Router — Governed MCP Routing, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://router.pipavia.com/mcp
- Repository: https://github.com/nrupala/conduit-router-listing
- Website: https://router.pipavia.com/
- Changelog RSS feed: https://verifymcp.io/servers/org-aimlds-conduit-router/router.xml
- Changelog JSON feed: https://verifymcp.io/servers/org-aimlds-conduit-router/router/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/org-aimlds-conduit-router/router.json
- HTML version of this page: https://verifymcp.io/servers/org-aimlds-conduit-router/router
