MCP Servers

Created By
decentralized-mcpa year ago
Overview

what is MCP Servers?

MCP Servers is a collection of decentralized servers designed to provide various functionalities such as calculations, weather data, keyword search, and more.

how to use MCP Servers?

To use MCP Servers, visit the respective README files for each server to understand their specific functionalities and how to interact with them.

key features of MCP Servers?

  • Multiple server functionalities including calculation, weather, keyword search, and data storage.
  • Decentralized architecture for enhanced reliability and performance.
  • Open-source and community-driven development.

use cases of MCP Servers?

  1. Performing complex calculations using the Gaia Calculator MCP Server.
  2. Accessing real-time weather data through the Gaia Weather MCP Server.
  3. Conducting keyword searches with the Gaia Keyword Search MCP Server.
  4. Utilizing data storage solutions with the Gaia TiDB MCP Server.

FAQ from MCP Servers?

  • What types of servers are included in MCP Servers?

MCP Servers include calculation, weather, keyword search, elastic search, and TiDB servers.

  • Are MCP Servers open-source?

Yes! MCP Servers are open-source and available for community contributions.

  • How can I contribute to MCP Servers?

You can contribute by visiting the GitHub repository and following the contribution guidelines.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
decentralized-mcp
Star
0
Language
Rust
License
-

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.

16 hours ago
Voyei

6 hours ago