MCP Servers Hub

Created By
MCP-Mirrora year ago
Mirror of
Overview

What is MCP Servers Hub?

MCP Servers Hub is a centralized repository that provides a comprehensive collection of Model Context Protocol (MCP) servers, facilitating seamless integration between LLM applications and external data sources.

How to use MCP Servers Hub?

Users can explore the MCP Servers Hub through its webpage, which is synced with the repository for the latest updates. The webpage offers interactive browsing, search, and sorting options for easy navigation.

Key features of MCP Servers Hub?

  • Extensive catalog of open-source and proprietary MCP servers.
  • Detailed documentation links and contributor information for each server.
  • User-friendly interface for searching and sorting servers.

Use cases of MCP Servers Hub?

  1. Integrating LLMs with various data sources and tools.
  2. Facilitating AI-powered applications in diverse domains such as finance, healthcare, and education.
  3. Enabling developers to quickly find and implement MCP servers for their projects.

FAQ from MCP Servers Hub?

  • What is the Model Context Protocol (MCP)?

MCP is an open protocol that allows LLM applications to connect with external data sources and tools seamlessly.

  • How can I contribute to the MCP Servers Hub?

Contributions can be made by submitting new MCP servers or improving existing ones through pull requests on the GitHub repository.

  • Is there a community for MCP users?

Yes! You can join the Reddit r/mcp and the Discord Server for discussions and support.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
-
Language
-
License
-

Recommend Servers

View All
Voyei

6 hours 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.

16 hours ago