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/dyegolara/nostr-auth-agentsWrote 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/dyegolara/nostr-auth-agents/nostr-auth)<a href="https://agentmods.dev/mcp/dyegolara/nostr-auth-agents/nostr-auth"><img src="https://agentmods.dev/badge/mcp/dyegolara/nostr-auth-agents/nostr-auth/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/dyegolara/nostr-auth-agents/nostr-auth"><img src="https://agentmods.dev/badge/mcp/dyegolara/nostr-auth-agents/nostr-auth.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
nostr-auth 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 10d 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
{
"nostr-auth": {
"command": "node",
"args": [
"mcp/server.js"
]
}
}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.
- 10d ago First seen · 8 lines scan A 406b8d970faf
nostr-auth is an MCP server published in the GitHub repository dyegolara/nostr-auth-agents (0 stars, last pushed 6d 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
nightgate-mcp
MCP server exposing NIGHTGATE (Midnight blockchain attestation layer) to AI agents. Runs locally from the @odatano/nightgate-mcp npm package.
vedetta
MCP server for Vedetta — pay-per-call crypto sentiment, divergence verdicts, and live analyst reads over x402 (USDC on Base). Descriptive market analysis only — not financial advice. Runs locally from the vedetta-mcp npm package. Needs 3 environment variables to run.
coal
Payment rails for AI agents. Pay merchants in USDC on Base. Dual-protocol: x402 + OKX APP. Remote server at mcp.usecoal.xyz.
seashail
MCP server "seashail" as configured in seashail/seashail. Launched with seashail mcp.
alloc-context
Portfolio-aware crypto context — CEX or wallet holdings, holdings-scoped market, optional allocation analysis. Runs locally from the alloc-context Python package.
thebuyside-x402-agent
Buyer-side MCP gateway for x402 and MPP (pay.sh) — let any agent pay any metered API on Base or Solana without seeing a 402 or a wallet. Runs locally from the thebuyside-x402-agent npm package.