mcp-server-collector MCP server

Created By
chatmcpa year ago
A MCP Server used to collect MCP Servers over the internet.
Overview

What is mcp-server-collector?

mcp-server-collector is a tool designed to collect MCP servers from the internet, allowing users to submit MCP servers into a centralized directory.

How to use mcp-server-collector?

To use mcp-server-collector, set up the required .env configuration file with the necessary API keys and endpoints, then utilize the provided tools to extract or submit MCP servers.

Key features of mcp-server-collector?

  • Extracts MCP servers from a specified URL or content.
  • Allows users to submit their MCP server to a directory like mcp.so.
  • Configurable through an .env file for seamless integration.

Use cases of mcp-server-collector?

  1. Collecting MCP servers for analysis and networking.
  2. Submitting new MCP servers to a public directory.
  3. Extracting MCP server data for research purposes.

FAQ from mcp-server-collector?

  • What is required to run mcp-server-collector?

Ensure you have the proper .env setup with API keys for OpenAI and the MCP server submit URL.

  • Is there community support available?

Yes, there are dedicated channels on Telegram and Discord for community support.

  • How can I publish my MCP server?

You can publish your MCP server by using the submit-mcp-server tool included in the collector.

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

Recommend Servers

View All
Payai X402 Tools

6 hours 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