Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/rylsherdamz-rgb/stellar-forgeWrote 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/mcp/rylsherdamz-rgb/stellar-forge/stellar-rpc)<a href="https://agentmods.dev/mcp/rylsherdamz-rgb/stellar-forge/stellar-rpc"><img src="https://agentmods.dev/badge/mcp/rylsherdamz-rgb/stellar-forge/stellar-rpc/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/rylsherdamz-rgb/stellar-forge/stellar-rpc"><img src="https://agentmods.dev/badge/mcp/rylsherdamz-rgb/stellar-forge/stellar-rpc.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
stellar-rpc 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 1mo 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.
What it actually says
{
"stellar-rpc": {
"command": "npx",
"args": [
"@stellar/mcp-server"
],
"env": {
"STELLAR_RPC_URL": {
"description": "Stellar RPC endpoint. Defaults to testnet.",
"default": "https://soroban-testnet.stellar.org"
},
"STELLAR_NETWORK_PASSPHRASE": {
"description": "Network passphrase. Defaults to Test SDF Network ; September 2015",
"default": "Test SDF Network ; September 2015"
}
}
}
}What else .mcp.json configures
This page is one entry in a file that holds 4. Installing the file brings all of them; each is measured and scanned on its own page.
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.
- 1mo ago First seen · 18 lines scan A c9c9d5a823d3
stellar-rpc is an MCP server published in the GitHub repository rylsherdamz-rgb/stellar-forge (17 stars, last pushed yesterday), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. 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-30.
Other mcp servers, from other repositories
stellar-agent-search
Discover and rank Stellar 8004 agents with a read-only MCP server and fail-closed contract probes. Runs locally from the stellar-agent-search npm package. Needs 4 environment variables to run.
mcp
Paid agent work and paid verification, settled in USDC. Verified outcomes get signed receipts. Remote server at api.averray.com.
sui-kapa
Semantic search across Sui documentation and knowledge sources, powered by kapa.ai. Remote server at sui.mcp.kapa.ai.
alchemy
MCP server "alchemy", hosted remotely at mcp.alchemy.com, as configured in alchemyplatform/alchemy-claude-plugin.
chains-api
MCP server "chains-api" as configured in Johnaverse/chains-api. Runs locally from the chains-api npm package.
frantic-mcp
A public bounty board where AI agents do paid work. USDC on Base, paid on accepted delivery. Runs locally from the frantic-mcp npm package.