@lobstack/mcp
OfficialRelated Servers
Alternatives to @lobstack/mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to browse a live catalog of 100+ models with pricing, rankings and measured uptime, check credits and spend, and send chat completions through an OAuth-authenticated, per-connection key capped by a spend limit. Read tools are free, and paid calls are priced and approved before any credit is used.MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to browse and compare model catalogs, pick models by budget or context window, and run completions metered to the caller's own API key.MIT
- AlicenseAqualityFmaintenanceMCP server for ProxyLLM, the OpenAI-compatible LLM gateway, enabling live model catalogs, plan-savings calculations, routing key management, and autonomous account signup.976 npmMIT
- AlicenseAqualityAmaintenanceCentralized encrypted gateway that routes requests to 11+ LLM providers (API keys and CLI subscriptions) through a single OpenAI-compatible endpoint, with MCP tools for vault operations, code search, and shared state.309 npm2MIT
- AlicenseAqualityBmaintenanceEnables any AI agent to connect to any OpenAI-compatible LLM provider through a unified MCP interface, with automatic failover, caching, cost tracking, and multi-model consensus.13MIT
- FlicenseNot gradedqualityCmaintenanceProvides a stateless MCP gateway that lets AI agents execute Python in an isolated AST sandbox, run guarded read-only SQL queries, and automatically route tasks to cheaper or more capable models.-
TDQS
Scored across 4 tools
Each tool targets a clearly distinct concern: route_preview scores/routes without spending, models lists the catalog, chat performs the actual paid call, and spend reports usage. The overlap risk between route_preview and chat is explicitly resolved by descriptions clarifying one runs no inference while the other spends money.
All tools share a consistent 'lobstack_' prefix and are snake_case, so they scan as one family. Suffix styles vary though — route_preview is verb_noun while models, chat and spend are bare nouns/verbs — a minor inconsistency but still readable and predictable.
Four tools is on the lean side but each earns its place and maps to a real workflow stage (discover, preview, execute, audit). Slightly thin, though appropriate for a focused gateway server.
The surface covers the core lifecycle: model discovery, routing/cost preview, the paid completion call, and spend auditing. Minor gaps exist (e.g. no embeddings, streaming controls, or key/scope management), but agents can accomplish the primary gateway tasks without dead ends.