XDC GOAT MCP Server

Created By
chainaimlabsa year ago
xdc-goat-mcp-server
Overview

what is XDC GOAT MCP Server?

XDC GOAT MCP Server is a comprehensive Model Context Protocol (MCP) server that provides blockchain services for the XDC Network and other EVM-compatible chains, enabling AI agents to interact with blockchain data.

how to use XDC GOAT MCP Server?

To use the server, clone the repository from GitHub, install the necessary dependencies, build the project, and run the server. Configuration for clients like Claude Desktop is also required.

key features of XDC GOAT MCP Server?

  • Multi-Chain Support for XDC Network and EVM-compatible networks
  • Wallet Management for various wallet providers
  • Token Operations including ERC20 and ERC721
  • NFT Minting with batch operations
  • DeFi Operations for token transfers and approvals
  • ENS Resolution for human-readable addresses
  • Real-time Data monitoring for balances and transactions

use cases of XDC GOAT MCP Server?

  1. Managing blockchain wallets and assets
  2. Minting and managing NFTs
  3. Performing DeFi operations like token transfers
  4. Interacting with multiple blockchain networks through a unified interface

FAQ from XDC GOAT MCP Server?

  • What is the primary function of the XDC GOAT MCP Server?

It serves as a bridge for AI agents to interact with blockchain data and perform various operations.

  • What are the prerequisites for installation?

You need Node.js, npm or yarn, and Git installed on your machine.

  • Can it support multiple blockchain networks?

Yes, it supports the XDC Network and other EVM-compatible networks.

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

17 hours ago
Voyei

7 hours ago