MCP Server

Created By
khaosansa year ago
Overview

What is MCP Server?

MCP Server is a FastAPI-based server that provides WebSocket communication, file management, and tools endpoints for developers.

How to use MCP Server?

To use MCP Server, clone the repository, set up a virtual environment, install dependencies, and run the server using Uvicorn.

Key features of MCP Server?

  • File Management API for handling files
  • WebSocket Communication for real-time interactions
  • Tools Endpoint for executing various tools
  • Static File Serving for serving files over HTTP
  • Comprehensive Test Suite for ensuring functionality

Use cases of MCP Server?

  1. Building real-time applications with WebSocket support
  2. Managing files through a RESTful API
  3. Executing tools for data processing or summarization

FAQ from MCP Server?

  • What programming language is MCP Server built with?

MCP Server is built using Python and the FastAPI framework.

  • Is MCP Server free to use?

Yes! MCP Server is open-source and available under the MIT License.

  • How can I contribute to MCP Server?

You can contribute by submitting issues or pull requests on the GitHub repository.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
khaosans
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