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.

coverctl - Tool - OpenSmartRoute

Name: coverctl
Author: felixgeelhaar

Imported from the official MCP registry - entry io.github.felixgeelhaar/coverctl v1.16.0. Ratings and installs below are from this marketplace.

io.github.felixgeelhaar/coverctl

Go code coverage analysis tool with MCP server for AI-powered coverage workflows

Packages

mcpb: https://github.com/felixgeelhaar/coverctl/releases/download/v1.16.0/coverctl-mcp-darwin-arm64.mcpb
mcpb: https://github.com/felixgeelhaar/coverctl/releases/download/v1.16.0/coverctl-mcp-darwin-amd64.mcpb
mcpb: https://github.com/felixgeelhaar/coverctl/releases/download/v1.16.0/coverctl-mcp-linux-amd64.mcpb
mcpb: https://github.com/felixgeelhaar/coverctl/releases/download/v1.16.0/coverctl-mcp-linux-arm64.mcpb
mcpb: https://github.com/felixgeelhaar/coverctl/releases/download/v1.16.0/coverctl-mcp-windows-amd64.mcpb
mcpb: https://github.com/felixgeelhaar/coverctl/releases/download/v1.16.0/coverctl-mcp-windows-arm64.mcpb

Source: https://github.com/felixgeelhaar/coverctl

Registry entry: io.github.felixgeelhaar/coverctl

# after Install: the listing is in your workspace's routing pool - nothing else to configure curl -s -X POST https://api.opensmartroute.ai/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-felixgeelhaar-coverctl", ...}

Install coverctl 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.

coverctl

About

io.github.felixgeelhaar/coverctl

Packages

Use it

Install coverctl 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