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.
npx agentmods add mcp/1lystore/1ly-mcp-server/mcp-servergit clone --depth 1 https://github.com/1lystore/1ly-mcp-serverWrote 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/1lystore/1ly-mcp-server/mcp-server)<a href="https://agentmods.dev/mcp/1lystore/1ly-mcp-server/mcp-server"><img src="https://agentmods.dev/badge/mcp/1lystore/1ly-mcp-server/mcp-server.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
mcp-server 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 6d 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
{
"mcp-server": {
"command": "npx",
"args": [
"-y",
"@1ly/mcp-server"
],
"env": {
"ONELY_WALLET_SOLANA_KEY": "",
"ONELY_WALLET_EVM_KEY": "",
"ONELY_API_KEY": "",
"ONELY_WALLET_PROVIDER": "",
"ONELY_NETWORK": "",
"ONELY_SOLANA_RPC_URL": "",
"ONELY_BUDGET_PER_CALL": "",
"ONELY_BUDGET_DAILY": "",
"ONELY_BUDGET_STATE_FILE": "",
"ONELY_SOLANA_DRY_RUN": "",
"ONELY_API_BASE": ""
}
}
}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.
- 6d ago First seen · 22 lines scan A b97c2cb443a2
mcp-server is an MCP server published in the GitHub repository 1lystore/1ly-mcp-server (3 stars, last pushed 6mo ago), 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-31.
Other mcp servers, from other repositories
x402-commerce
TypeScript Execute (tsx): Node.js enhanced with esbuild to run TypeScript & ESM files. Runs locally from the tsx npm package. Needs 8 environment variables to run.
x402-commerce-solana
TypeScript Execute (tsx): Node.js enhanced with esbuild to run TypeScript & ESM files. Runs locally from the tsx npm package. Needs 7 environment variables to run.
x402-commerce-sandbox
TypeScript Execute (tsx): Node.js enhanced with esbuild to run TypeScript & ESM files. Runs locally from the tsx npm package. Needs 4 environment variables to run.
tryx402
The OpenRouter for agent payments: budget router, idempotency, cost ledger, and multi-currency billing over x402. Runs locally from the tryx402 Python package. Needs 2 environment variables to run.
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.
clawswap
Cross-chain swaps between Solana and Base for AI agents paid for via via x402 micropayments. Runs locally from the @clawswap/mcp-server npm package. Needs 4 environment variables to run.