ton-mcp

Created By
kriuchkova year ago
This MCP Server allows you to interact with the TON Blockchain
Overview

What is ton-mcp?

ton-mcp is a Model Context Protocol (MCP) Server that allows users to interact with the TON Blockchain, enabling operations such as sending transactions and checking balances through their Ton wallet.

How to use ton-mcp?

To use ton-mcp, you need to add a server entry to your configuration file and run the server using the specified command. Detailed instructions can be found in the repository documentation.

Key features of ton-mcp?

  • Seamless interaction with the TON Blockchain.
  • Ability to send transactions and check wallet balances.
  • Integration with LLM applications through the Model Context Protocol.

Use cases of ton-mcp?

  1. Managing cryptocurrency transactions on the TON Blockchain.
  2. Integrating AI applications with blockchain data.
  3. Enhancing chat interfaces with blockchain capabilities.

FAQ from ton-mcp?

  • What is the Model Context Protocol (MCP)?

MCP is an open protocol that facilitates integration between LLM applications and external data sources.

  • Is ton-mcp free to use?

Yes! ton-mcp is open-source and available for anyone to use.

  • What programming language is ton-mcp written in?

ton-mcp is written in TypeScript.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
kriuchkov
Star
0
Language
TypeScript
License
MIT license
Tags

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.

13 hours ago