{"id":"slzcdhd-1mcp","name":"1mcp","af_score":49.5,"security_score":34.0,"reliability_score":28.8,"what_it_does":"1mcp is a central proxy/hub that aggregates multiple upstream MCP servers and exposes a unified streamable-http MCP interface to downstream clients. It discovers upstream tools/resources/prompts, prefixes capability names (e.g., serverName___toolName), routes downstream requests to the correct upstream server, and supports dynamic hot-reloading of the upstream server configuration with live capability updates.","best_when":"You want an MCP “hub” that consolidates tools from multiple upstream MCP servers and you’re comfortable managing upstream connections through a local configuration file.","avoid_when":"You need a hosted SaaS with SLAs, explicit rate limiting, and documented security guarantees for external clients hitting the hub.","last_evaluated":"2026-04-04T21:23:33.857147+00:00","has_mcp":true,"has_api":false,"auth_methods":["None documented for the hub itself","Upstream servers may require auth via their own transport headers (e.g., SSE/streamable-http examples)"],"has_free_tier":false,"known_gotchas":["Capability names are prefixed with serverName___, so agents must use the prefixed name when calling through the hub.","Upstream reconnection and dynamic capability updates can change available capabilities during runtime.","Session management is described as having a 30-minute timeout/inactivity cleanup in places, but the README also contains an apparent inconsistency saying sessions persist indefinitely; agents should be prepared for session expiration/cleanup.","Dynamic config hot-reload may briefly invalidate/refresh capability mappings during changes.","Upstream servers that are unreachable will prevent certain capabilities from being routed successfully; agents should handle tool-not-found/connection errors."],"error_quality":0.0}