# io.github.jdhart81/wu-wei-router (remote · mcp.viridisconservation.com)

Plan agent workload routes from evaluation and cost data. $1 USDC per plan; modeled savings only.

- Trust score: 60/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `mcp.viridisconservation.com`: 60/100 (this document), [markdown](https://verifymcp.io/servers/jdhart81-wu-wei-router/wu-wei-router-mcp.md), [page](https://verifymcp.io/servers/jdhart81-wu-wei-router/wu-wei-router-mcp)

## Channel facts

- Endpoint: `https://mcp.viridisconservation.com/wu-wei-router/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## 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-09-20.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 2 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 51/100
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 86 tokens (~43/item across 2 items; 2 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 20/100
  - Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the io.github.jdhart81/wu-wei-router MCP server?

io.github.jdhart81/wu-wei-router is a hosted endpoint at https://mcp.viridisconservation.com/wu-wei-router/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 jdhart81-wu-wei-router 'https://mcp.viridisconservation.com/wu-wei-router/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "jdhart81-wu-wei-router": {
      "url": "https://mcp.viridisconservation.com/wu-wei-router/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "jdhart81-wu-wei-router": {
      "type": "http",
      "url": "https://mcp.viridisconservation.com/wu-wei-router/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.jdhart81-wu-wei-router]
url = "https://mcp.viridisconservation.com/wu-wei-router/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "jdhart81-wu-wei-router": {
      "type": "remote",
      "url": "https://mcp.viridisconservation.com/wu-wei-router/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add jdhart81-wu-wei-router --url 'https://mcp.viridisconservation.com/wu-wei-router/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  jdhart81-wu-wei-router:
    url: "https://mcp.viridisconservation.com/wu-wei-router/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "jdhart81-wu-wei-router": {
      "Transport": "http",
      "Url": "https://mcp.viridisconservation.com/wu-wei-router/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add jdhart81-wu-wei-router -t streamable-http -u 'https://mcp.viridisconservation.com/wu-wei-router/mcp'
```

### Other

```json
{
  "mcpServers": {
    "jdhart81-wu-wei-router": {
      "type": "http",
      "url": "https://mcp.viridisconservation.com/wu-wei-router/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-09-19 (score 60, +1)

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

### 2026-09-16 (score 59, +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-09-15 (score 58, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-14 (score 58)

First indexed and scored.

## MCP tools (2)

### `plan_workload` (~72 tokens)

$1 workload routing plan from declared costs and representative evaluation counts.

    Up to 20 profiles and 50 task groups. Inspect the public service schema and a free
    unpaid quote first. Does not execute tasks or establish actual savings.

Input parameters:

- `profiles` (array, required)
- `tasks` (array, required)

Output parameters:

- `result` (string)

### `describe_agent` (~14 tokens)

Free scope and price discovery.

Output parameters:

- `result` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/jdhart81-wu-wei-router/wu-wei-router-mcp#diagnostics

## Score history

- 2026-09-20: 60
- 2026-09-19: 60
- 2026-09-18: 59
- 2026-09-17: 59
- 2026-09-16: 59
- 2026-09-15: 58
- 2026-09-14: 58

## Common questions

### What is the io.github.jdhart81/wu-wei-router MCP server?

io.github.jdhart81/wu-wei-router is an MCP server listed in the public MCP registry as io.github.jdhart81/wu-wei-router. Plan agent workload routes from evaluation and cost data. $1 USDC per plan; modeled savings only. This page covers its hosted endpoint (https://mcp.viridisconservation.com/wu-wei-router/mcp).

### Is the io.github.jdhart81/wu-wei-router MCP server safe to use?

io.github.jdhart81/wu-wei-router scores 60 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 io.github.jdhart81/wu-wei-router MCP server expose?

io.github.jdhart81/wu-wei-router exposes 2 tools: plan_workload, describe_agent. Their descriptions and schemas cost roughly 86 tokens of context every time the server is loaded.

### Does the io.github.jdhart81/wu-wei-router MCP server require authentication?

No. We connected to io.github.jdhart81/wu-wei-router without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the io.github.jdhart81/wu-wei-router MCP server still maintained?

io.github.jdhart81/wu-wei-router is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.viridisconservation.com/wu-wei-router/mcp
- Repository: https://github.com/jdhart81/viridis-agent-fleet
- Changelog RSS feed: https://verifymcp.io/servers/jdhart81-wu-wei-router/wu-wei-router-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/jdhart81-wu-wei-router/wu-wei-router-mcp.json
- HTML version of this page: https://verifymcp.io/servers/jdhart81-wu-wei-router/wu-wei-router-mcp