MCP Servers Collection

Created By
XyAgenta year ago
Overview

What is MCP Servers Collection?

MCP Servers Collection is a repository that hosts a collection of Model Context Protocol (MCP) servers, each providing specific functionality through a standardized interface, implemented in Python with Server-Sent Events (SSE) transport.

How to use MCP Servers Collection?

To use the MCP Servers Collection, clone the repository from GitHub, and follow the provided guidelines to create new servers based on the template server. Each server can be run independently with its own configuration.

Key features of MCP Servers Collection?

  • Standardized implementation across all servers
  • Built with Python 3.12+ and modern language features
  • Exclusively uses Server-Sent Events for communication
  • Modular design for self-contained server modules
  • Consistent documentation structure
  • Docker support for containerization

Use cases of MCP Servers Collection?

  1. Creating custom MCP servers for various functionalities.
  2. Utilizing the YouTube server for video search and transcript retrieval.
  3. Developing educational tools or services using the template server.

FAQ from MCP Servers Collection?

  • Can I contribute new servers to the collection?

Yes! Contributions are welcome, and you can start by using the template server.

  • What are the requirements to run the servers?

All servers require Python 3.12+ and optionally Docker for containerization.

  • Is there documentation available for each server?

Yes, each server follows a standardized README structure for documentation.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
XyAgent
Star
0
Language
Python
License
MIT license

Recommend Servers

View All
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.

8 hours ago