MCP Server Directory

Created By
ankittyagi140a year ago
Discover and share Model Context Protocol Servers for AI applications, development, and integration.
Overview

what is MCP Server Directory?

MCP Server Directory is a comprehensive application designed for browsing and managing Minecraft Protocol (MCP) servers, allowing users to search, filter, and submit server listings.

how to use MCP Server Directory?

To use the MCP Server Directory, clone the repository, install the necessary dependencies, set up your Supabase environment, and run the development server to access the application in your browser.

key features of MCP Server Directory?

  • Server Listings: Explore detailed information about various MCP servers.
  • Search & Filter: Easily find servers based on tags, features, or keywords.
  • Server Detail Page: Access comprehensive information for each server.
  • Submission Form: Submit your own MCP servers for inclusion in the directory.
  • Admin Review: A moderation system to review and approve server submissions.

use cases of MCP Server Directory?

  1. Finding new Minecraft servers to join.
  2. Submitting personal Minecraft servers for others to discover.
  3. Browsing server features to choose the best fit for gameplay.

FAQ from MCP Server Directory?

  • How do I submit my own server?

You can submit your server using the submission form available in the application.

  • Is there a moderation process for submitted servers?

Yes, all submitted servers go through an admin review process before being listed.

  • What technologies are used in this project?

The project uses Next.js, Supabase, Tailwind CSS, and other modern web technologies.

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