MCP Server

Created By
zaki9501a year ago
Overview

what is MCP Server?

MCP Server is a Node.js server designed for interacting with the Monad Testnet blockchain network, providing a REST API interface for common blockchain operations.

how to use MCP Server?

To use MCP Server, clone the repository, install dependencies, configure environment variables, and start the server using npm or Docker.

key features of MCP Server?

  • Express.js REST API for blockchain operations
  • Web3.js integration for blockchain interaction
  • Security middleware (helmet, cors)
  • Swagger API documentation for easy access to API endpoints
  • Docker support for containerized deployment

use cases of MCP Server?

  1. Interacting with the Monad Testnet for blockchain development.
  2. Executing transactions and analyzing blockchain data.
  3. Building decentralized applications (dApps) that require blockchain connectivity.

FAQ from MCP Server?

  • What is the minimum Node.js version required?

Node.js version 16 or higher is required to run MCP Server.

  • Can I run MCP Server using Docker?

Yes! MCP Server supports Docker for easy deployment.

  • Where can I find the API documentation?

The API documentation is available at /api-docs when the server is running.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
zaki9501
Star
0
Language
JavaScript
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.

21 hours ago