Skip to content
Model Context Protocol
- Model Context Protocol - The specification itself; the source of truth for what a compliant client, server, and transport must do.
- MCP Registry - Official, community-owned registry service for publishing and discovering MCP servers; still in preview.
- ToolHive - Runs MCP servers in containers with permission policies, secrets handling, and audit logging, and its proxy exports OpenTelemetry traces and metrics for each MCP request with MCP semantic-convention attributes such as
mcp.method.name.
- MCPJungle - Self-hosted registry and single gateway endpoint for the MCP servers an organisation runs, exposing Prometheus metrics through OpenTelemetry but documenting no traces.
- MCP Context Forge - Gateway and registry that federates MCP servers and REST APIs behind one endpoint, with auth, plugins, and a
tool.invoke OpenTelemetry span per tool call; Apache-2.0.
- Docker MCP Gateway - Docker CLI plugin that fronts multiple MCP servers behind one gateway with container isolation, and starts an
mcp.tool.call OpenTelemetry span per tool call on the Docker CLI’s tracer provider, which its code does; its README mentions call tracing but not OpenTelemetry.
- Aident Loadout - Proprietary hosted service, with an MIT-licensed client skill, that gives agents a CLI and MCP endpoint for actions on connected apps, with vault-held credentials, a pre-run cost estimate, and an audit of recent actions with status and, where applicable, cost.