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/CryptoServers/nordbastion-mcpWrote 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/cryptoservers/nordbastion-mcp/nordbastion)<a href="https://agentmods.dev/mcp/cryptoservers/nordbastion-mcp/nordbastion"><img src="https://agentmods.dev/badge/mcp/cryptoservers/nordbastion-mcp/nordbastion/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/cryptoservers/nordbastion-mcp/nordbastion"><img src="https://agentmods.dev/badge/mcp/cryptoservers/nordbastion-mcp/nordbastion.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
nordbastion 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
{
"nordbastion": {
"command": "uvx",
"args": [
"nordbastion-mcp"
],
"env": {
"NORDBASTION_API_KEY": "nb_live_xxxxxxxxxxxxxxxx"
}
}
}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 · 11 lines scan A 8a27a8fd66c0
nordbastion is an MCP server published in the GitHub repository CryptoServers/nordbastion-mcp (0 stars, last pushed 3mo 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
dataproc
MCP server "dataproc", hosted remotely at dataproc-$gcpregion.googleapis.com, as configured in gemini-cli-extensions/data-agent-kit-starter-pack. Needs 1 environment variable to run.
mcp-pve
Manage Proxmox VE through AI assistants. Runs locally from the @samik081/mcp-pve npm package. Needs 3 environment variables to run.
ssh-licco
SSH Model Context Protocol Server - Enable SSH functionality for AI models. Runs locally from the ssh-licco Python package. Needs 4 environment variables to run.
AWSPrice
MCP server "AWSPrice" as configured in spacehendrix/clauder. Runs locally from the awslabs.aws-pricing-mcp-server@latest Python package. Needs 3 environment variables to run.
terraform
MCP server "terraform" as configured in aws-samples/sample-agentic-chatbot-accelerator. Runs in Docker (hashicorp/terraform-mcp-server:0.5.2).
CloudflareLogpush
MCP server "CloudflareLogpush", hosted remotely at logs.mcp.cloudflare.com, as configured in spacehendrix/clauder.