StellarMCP (siriuslattice/stellarmcp) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 17 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Emerging
74/100
2 months ago

StellarMCP

MCP server giving AI agents access to Stellar blockchain data with monetized tool calls via x402 micropayments.

→ siriuslattice/stellarmcp· listed on glama

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

siriuslattice

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

Glama

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
🚨
Known vulnerabilities in dependencies: 2 critical
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
🔐
You'll be asked for 2 credentials: OZ_API_KEY, STELLAR_SECRET_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// known CVEs in dependencies2 critical1 low

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

criticalvitest@3.0.0GHSA-5xrq-8626-4rwp

When Vitest UI server is listening, arbitrary file can be read and executed

criticalvitest@3.0.0GHSA-9crc-q9x8-hgqq

Vitest allows Remote Code Execution when accessing a malicious website while Vitest API server is listening

lowtsup@8.0.0GHSA-3mv9-4h5g-vhg3

tsup DOM Clobbering vulnerability

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configCORS_ORIGINS
configHORIZON_URLNo https://horizon-testnet.stellar.org Horizon API URL
configHOST
configLOG_LEVELNo info debug, info, warn, error
🔐 secretOZ_API_KEYHTTP mode — OpenZeppelin facilitator API key
configOZ_FACILITATOR_URLHTTP mode — OpenZeppelin x402 facilitator URL
configREFLECTOR_CONTRACT_IDNo — Reflector oracle contract ID on Stellar (enables ReflectorOracle in PriceAggregator)
configSOROBAN_RPC_URLRequires to be configured. Uses Soroban contract simulation (read-only, no fees).
configSTELLARMCP_URL
configSTELLAR_NETWORK"": "testnet"
configSTELLAR_PAYEE_ADDRESSHTTP mode — Your Stellar address for receiving payments
🔐 secretSTELLAR_SECRET_KEY
configTRANSPORThttp pnpm start
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployPORT
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

17/17 tools missing one or more hints — getAccount (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); getAssetInfo (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); getClaimableBalances (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +14 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tool inputs are validated

11/17 tool handlers declare input schemas (65%)

Declare an inputSchema with zod/joi/yup on every tool definition.

Dev dependencies

2 critical/high in dev-only deps (does not ship to users)

Upgrade dev dependencies when convenient.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 4 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/siriuslattice/stellarmcp)](https://m8ven.ai/mcp/siriuslattice/stellarmcp)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: cefc720c9ec37907136add858881d1c044fcfea6
code hash: 73d6a6505889bf067ae1b14b79344fb5cef1c1cda7ac5eb63088c09a7e8bf887
verified: 6/22/2026, 12:58:51 PM
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client