Model Context Protocol servers

Created By
thanhvinh199700a year ago
Overview

What is MCP-SERVER?

MCP-SERVER is a repository containing reference implementations for the Model Context Protocol (MCP), showcasing how it can be utilized to provide Large Language Models (LLMs) with secure and controlled access to various tools and data sources.

How to use MCP-SERVER?

To use MCP-SERVER, you can run the servers directly using npx for TypeScript-based servers or uvx/pip for Python-based servers. Configuration examples for integrating with clients like Claude Desktop are also provided in the documentation.

Key features of MCP-SERVER?

  • A collection of reference implementations for MCP.
  • Support for both TypeScript and Python SDKs.
  • Demonstrates various integrations with third-party services like AWS, Google Drive, and more.
  • Community-driven with a growing set of servers for diverse applications.

Use cases of MCP-SERVER?

  1. Enabling LLMs to interact with cloud services like AWS and Google Drive.
  2. Facilitating secure file operations and database interactions.
  3. Providing a framework for building custom MCP servers.

FAQ from MCP-SERVER?

  • What is the Model Context Protocol?

The Model Context Protocol is a framework that allows LLMs to access tools and data securely and efficiently.

  • Is MCP-SERVER free to use?

Yes! MCP-SERVER is open-source and free to use under the MIT License.

  • How can I contribute to MCP-SERVER?

Contributions are welcome! Please refer to the contributing guidelines in the repository.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
thanhvinh199700
Star
0
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.

a day ago