In-depth architectural comparison of the Llm Prices Cn and Orcarouter MCP Server MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Llm Prices Cn
Aggregators · Remote HTTP/SSE
Quality: 49/100 (Fair) | Auth: No auth required
Orcarouter MCP Server
Aggregators · Local stdio
Quality: 63/100 (Good) | Auth: API Key required
Verdict Summary: Choose Llm Prices Cn if you need specialized Aggregators tools running via a hosted cloud SSE transport. Choose Orcarouter MCP Server if your workspace requires Aggregators integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Llm Prices Cn when:
You need dedicated capabilities in the Aggregators domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: Daily-verified pricing for 44 LLM models, USD and CNY input/output prices per million tokens, Hosted MCP tools for price queries and cost estimation.
Llm Prices Cn is categorized under Aggregators and uses a remote streaming HTTP/SSE transport. In contrast, Orcarouter MCP Server belongs to Aggregators using local stdio subprocess. Select Llm Prices Cn when you need capabilities focused on aggregators and Orcarouter MCP Server when you require tools for aggregators.
Send a single-turn chat request to OrcaRouter and return the assistant's response text. Default model is the workspace's auto-router. Use `orcarouter/<name>` for other routers or `<provider>/<model>` for direct calls. For OpenAI reasoning models (gpt-5/o1/o3/...), max_tokens is automatically routed to max_completion_tokens at the wire level. The optional `models` array sets a fallback chain — the primary `model` is tried first, then each entry on failure (5 entries total max, including the primary). Errors are returned as text content with isError:true; common cases include missing API key, rate limits, and upstream provider outages. Requires ORCAROUTER_API_KEY.
orcarouter_models_list
List LLM models in the OrcaRouter catalog. Each entry includes id, name, description, owned_by, context_length, supported_endpoint_types, and pricing (both per-token and per-million tokens). Filter by `provider`, `capability`, or `min_context` — filters compose (all conditions must match) and are applied server-side. Discover valid provider ids first with orcarouter_providers_list. Returns the full catalog when called without filters. Read-only, no API key required.
orcarouter_model_card
Get detailed information about a single model — display name, long description, pricing (per-call and per-million tokens), context window, max output, modalities (input/output), supported endpoints, latency percentiles (p50/p95), and release date. Use this when you already know the model id and want full details; for browsing or filtering across many models use orcarouter_models_list instead. Returns isError:true with a clear hint when the id is not found. Read-only, no API key required.
orcarouter_providers_list
List all model providers on OrcaRouter with their `provider_id`, human-readable `display_name`, `icon_url`, and `model_count`. Call this first to discover valid provider ids (e.g. 'openai', 'anthropic', 'google', 'qwen', 'deepseek') which you can then pass to orcarouter_models_list as the `provider` filter. Takes no parameters and returns the same list on every call until the deployment's catalog changes. Read-only, no API key required.
Daily-verified LLM API pricing dataset (44+ models, CN & global) with a hosted MCP server for live price queries and token cost estimation.
Browse 160+ LLM models (OpenAI, Anthropic, Google, Qwen, DeepSeek, …) with live pricing — no API key required for catalog tools. Routes chat completions through the OrcaRouter gateway with automatic fallback. npx -y @orcarouter/mcp.