Rad Security MCP Server
@rad-security/mcp-server
npm
v0.0.43
Source verified
Published by rad-security — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.
RAD Security MCP Server for AI-powered security insights
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 − 3 = 97. 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:
| Points | Adoption-risk factor |
|---|---|
| −3 | capability blast radius (moderate) — client exposure if the model is manipulated |
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 0
Tools 51
Each tool and what it can reach — statically extracted from the published source.
get_knowledge_base_document_download_urlingests untrusted inputadd_workflow_scheduleno sensitive capabilitycreate_custom_workflowno sensitive capabilitycreate_dashboardno sensitive capabilityget_cluster_detailsno sensitive capabilityget_container_detailsno sensitive capabilityget_container_llm_analysisno sensitive capabilityget_containers_baselinesno sensitive capabilityget_containers_process_treesno sensitive capabilityget_dashboardno sensitive capability
Show 41 more tools ↓
get_dashboard_templateno sensitive capabilityget_image_sbomno sensitive capabilityget_inbox_item_detailsno sensitive capabilityget_k8s_resource_detailsno sensitive capabilityget_knowledge_base_document_contentno sensitive capabilityget_top_vulnerable_imagesno sensitive capabilityget_widget_templateno sensitive capabilityget_workflowno sensitive capabilityget_workflow_runno sensitive capabilityignore_cveno sensitive capabilitylist_clustersno sensitive capabilitylist_containersno sensitive capabilitylist_cve_dispositionsno sensitive capabilitylist_dashboard_templatesno sensitive capabilitylist_dashboardsno sensitive capabilitylist_external_integrationsno sensitive capabilitylist_image_vulnerabilitiesno sensitive capabilitylist_imagesno sensitive capabilitylist_inbox_itemsno sensitive capabilitylist_k8s_resourcesno sensitive capabilitylist_knowledge_base_collectionsno sensitive capabilitylist_knowledge_base_documentsno sensitive capabilitylist_security_findingsno sensitive capabilitylist_widget_templatesno sensitive capabilitylist_workflow_runsno sensitive capabilitylist_workflow_schedulesno sensitive capabilitylist_workflowsno sensitive capabilitymark_inbox_item_as_false_positiveno sensitive capabilityquery_knowledge_base_documentno sensitive capabilityradql_batch_queryno sensitive capabilityradql_get_type_metadatano sensitive capabilityradql_list_data_typesno sensitive capabilityradql_list_filter_valuesno sensitive capabilityradql_query_builderno sensitive capabilityrun_workflowno sensitive capabilitysearch_knowledge_baseno sensitive capabilityunignore_cveno sensitive capabilityupdate_custom_workflowno sensitive capabilityupdate_dashboardno sensitive capabilityupdate_security_finding_statusno sensitive capabilitywho_shelled_into_podno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (51 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions 9
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.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v0.0.43 latest |
A 97/100 | 0 | 1.13.0 | 2026-09-07 |
v0.0.42 |
A 97/100 | 0 | 1.12.1 | 2026-08-14 |
v0.0.41 |
A 97/100 | 0 | 1.12.1 | 2026-08-10 |
v0.0.40 |
A 97/100 | 0 | 1.12.1 | 2026-08-07 |
v0.0.39 |
A 100/100 | 0 | 1.12.1 | 2026-07-28 |
Show 4 more versions ↓
v0.0.38 |
A 100/100 | 0 | 1.10.0 | 2026-07-27 |
v0.0.33 |
A 100/100 | 0 | 1.9.0 | 2026-07-24 |
v0.0.32 |
A 92/100 | 5 | 1.7.0 | 2026-07-23 |
v0.0.31 |
A 91/100 | 5 | 1.3.1 | 2026-07-21 |
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.
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 @rad-security/mcp-server --onlineMore in Cloud & DevOps
Operator control CLI for AdGuard Home with an MCP adapter
interacting with Aliyun (Alibaba Cloud) services through This MCP server provides tools.
MCP server for the Aspro.Cloud REST API
MCP server for Atlassian Confluence and Jira Cloud APIs
AuroraCloud-first MCP server that exposes AuroraDocs workspace data to Claude Desktop and other AI agents
The official AWS Knowledge Base retrieval server using Bedrock Agent Runtime.