"Multi MCP (Model Context Protocol) implementation or management" matching MCP servers:

Local MCP server that lets Claude Code delegate bounded, read-only tasks to external AI models (Codex, Grok, local OpenAI-compatible servers) via CLIProxyAPI.

An MCP server that exposes tools for sub-agent style reasoning across multiple LLM providers, enabling delegation of prompts to various models and running critique loops, debates, red-teaming, and answer ranking.

A local, read-only MCP server (plus CLI) over your own stock/ETF transaction log. A deterministic core computes drawdown-first risk with bootstrap confidence intervals and validates targets with walk-forward verdicts. The assistant narrates, but the number fence makes it structurally impossible for the model to produce a figure.

Autonomous DeFi yield for AI agents on Base. Query APY rates, agent status, payment splits, and referral stats. 4 read-only tools + 1 resource.

An MCP server that seats multiple LLMs as a council, letting your assistant query them in parallel or in sequence, relay answers for cross-critique, and merge conclusions within one conversation.

MCP server that pings 130+ free coding LLM models across 17 providers in real-time, ranks them by latency, and helps AI agents pick the fastest available model.

Discovers local model runtimes such as Ollama, LM Studio, and LocalAI, and exposes their endpoint metadata to MCP clients like Copilot.

Trust, identity, and reputation infrastructure for AI agents. Register agents with W3C DID (Ed25519), check EigenTrust reputation scores, submit peer attestations, search agents by capability, and verify IPFS-anchored audit trails. 11 tools.

Trust infrastructure for the agent economy.

An MCP server that provides AI trading agents with persistent, outcome-weighted memory to learn from historical performance and detect behavioral biases. It enables agents to automatically adjust strategies and optimize position sizing based on context-aware recall of past trade outcomes.

Security-enforcing MCP proxy that sits between an AI agent and any number of downstream MCP servers, intercepting every tool call through a capability-token policy gateway that can allow, deny, or escalate to human approval before the call reaches any real tool. It also exposes built-in operator tools for approval workflows, audit trail queries, token management, voice/HUD output, and hierarchical

Connects to wetlab protocol resources such as protocols.io, enabling users to access and manage experimental protocols via natural language.

Exposes employee leave-management operations (add employees, check balance, apply/cancel leave, view history) as MCP tools for AI clients like Claude Desktop to call directly.

Enables AI assistants to directly manage Anki flashcards, decks, notetypes, tags, and media, with support for batch operations, searches, and deck exports via file-based input/output.

A comprehensive MCP server for managing AI-assisted Dungeons & Dragons campaigns, featuring tools for character sheets, combat tracking, and world-building. It enables players and DMs to interact with 5e game mechanics and query personal PDF rulebooks using RAG capabilities.

A flexible proxy server that aggregates multiple backend MCP servers into a single interface using STDIO or SSE transports. It supports dynamic server management via an HTTP API and utilizes namespacing to prevent tool conflicts across connected services.

An MCP server that turns the Hugging Face Hub into a conversational model picker with a tool-use eval harness to prove the agent actually uses it correctly.

An MCP server that keeps raw tool output out of the context window by sandboxing and compressing results (about 98% reduction), persisting file edits, git operations, tasks and decisions in SQLite with BM25 retrieval so the agent resumes after compaction, and enforcing routing across 17 platforms via MCP and hooks. It also encourages the model to write scripts that compute answers and log only results instead of reading large data into context.

Multi-modal RAG engine for AI assistants. Stores conversation history, conclusions, diffs, error traces, and other development artifacts in LanceDB with vector search, multi-factor scoring, and an LLM-driven consolidation pipeline.

Evaluates task suitability for local models before cloud API calls, routing to Ollama or similar to reduce costs.