Starknet MCP Server

Created By
MCP-Mirrora year ago
Mirror of
Overview

What is Starknet MCP Server?

Starknet MCP Server is a comprehensive Model Context Protocol (MCP) server designed for the Starknet blockchain, enabling AI agents to interact with Starknet networks, query blockchain data, manage wallets, and interact with smart contracts.

How to use Starknet MCP Server?

To use the Starknet MCP Server, you can run it directly using npx or install it globally. It can operate in two modes: stdio mode for CLI tools and HTTP mode for web applications.

Key features of Starknet MCP Server?

  • Full integration with Starknet blockchain using Starknet.js
  • Supports both Mainnet and Sepolia testnet
  • Resolution of Starknet IDs to addresses and vice versa
  • Native token support for ETH and STRK
  • Smart contract interaction capabilities
  • Designed for use with AI assistants like Claude and GPT

Use cases of Starknet MCP Server?

  1. Querying blockchain state such as balances and transactions.
  2. Interacting with smart contracts on the Starknet blockchain.
  3. Managing token transfers and NFT operations.
  4. Resolving Starknet IDs for user-friendly address management.

FAQ from Starknet MCP Server?

  • What networks does the server support?

    The server supports Starknet Mainnet and Sepolia testnet.

  • Is there a way to run the server without installation?

    Yes, you can use npx to run the server directly without installation.

  • Can I use this server with AI assistants?

    Yes, it is designed to be compatible with AI assistants like Claude and GPT.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
0
Language
TypeScript
License
MIT 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