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/bridgenode-ai/bridgenode-skill/bridgenodegit clone --depth 1 https://github.com/bridgenode-ai/bridgenode-skillWrote 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/bridgenode-ai/bridgenode-skill/bridgenode)<a href="https://agentmods.dev/mcp/bridgenode-ai/bridgenode-skill/bridgenode"><img src="https://agentmods.dev/badge/mcp/bridgenode-ai/bridgenode-skill/bridgenode.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
bridgenode 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 4d 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.
The source is not reproduced here
Licensed MIT-0
The repository is licensed MIT-0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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.
- 4d ago First seen · 5 lines scan A 302daa832701
bridgenode is an MCP server published in the GitHub repository bridgenode-ai/bridgenode-skill (2 stars, last pushed yesterday), licensed MIT-0. 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
gonka-mcp-server
A second opinion for AI agents: one prompt across several live Gonka models + roles, one call. Remote server at mcp.gogonka.com.
bridgenode-mcp
BridgeNode — x402 pay-per-request AI inference. OpenAI-compatible API + MCP server, Solana USDC. Runs locally from the @bridgenode/mcp npm package.
svelte
MCP server "svelte", hosted remotely at mcp.svelte.dev, as configured in xinity-ai/xinity-ai.
agenticpay
Real MCP server (stdio + @modelcontextprotocol/sdk) that exposes x402-paywalled HTTP endpoints as MCP tools. Drop into Claude Desktop, Cursor, or any MCP client. Runs locally from the @agenticpay/mcp-bridge npm package. Needs 6 environment variables to run.
council
MCP server "council" as configured in openvecta/council. Runs locally from the @openvecta/council npm package.
agent-toolbox
26 deterministic, offline pre-action safety gates for AI agents, each with a signed verdict. Runs locally from the agentoolbox-mcp npm package.