TrustedRouter MCP Server
Connect coding agents to TrustedRouter's live model catalog, provider posture, credits, docs, and safe test inference over MCP.
Connect your agent
Remote MCPThe TrustedRouter MCP server gives coding agents live TrustedRouter context: models, prices, providers, credits, docs, generation metadata, and small test messages. Production apps should still call the API directly at https://api.trustedrouter.com/v1.
# Claude Code
claude mcp add --transport http trustedrouter https://trustedrouter.com/mcp \
--header "Authorization: Bearer $TRUSTEDROUTER_API_KEY"
# Generic MCP client
{
"mcpServers": {
"trustedrouter": {
"url": "https://trustedrouter.com/mcp",
"headers": {
"Authorization": "Bearer ${TRUSTEDROUTER_API_KEY}"
}
}
}
}
Public lookup tools work without a key. credits-get, generation-get, and chat-send require a normal sk-tr-... API key. chat-send is billable and capped to short test messages.
Tools
agent-readableAsk your agent
examples- Which TrustedRouter model should I use for cheap code review with ZDR?
- Show providers for
anthropic/claude-sonnet-5and their data policies. - Send a PONG smoke test through
trustedrouter/zdrand tell me the generation id. - Compare
trustedrouter/synth,trustedrouter/advisor, andtrustedrouter/subagent.
Privacy boundary
metadata firstMCP calls go to the control plane. Catalog, docs, providers, credits, and generation metadata never need prompt content. The only MCP tool that sends a prompt is chat-send, which forwards the short test message to the attested API gateway.
For application traffic, keep using the OpenAI-compatible API directly:
export OPENAI_BASE_URL="https://api.trustedrouter.com/v1"
export OPENAI_API_KEY="$TRUSTEDROUTER_API_KEY"