Simple MCP Servers

Created By
Jython1415a year ago
Repo for holding my MCP servers
Overview

what is Simple MCP Servers?

Simple MCP Servers is a repository that contains self-contained, single-file Model Context Protocol (MCP) servers written in Python, designed for easy integration into MCP-compatible applications.

how to use Simple MCP Servers?

To use the servers, ensure you have Python >= 3.11 and the uv package manager installed. You can run each server directly or through the uv command.

key features of Simple MCP Servers?

  • Self-contained scripts that are easy to execute
  • PEP 723 compliance for inline dependency management
  • Direct execution capabilities with uv
  • No setup required for dependencies

use cases of Simple MCP Servers?

  1. Converting URLs for integration with Bluesky tools
  2. Efficiently reading large files in chunks
  3. Validating Scrabble words using a complete word list

FAQ from Simple MCP Servers?

  • What is PEP 723?

PEP 723 is a Python Enhancement Proposal that allows inline script metadata for managing dependencies.

  • Do I need to install dependencies manually?

No, dependencies are automatically handled at runtime by the uv package manager.

  • Can I create my own MCP server?

Yes! Follow the provided guidelines in the repository to create a new MCP server.

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