Borrowing it
Nothing to install: this file belongs to siriuslattice/stellarmcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/siriuslattice/stellarmcp/main/AGENTS.mdgit clone --depth 1 https://github.com/siriuslattice/stellarmcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/instructions/siriuslattice/stellarmcp/agents-md)<a href="https://agentmods.dev/instructions/siriuslattice/stellarmcp/agents-md"><img src="https://agentmods.dev/badge/instructions/siriuslattice/stellarmcp/agents-md.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00888 | $0.00888 |
| Opus 5 | $0.00444 | $0.00444 |
| Sonnet 5 | $0.00178 | $0.00178 |
| Haiku 4.5 | $0.00089 | $0.00089 |
Grade A, and why
stellarmcp AGENTS.md scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 7d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — StellarMCP
Agent Identity
- Name: StellarMCP
- Type: Data Merchant
- Version: 0.2.0
- Description: Sells Stellar blockchain data to AI agents via x402 micropayments
Capabilities
- Reads: Stellar accounts, transactions, payments, DEX orderbooks, trade aggregations, asset metadata, network status, ledger details, effects, offers, operations, liquidity pools, claimable balances, normalized prices, VWAP
- Prices: Multi-oracle aggregation (SdexOracle + ReflectorOracle) with median computation and per-source attribution (
sources[]in responses) - Transports: stdio, HTTP REST (x402-gated), MCP-over-HTTP at
/mcp(StreamableHTTPServerTransport, stateful sessions) - Writes: None (read-only)
- Settlement: x402 on Stellar (USDC)
Interfaces
MCP (stdio)
Full Model Context Protocol server with 16 tools. Connect via any MCP client.
{
"mcpServers": {
"stellarmcp": {
"command": "npx",
"args": ["stellar-mcp-x402"],
"env": {
"STELLAR_NETWORK": "testnet"
}
}
}
}
MCP-over-HTTP (remote)
Connect via HTTP at POST /mcp using the MCP StreamableHTTP transport. Stateful sessions via mcp-session-id header.
Example: An MCP client points to http://localhost:4021/mcp instead of stdio. All 16 tools are accessible — same instance as stdio.
HTTP REST (x402-gated)
Each tool exposed as a GET endpoint. Paid endpoints require x402 payment header.
| Endpoint | Price | Params |
|---|---|---|
| GET /tools/getAccount | $0.001 | accountId |
| GET /tools/getTransactions | $0.001 | accountId, limit? |
| GET /tools/getPayments | $0.001 | accountId, limit? |
| GET /tools/getOrderbook | $0.002 | sellingAsset, buyingAsset, limit? |
| GET /tools/getTradeAggregations | $0.002 | baseAsset, counterAsset, resolution?, limit? |
| GET /tools/getAssetInfo | $0.001 | assetCode, assetIssuer? |
| GET /tools/getNetworkStatus | free | — |
| GET /tools/getLedger | $0.001 | sequence? |
| GET /tools/getEffects | $0.001 | accountId, limit? |
| GET /tools/getOffers | $0.001 | accountId, limit? |
| GET /tools/getOperations | $0.001 | accountId, limit? |
| GET /tools/getLiquidityPools | $0.002 | account?, limit? |
| GET /tools/getClaimableBalances | $0.001 | claimant?, asset?, limit? |
| GET /tools/getPrice | $0.002 | baseAsset, counterAsset |
| GET /tools/getPriceHistory | $0.002 | baseAsset, counterAsset, resolution?, limit? |
| GET /tools/getVWAP | $0.002 | baseAsset, counterAsset, resolution?, limit? |
| GET /tools/getSorobanTokenInfo | $0.002 | contractId, accountId? |
| GET /pricing | free | — |
| GET /health | free | — |
| POST /mcp | free | MCP-over-HTTP JSON-RPC (StreamableHTTPServerTransport) |
| GET /mcp | free | SSE stream for server-initiated MCP messages |
| DELETE /mcp | free | Terminate MCP-over-HTTP session |
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 7d ago First seen · 78 lines · 888 tokens per session scan A 703fb407db04
stellarmcp AGENTS.md is an instructions file published in the GitHub repository siriuslattice/stellarmcp (0 stars, last pushed 5mo ago), licensed MIT. It adds 888 tokens to every session, about $0.0044 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.