MCP Collections

Created By
h4ck4lifea year ago
MCP servers collection
Overview

What is MCP Collections?

MCP Collections is a collection of tools and scripts designed to interact with various MCP servers, including YouTube, Reddit, and Mermaid diagrams.

How to use MCP Collections?

To use MCP Collections, clone the repository from GitHub, install the dependencies using npm, and configure the necessary API keys for the services you wish to use.

Key features of MCP Collections?

  • Integration with YouTube API for fetching video data.
  • Generation of Mermaid diagrams for visual representation.
  • Access to Reddit data through its API.
  • Headless browser functionality for web fetching.

Use cases of MCP Collections?

  1. Fetching and displaying YouTube video information.
  2. Creating visual diagrams using Mermaid.js.
  3. Accessing and analyzing Reddit posts and comments.
  4. Automating web data fetching tasks.

FAQ from MCP Collections?

  • What programming language is used in MCP Collections?

MCP Collections is built using TypeScript.

  • Do I need API keys to use this project?

Yes, you will need to configure API keys for services like YouTube and Reddit to access their data.

  • Is there any installation required?

Yes, you need to run npm install to install the necessary dependencies.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
h4ck4life
Star
0
Language
TypeScript
License
-

Recommend Servers

View All
Payai X402 Tools

8 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