MCP (Model Context Protocol) client, bridge, and dispatcher.

Three layers:

• [client] — minimal JSON-RPC 2.0 client over stdio or HTTP
• [bridge] — fleet of connected peers, tool cache, call routing
• [handler] / [dispatch] — config-driven load, port-file discovery, meta-tool dispatch

Features

Pick exactly one HTTP backend and one TLS backend:

• hyper (default) / reqwest
• native-tls (default) / rustls

The hyper backend is more compact — it skips reqwest's cookie store, redirect logic, and decoders that MCP never uses.