Test

Created By
chatmcpa year ago
test
Overview

what is MCP Directory?

MCP Directory is a directory for Awesome MCP Servers that allows users to find and manage various MCP servers.

how to use MCP Directory?

To use MCP Directory, clone the repository from GitHub, install the necessary dependencies, set up a database with Supabase, configure environment variables, and run the development server.

key features of MCP Directory?

  • Easy setup and installation process
  • Integration with Supabase for database management
  • Community support through Telegram and Discord channels

use cases of MCP Directory?

  1. Managing and organizing MCP servers for easy access
  2. Collaborating with other users in the MCP community
  3. Setting up a personal or public MCP server directory

FAQ from MCP Directory?

  • Is MCP Directory free to use?

Yes! MCP Directory is open-source and free to use for everyone.

  • What technologies does MCP Directory use?

MCP Directory uses Node.js and Supabase for backend services.

  • How can I contribute to MCP Directory?

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

Project Info
Created At
a year ago
Updated At
9 months ago
Author Name
chatmcp
Star
-
Language
-
License
-
Category

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.

37 minutes ago