Simple MCP Server Example

Created By
MCP-Mirrora year ago
Mirror of
Overview

what is Simple MCP Server Example?

This project is a basic implementation of a Model Context Protocol (MCP) server using FastAPI, designed to demonstrate the core concepts of MCP by providing a simple context service.

how to use Simple MCP Server Example?

To use the server, first install the required dependencies and then run the server using Uvicorn. You can interact with the server through its endpoints.

key features of Simple MCP Server Example?

  • Basic health check endpoint
  • Context endpoint that processes prompt templates
  • Support for parameterized prompts

use cases of Simple MCP Server Example?

  1. Providing context for various prompts in applications.
  2. Health monitoring of the server.
  3. Demonstrating the functionality of MCP in a simple setup.

FAQ from Simple MCP Server Example?

  • What is the purpose of the health check endpoint?

The health check endpoint is used to verify that the server is running and responsive.

  • How can I send a request to the context endpoint?

You can send a POST request to the /context endpoint with the required parameters in JSON format.

  • Is this server suitable for production use?

This example is primarily for educational purposes and may require additional features and security measures for production use.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
-
Language
-
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