Nimbus MCP Server

nimbus-mcp npm v1.6.0

Published by h4cd0c — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

Nimbus - AWS Security Assessment MCP Server - 45 Tools with Full OWASP MCP Security

Trust grade
A
93/100
Last scanned get badge →
Trust
A · 93/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
High
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 93/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 7 = 93. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−6 capability blast radius (high) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 3

high Sensitive-source and external-sink co-existMTC-FLOW-004

Tools that read sensitive data ([aws_scan_secrets_manager, Get Secret Value]) and tools that can send data out ([SSM Run Command]) are exposed together. An agent can move private data to the sink.

Evidence: sources [aws_scan_secrets_manager, Get Secret Value] → sinks [SSM Run Command]

Fix: Keep secret-reading and egress capabilities on separate, separately-approved servers.

Location: flow aws_scan_secrets_manager → SSM Run Command

high Tool "SSM Run Command" exposes command/code executionMTC-CAP-001

Tool "SSM Run Command" appears to run shell commands or evaluate code (keyword "run_command" in tool name). Arbitrary execution driven by model input is one of the most dangerous MCP capabilities; combined with any untrusted input it becomes RCE.

Fix: Sandbox execution, allowlist commands/arguments, and never pass model output to a shell unescaped.

Location: tool SSM Run Command

low Mutating tool "SSM Run Command" declares no destructiveHintMTC-CAP-005

Tool "SSM Run Command" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.

Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.

Location: tool SSM Run Command

Tools 87

Each tool and what it can reach — statically extracted from the published source.

  • aws_scan_secrets_managerreads sensitive data
  • Get Secret Valuereads sensitive data
  • SSM Run Commandruns code / shell
  • Add Malicious Lambda Layerno sensitive capability
  • Attach Administrator Policyno sensitive capability
  • Attach Policy to Roleno sensitive capability
  • aws_analyze_ami_securityno sensitive capability
  • aws_analyze_api_distribution_securityno sensitive capability
  • aws_analyze_cloudwatch_securityno sensitive capability
  • aws_analyze_cross_account_movementno sensitive capability
Show 77 more tools ↓
  • aws_analyze_ec2_metadata_exposureno sensitive capability
  • aws_analyze_eks_attack_surfaceno sensitive capability
  • aws_analyze_encryption_securityno sensitive capability
  • aws_analyze_iam_trust_chainsno sensitive capability
  • aws_analyze_iam_usersno sensitive capability
  • aws_analyze_infrastructure_automationno sensitive capability
  • aws_analyze_lambda_securityno sensitive capability
  • aws_analyze_messaging_securityno sensitive capability
  • aws_analyze_network_exposureno sensitive capability
  • aws_analyze_network_securityno sensitive capability
  • aws_analyze_s3_securityno sensitive capability
  • aws_analyze_service_role_chainno sensitive capability
  • aws_build_attack_chainsno sensitive capability
  • aws_cache_clearno sensitive capability
  • aws_cache_statsno sensitive capability
  • aws_detect_data_exfiltration_pathsno sensitive capability
  • aws_detect_mfa_bypass_vectorsno sensitive capability
  • aws_detect_permissive_rolesno sensitive capability
  • aws_detect_persistence_mechanismsno sensitive capability
  • aws_detect_privesc_patternsno sensitive capability
  • aws_enumerate_detection_servicesno sensitive capability
  • aws_enumerate_ec2_instancesno sensitive capability
  • aws_enumerate_eks_clustersno sensitive capability
  • aws_enumerate_iam_rolesno sensitive capability
  • aws_enumerate_organizationsno sensitive capability
  • aws_enumerate_public_resourcesno sensitive capability
  • aws_enumerate_rds_databasesno sensitive capability
  • aws_generate_security_reportno sensitive capability
  • aws_generate_tra_reportno sensitive capability
  • aws_get_audit_logsno sensitive capability
  • aws_get_guardduty_findingsno sensitive capability
  • aws_helpno sensitive capability
  • aws_hunt_eks_secretsno sensitive capability
  • aws_list_active_regionsno sensitive capability
  • aws_scan_all_regionsno sensitive capability
  • aws_scan_api_gateway_authno sensitive capability
  • aws_scan_container_registry_poisoningno sensitive capability
  • aws_scan_eks_irsa_risksno sensitive capability
  • aws_scan_eks_service_accountsno sensitive capability
  • aws_scan_elasticache_securityno sensitive capability
  • aws_scan_lambda_cold_start_risksno sensitive capability
  • aws_scan_resource_policiesno sensitive capability
  • aws_scan_ssm_securityno sensitive capability
  • aws_whoamino sensitive capability
  • Create Access Keyno sensitive capability
  • Create Inline Role Policyno sensitive capability
  • Create Inline User Policyno sensitive capability
  • Create Login Profileno sensitive capability
  • Create Policy Versionno sensitive capability
  • Delete CloudTrailno sensitive capability
  • Disable GuardDutyno sensitive capability
  • EKS Cluster Admin Accessno sensitive capability
  • EKS Fargate Profile PassRoleno sensitive capability
  • EKS Node Role Credential Theftno sensitive capability
  • EKS Wildcard Describeno sensitive capability
  • etcd Secrets Encryption Not Enabledno sensitive capability
  • IRSA Pod Execution Abuseno sensitive capability
  • Lambda Environment Variable Secretsno sensitive capability
  • Lambda Layer Backdoorno sensitive capability
  • Missing Control Plane Loggingno sensitive capability
  • Modify S3 Bucket Policyno sensitive capability
  • PassRole to CloudFormationno sensitive capability
  • PassRole to CodeBuildno sensitive capability
  • PassRole to EC2no sensitive capability
  • PassRole to ECS Taskno sensitive capability
  • PassRole to Glueno sensitive capability
  • PassRole to Lambdano sensitive capability
  • PassRole to SageMakerno sensitive capability
  • Public API Server Endpointno sensitive capability
  • S3 Data Exfiltrationno sensitive capability
  • Set Default Policy Versionno sensitive capability
  • SSM Parameter Store Secretsno sensitive capability
  • SSM Start Sessionno sensitive capability
  • Stop CloudTrail Loggingno sensitive capability
  • Update Assume Role Policyno sensitive capability
  • Update Lambda Codeno sensitive capability
  • Update Login Profileno sensitive capability

Toxic flows 1

Cross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v1.6.0 latest A 93/100 3 1.13.0 2026-08-30

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 93/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/nimbus-mcp/badge.svg)](https://mcptrustchecker.com/registry/nimbus-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/nimbus-mcp"><img src="https://mcptrustchecker.com/registry/nimbus-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/nimbus-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan nimbus-mcp --online

Use the free API → How scoring works

More in Security & Testing