How long does the integration take?

Change one base URL in an OpenAI-compatible client, or install the Python or TypeScript SDK; the quickstart routes a first request in a few minutes.

Will this lock us into another vendor?

No. The router is Apache-2.0 open source, your provider keys stay yours, and the API is OpenAI-compatible, so leaving is a change of base URL.

What happens when a provider fails?

The router falls back to the next model your policy allows and records the fallback in the trace, so an outage costs a retry, not an incident.

90 days of the enterprise, pro and team plans free, no card needed. See the plans

OpenSmartRoute

LEGION Verify: MCP tool-list history - Tool - OpenSmartRoute

Toolv1.3.0

LEGION Verify: MCP tool-list history

Name: LEGION Verify: MCP tool-list history
Author: Legion33shadow

Check if an MCP server changed its tools: signed history, per-server coverage, offline proofs.

by Legion33shadow(0) 0 installs

Free

Free account. Installing gives you the manifest plus copy-paste snippets.

See reviews

About

Imported from the official MCP registry - entry io.github.Legion33shadow/legion-verify v1.3.0. Ratings and installs below are from this marketplace.

LEGION Verify: MCP tool-list history

Check if an MCP server changed its tools: signed history, per-server coverage, offline proofs.

Remote endpoints

streamable-http https://mcp.legion-api.com/mcp

Source: https://github.com/Legion33shadow/legion-mcp

Registry entry: io.github.Legion33shadow/legion-verify

Use it

Copy one of these into your project. Installing also returns the manifest and these snippets.

# after Install: the listing is in your workspace's routing pool - nothing else to configure
curl -s -X POST https://osr-api.kindrock-caaab1a2.centralindia.azurecontainerapps.io/api/v1/route -H 'Authorization: Bearer $OSR_API_KEY' -H 'Content-Type: application/json' -d '{"text": "...", "plan": true}'
# or pin it on the OpenAI-compatible endpoint: {"model": "mcp-io-github-legion33shadow-legion-verify", ...}

Installed into a catalogue, chosen by a router

Install LEGION Verify: MCP tool-list history and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

Photo: RDNE Stock project

For the business

What it costs to adopt - in engineering time.

Same client, same code
One base URL
The OpenAI-compatible endpoint answers your existing SDK calls; model=auto lets the router choose.
The SDKs
One URL, every vendor
No vendor lock-in
Point your OpenAI-compatible client at one address; add, swap or retire providers in the catalogue without touching application code.
Every vendor side by side
Next eligible model answers
Failover built in
When a provider is down or over quota the request moves on; the trace says it did.

Manifest

An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.

mcp-io-github-legion33shadow-legion-verify.ocm.jsonjson

{
  "ocm": "1",
  "id": "mcp-io-github-legion33shadow-legion-verify",
  "kind": "tool",
  "name": "LEGION Verify: MCP tool-list history",
  "description": "Check if an MCP server changed its tools: signed history, per-server coverage, offline proofs.",
  "publisher": "Legion33shadow",
  "version": "1.3.0",
  "capabilities": {
    "domains": [
      "coding"
    ],
    "tags": [
      "mcp",
      "mcp-server",
      "mcp-registry"
    ],
    "languages": [
      "en"
    ],
    "supports_tools": true
  },
  "quality_prior": 0.6,
  "examples": [
    "Check if an MCP server changed its tools: signed history, per-server coverage, offline proofs."
  ],
  "primary": false,
  "metadata": {
    "source": {
      "provider": "mcp-registry",
      "repository": "https://github.com/Legion33shadow/legion-mcp",
      "path": "server.json",
      "ref": "1.3.0",
      "url": "https://github.com/Legion33shadow/legion-mcp",
      "key": "io.github.Legion33shadow/legion-verify",
      "registry": "https://registry.modelcontextprotocol.io"
    }
  },
  "endpoints": [
    {
      "protocol": "mcp",
      "url": "https://mcp.legion-api.com/mcp"
    }
  ]
}

Fetch it by URL: GET /api/v1/registry/mcp-io-github-legion33shadow-legion-verify/manifest?version=1.3.0

About

LEGION Verify: MCP tool-list history

Remote endpoints

Use it

Install LEGION Verify: MCP tool-list history and it becomes one more candidate the router can pick - when it fits.

What it costs to adopt - in engineering time.

One base URL

No vendor lock-in

Failover built in

Manifest

Reviews