StellarExpert MCP

Model Context Protocol server for the StellarExpert Open API (v1.4.0). It exposes Directory, Asset Info, and Ledger helper endpoints as tools so Cursor, Claude, and other MCP hosts can query the same public data your product documents.

The Open API is public, unauthenticated, and CORS-enabled. This server only wraps documented Open API routes — not undocumented explorer UI endpoints.

Upstream: https://api.stellar.expert
Docs: https://stellar.expert/openapi
Data license on the Open API: MIT

Tools

Resource: stellar-expert://docs
Prompts: check-address-safety, lookup-asset

network is public or testnet (default public, or STELLAR_EXPERT_NETWORK).

Related MCP server: Polymarket MCP

Rate limits

StellarExpert may return HTTP 429. The MCP surfaces that as a tool error and asks the model to cache or batch queries. For heavy client usage, cache on your side.

Requests send User-Agent: stellar-expert-mcp/0.1.0.

Requirements

• Node.js 20+

Install (from a clone)

npm install
npm run build

Local stdio (until published to npm)

Cursor — project .cursor/mcp.json or ~/.cursor/mcp.json:

{
  "mcpServers": {
    "stellar-expert": {
      "command": "npx",
      "args": ["tsx", "/ABS/PATH/TO/stellar-expert-mcp/src/stdio.ts"]
    }
  }
}

Or after npm run build:

{
  "mcpServers": {
    "stellar-expert": {
      "command": "node",
      "args": ["/ABS/PATH/TO/stellar-expert-mcp/dist/stdio.js"]
    }
  }
}

After npm publish

{
  "mcpServers": {
    "stellar-expert": {
      "command": "npx",
      "args": ["-y", "stellar-expert-mcp"]
    }
  }
}

Claude Desktop / Claude Code (stdio)

{
  "mcpServers": {
    "stellar-expert": {
      "command": "npx",
      "args": ["tsx", "/ABS/PATH/TO/stellar-expert-mcp/src/stdio.ts"]
    }
  }
}

MCP Inspector

npm run inspector

Equivalent: npx @modelcontextprotocol/inspector npx tsx src/stdio.ts

Remote HTTP (clients)

Same createServer() factory over Streamable HTTP at /mcp.

npm run start:http

Defaults: http://127.0.0.1:3000/mcp. Health: GET /health.

Cursor remote config:

{
  "mcpServers": {
    "stellar-expert": {
      "url": "https://YOUR_HOST/mcp"
    }
  }
}

Smoke test:

curl -s -X POST http://127.0.0.1:3000/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

This v1 ships a Node process (npm run start:http). Host it on Fly, a VM, or similar; do not bind 0.0.0.0 without ALLOWED_HOSTS / a proxy.

Publishing to npm

npm is deprecating 2FA-bypass granular access tokens for account/package management (already in effect) and for direct publish (targeted January 2027). This repo does not use a long-lived NPM_TOKEN. Releases go through trusted publishing (OIDC).

First publish (the package does not exist yet — trusted publishers can only be attached after it does).

npm login --auth-type=web only signs you in. It is not package-publish 2FA. npm now requires account 2FA (or a bypass-2FA token, which we are not using) for every new package. --auth-type=web on npm publish will not open a second browser prompt if you are already logged in.

1. Enable 2FA on the npm account (not GitHub): Two-Factor Authentication — authenticator app, auth-and-writes.

2. Then, from this repo, use the 6-digit npm code (refreshes every 30s):

npm publish --access public --otp=123456

npx stellar-expert-mcp returning 404 is expected until this first publish succeeds.

Then on npmjs.com → stellar-expert-mcp → Settings → Trusted Publisher:

• Organization or user: Bran18

• Repository: stellar-expert-mcp

• Workflow filename: publish.yml

• Allow npm publish (and/or npm stage publish)

Later versions: bump version in package.json, commit, tag, push:

git tag v0.1.1
git push origin v0.1.1

.github/workflows/publish.yml publishes from GitHub-hosted runners with id-token: write. No bypass-2FA token.

Provenance attestations require a public GitHub repo. This repository is private, so npm will publish without provenance until you change visibility.

Development

npm start          # stdio
npm run start:http
npm run typecheck
npm run verify     # live Open API + in-process MCP handler

Attribution

API data and schema: StellarExpert. This MCP is a DevRel wrapper around the public Open API; it is not a substitute for on-chain source of truth (Horizon / RPC). Asset ratings are technical activity scores, not investment advice.