MCP Hub

Created By
ravitemera year ago
A centralized manager for Model Context Protocol (MCP) servers with dynamic server management and monitoring
Overview

what is MCP Hub?

MCP Hub is a centralized manager for Model Context Protocol (MCP) servers that facilitates dynamic server management and monitoring.

how to use MCP Hub?

To use MCP Hub, install it via npm and start the hub server with a specified configuration file. The server will manage multiple MCP servers and provide a unified API for client interactions.

key features of MCP Hub?

  • Dynamic management and monitoring of MCP servers
  • REST API for executing tools and accessing resources
  • Real-time server status tracking and client connection management
  • Comprehensive error handling and logging

use cases of MCP Hub?

  1. Managing multiple MCP servers in a development environment
  2. Monitoring server health and performance in real-time
  3. Facilitating client-server interactions through a unified API

FAQ from MCP Hub?

  • What is the purpose of MCP Hub?

MCP Hub serves as a central management point for multiple MCP servers, allowing for efficient monitoring and resource management.

  • How do I install MCP Hub?

You can install MCP Hub using npm with the command npm install -g mcp-hub.

  • Can MCP Hub manage any MCP server?

Yes, MCP Hub can manage any server that adheres to the Model Context Protocol.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
ravitemer
Star
131
Language
JavaScript
License
MIT license

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

5 hours ago