MCP servers › io.github.GuardBee › security-suite

MCP server · registry snapshot 2026-10-23 · last tested 2026-10-23

io.github.GuardBee/security-suite

Every GuardBee MCP security tool in one server: OWASP MCP Top 10, secrets, supply chain, TLS/DNS — the publisher's description

9 of 9 record checks metRead-only · tools listed 2026-10-23Topic: security · AI-classifiedversion 0.4.1TypeScriptMITstandard input/output31 tools

Summary

io.github.GuardBee/security-suite is a local MCP server listed in the official MCP registry at version 0.4.1. On 2026-10-23 ProtocolProbe started its published package in an isolated sandbox in read-only mode and read its inventory: 31 tools, 0 resources and 0 prompts.

Record checks

9 of 9 record checks met

met: Registry entry is active and says how to run it
met: Source repository link opens
met: Repository is not archived
met: Code pushed to the repository in the 90 days before our check
met: Repository publishes a security policy (SECURITY.md)
met: Package names its licence with a standard (SPDX) identifier
met: The version the registry lists can be installed and is not withdrawn
met: npm package carries build provenance (attestation)
met: No known critical or high advisory in the package or its dependencies

#3,059 of 15,112 packages by monthly downloads, tied with 3 others (package shared with 1 other registry entry)
Not ranked by stars: 1 star (ranked from 10)
#443 of 1,074 packages meeting all 9 record checks, by downloads, tied with 1 other

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Key facts

Runs: local package
Transport: standard input/output
Package: npm · listed version current
License: MIT
Dependencies: no known high or critical advisories
Repository: public
Tools: 31
Described as changing data: 10 of 31 toolsAI-classified
Mainly works on: files and code on the machine it runs on; accounts and data in outside web servicesAI-classified
Topic: securityAI-classified
Last tested: 2026-10-23

Add to your client

Worth knowing before you connect it

10 tools are described as changing something (owasp_scan_path, owasp_scan_live, owasp_scan_catalog, …): our AI model's reading of the descriptions, not something we tested. We did not call them.
Its package is signed and carries a build record naming its source.

Each line comes from a section below, with its source and date.

How fresh this is

Live-tested

yes, a real session (not a text-only review)

Last tested

2026-10-23

Mode

read-only (no tool calls)

Latest version

0.4.1, published 2026-10-22 (registry, as of the 2026-10-23 snapshot)

First listed version

2026-10-09 (earliest version still in the registry; older removed versions would be earlier)

Version history

15 versions listed, 2026-10-09 to 2026-10-22; 15 in the 90 days before the 2026-10-23 snapshot.

Most recent 12 versions

0.4.1 · 2026-10-22
0.4.0 · 2026-10-22
0.3.1 · 2026-10-22
0.3.0 · 2026-10-22
0.2.19 · 2026-10-14
0.2.18 · 2026-10-14
0.2.17 · 2026-10-14
0.2.16 · 2026-10-14
0.2.14 · 2026-10-13
0.2.13 · 2026-10-13
0.2.11 · 2026-10-13
0.2.10 · 2026-10-13

(versions still listed in the registry only)

Registry data

snapshot 2026-10-23

Package and repository

checked 2026-10-23

Engine

mcp-runtime-engine@0.1.0 · sdk@1.32.0

Changes since the last refresh

New in the registry: not in the list of 2026-10-04, listed on 2026-10-23 with version 0.4.1 (published 2026-10-22).

Source: the official MCP Registry list on 2026-10-04 and on 2026-10-23.

What it is

What does this server offer?

Observed inventory

31tools

0resources

0prompts

What it mainly works on, as our AI model read its tool descriptions: files and code on the machine it runs on; accounts and data in outside web services.

10 of 31 tools are described as changing something (creating, editing, deleting, sending or running). For 1 the reading was uncertain, so no mark is shown.

owasp_scan_pathon 1 other serverruns code or commandsdescribed as changing data
“Run a unified OWASP MCP Top 10 scan over a filesystem path — orchestrates secret, server, oauth, audit-gap, context-oversharing, toxic-flow, and tool-poisoning auditors; returns A–F grade.”
4 inputs, 1 required
- pathstringrequired“File or directory to scan”
- maxFilesinteger
- discoverShadowboolean“Also discover Shadow MCP on this host (MCP09)”
- allowlistPathstring“Allowlist file for Shadow MCP discover”
owasp_scan_liveon 1 other serverruns code or commandsdescribed as changing data
“Connect to a live MCP server (stdio or HTTP), call tools/list, then grade toxic-flow + tool-poisoning (MCP03/MCP10).”
3 inputs
- urlstring“Streamable HTTP MCP URL”
- commandstring“stdio command to spawn”
- argsarray
owasp_scan_catalogon 1 other serverruns code or commandsdescribed as changing data
“Audit a tools/list JSON dump for toxic flows and tool-description poisoning (MCP03/MCP10).”
2 inputs, 1 required
- catalogstringrequired“JSON string: { tools: [...] } or a bare tools array”
- labelstring
list_owasp_coverageon 1 other serverreads or searches
“List OWASP MCP Top 10 categories and which GuardBee scanners cover them in this meta-scan”
Takes no inputs.
secrets_scan_textreads or searches
“Scan a text string or code snippet for exposed secrets and API keys”
3 inputs, 1 required
- contentstringrequired“The text content to scan”
- labelstring“Optional label shown in findings (e.g.”
- entropyboolean“Also flag random-looking values assigned to secret-like names (default true)”
secrets_scan_filereads or searches
“Scan a single file for exposed secrets and API keys”
2 inputs, 1 required
- pathstringrequired“Absolute or relative path to the file to scan”
- entropyboolean“Also flag random-looking values assigned to secret-like names (default true)”
secrets_scan_directoryreads or searches
“Recursively scan a directory for exposed secrets and API keys.”
6 inputs, 1 required
- pathstringrequired“Absolute or relative path to the directory to scan”
- maxFilesinteger“Maximum number of files to scan (default: 5000)”
- includearray“Only scan files whose path contains one of these strings (e.g.”
- excludearray“Skip files/dirs whose path contains one of these strings”
- baselinestring“Path to a baseline file: only findings not in it are reported”
- entropyboolean“Also flag random-looking values assigned to secret-like names (default true)”
secrets_scan_gitreads or searches
“Scan a git repository for secrets in what git says was added: the staged changes (before a commit) or every commit's added lines (history).”
6 inputs, 2 required
- pathstringrequired“A directory inside the git repository”
- modestringrequired“staged: lines added in the index; history: lines added by each commit”
- rangestring“History only: a revision range such as main..HEAD (default: all refs)”
- maxCommitsinteger“History only: stop after this many commits”
- baselinestring“Path to a baseline file: only findings not in it are reported”
- entropyboolean“Also flag random-looking values assigned to secret-like names (default true)”
secrets_scan_agent_historyreads or searches
“Scan the transcripts coding agents keep on this machine (Claude Code, Codex, Gemini CLI, Continue) for secrets that were pasted into a chat or printed by a command.”
1 input
- entropyboolean“Also flag random-looking values assigned to secret-like names (default false here: transcripts hold a lot of code)”
secrets_list_patternsreads or searches
“List all secret patterns that the scanner can detect”
Takes no inputs.
injection_scan_textreads or searches
“Scan a text string — a RAG chunk, a scraped web page, a document, a tool result — for indirect prompt injection payloads (instruction-override phrases, spoofed chat-template roles, hidden/invisible t…”
2 inputs, 1 required
- contentstringrequired“The text content to scan”
- labelstring“Optional label shown in findings (e.g.”
injection_scan_filereads or searches
“Scan a single file (a knowledge-base document, an HTML page, extracted text) for indirect prompt injection payloads”
1 input, 1 required
- pathstringrequired“Absolute or relative path to the file to scan”

Show 19 more tools

injection_scan_directoryreads or searches
“Recursively scan a directory — e.g.”
4 inputs, 1 required
- pathstringrequired“Absolute or relative path to the directory to scan”
- maxFilesinteger“Maximum number of files to scan (default: 5000)”
- includearray“Only scan files whose path contains one of these strings (e.g.”
- excludearray“Skip files/dirs whose path contains one of these strings”
injection_list_patternsreads or searches
“List all indirect prompt injection patterns that the scanner can detect, grouped by category”
Takes no inputs.
toxic_flow_audit_catalogruns code or commandsdescribed as changing data
“Audit a tools/list-shaped JSON catalog for the lethal trifecta (toxic flow): untrusted content + sensitive/private data + exfiltration or destruction on the same MCP server.”
2 inputs, 1 required
- catalogstringrequired“JSON array of tools, or { tools: [...] } from tools/list”
- labelstring“Optional label for the server/catalog”
toxic_flow_scan_sourceruns code or commandsdescribed as changing data
“Scan TypeScript/JavaScript MCP server source for .registerTool(...) and .tool(...) registrations and audit them for toxic flows”
2 inputs, 1 required
- contentstringrequired“Source code to scan”
- labelstring
toxic_flow_scan_fileruns code or commandsdescribed as changing data
“Scan a single source file for toxic flows”
1 input, 1 required
- pathstringrequired
toxic_flow_scan_directoryruns code or commandsdescribed as changing data
“Recursively scan a directory of MCP server source for toxic flows across all registered tools”
3 inputs, 1 required
- pathstringrequired
- maxFilesinteger
- excludearray
toxic_flow_explain_trifectareads or searches
“Explain the lethal trifecta / toxic-flow model this auditor uses”
Takes no inputs.
mcp_config_scan_config_textreads or searches
“Scan an MCP client config JSON string (Cursor mcp.json, Claude Desktop, Windsurf, or VS Code) for unpinned packages, secrets, wildcard auto-approve, unauthenticated remote endpoints, and typosquats.”
2 inputs, 1 required
- contentstringrequired“Raw JSON config”
- labelstring“Optional filename shown in findings”
mcp_config_scan_filereads or searches
“Scan one MCP client config file, or a SKILL.md agent skill when the file has that name.”
1 input, 1 required
- pathstringrequired“Path to the config file”
mcp_config_scan_skill_textreads or searches
“Scan one agent SKILL.md (YAML frontmatter plus body) for unrestricted allowed-tools, instruction override, credential file reads, and literal secrets.”
2 inputs, 1 required
- contentstringrequired“Raw SKILL.md text”
- labelstring“Optional filename shown in findings”
mcp_config_scan_directoryreads or searches
“Find mcp.json, mcp_config.json, claude_desktop_config.json, and SKILL.md under a directory and audit each one.”
3 inputs, 1 required
- pathstringrequired“Directory to search”
- maxFilesinteger“Maximum files to consider (default: 5000)”
- excludearray“Skip paths containing one of these strings”
mcp_config_scan_inventoryreads or searches
“Detect cross-server tool shadowing from an inventory of tool catalogs.”
1 input, 1 required
- inventorystringrequired“JSON: {"servers":[{"name":"github","tools":[{"name":"create_issue","description":"..."}]}]}”
mcp_config_discover_shadow_mcpreads or searches
“OWASP MCP09:2025 — discover MCP client configs in well-known host paths (Cursor, Claude Desktop, Windsurf, VS Code, Claude Code) and flag servers that are not on an organization allowlist (Shadow MCP…”
3 inputs
- allowliststring“JSON allowlist: {"names":["filesystem"],"packages":["@modelcontextprotocol/server-filesystem"],"hosts":["mcp.example.com"]} or line form name:/package:/host:”
- homestring“Override home directory used to resolve well-known config paths”
- includeContentAuditboolean“Also run the normal config content checks on each discovered file (default false)”
mcp_config_list_host_config_pathsreads or searches
“List the well-known MCP client config paths this auditor checks during shadow (MCP09) discovery on the current OS.”
1 input
- homestring“Override home directory”
mcp_config_list_patternsreads or searches
“List the MCP config, agent skill, shadow-MCP discovery, and cross-server shadowing checks, with their OWASP MCP Top 10 tags.”
Takes no inputs.
deps_audit_npmruns code or commandsdescribed as changing data
“Audit npm dependencies for known CVEs using the OSV database.”
3 inputs, 1 required
- directorystringrequired“Path to the directory containing package.json”
- includeDevDepsboolean“Include devDependencies in the audit (default: false)”
- exploitDataboolean“Add CISA KEV (exploited in the wild) and FIRST EPSS data and order findings by it (default: true; sends CVE IDs only)”
deps_audit_pipruns code or commandsdescribed as changing data
“Audit Python dependencies for known CVEs using the OSV database.”
3 inputs, 1 required
- directorystringrequired“Path to the directory containing requirements.txt or pyproject.toml”
- includeDevDepsboolean“Include dev groups from poetry.lock, uv.lock or Pipfile.lock (default: false)”
- exploitDataboolean“Add CISA KEV (exploited in the wild) and FIRST EPSS data and order findings by it (default: true; sends CVE IDs only)”
deps_audit_package
“Audit a single package by name, version, and ecosystem”
4 inputs, 3 required
- namestringrequired“Package name”
- versionstringrequired“Package version (e.g.”
- ecosystemstringrequired“Package ecosystem”
- exploitDataboolean“Add CISA KEV (exploited in the wild) and FIRST EPSS data and order findings by it (default: true; sends CVE IDs only)”
deps_audit_directoryruns code or commandsdescribed as changing data
“Auto-detect and audit every supported project in a directory: npm (package-lock, pnpm, yarn, bun), Python (uv, Poetry, Pipenv, requirements), Rust (Cargo.lock), Go (go.mod), Ruby (Gemfile.lock) and P…”
3 inputs, 1 required
- directorystringrequired“Path to the project root directory”
- includeDevDepsboolean“Include dev dependencies (default: false)”
- exploitDataboolean“Add CISA KEV (exploited in the wild) and FIRST EPSS data and order findings by it (default: true; sends CVE IDs only)”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-23.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

Says what the tool does: 100% of 31 tools
Says what it returns: 100% of 31 tools
States limits, defaults or errors: 19% of 31 tools
Items covered per tool: 3.2 of 4 on average

Counted from the listing

Parameters with a description: 88% of 68
Tools with a description: 100% of 31
Typical description length: 146 characters

The tool set

Counted from the listing

Tools: 31
Size of the list: about 4,445 tokens for an agent to load (characters ÷ 4)
Naming: 31 of 31 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 31 of 31 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the npm package @guardbee/security-suite

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below. The command runs the publisher’s code on your machine.

Claude Desktop · claude_desktop_config.json (Settings → Developer → Edit Config)

{
  "mcpServers": {
    "security-suite": {
      "command": "npx",
      "args": [
        "-y",
        "@guardbee/security-suite@0.4.1",
        "serve",
        "--tools",
        "recommended"
      ]
    }
  }
}

Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "security-suite": {
      "command": "npx",
      "args": [
        "-y",
        "@guardbee/security-suite@0.4.1",
        "serve",
        "--tools",
        "recommended"
      ]
    }
  }
}

VS Code · .vscode/mcp.json

{
  "servers": {
    "security-suite": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@guardbee/security-suite@0.4.1",
        "serve",
        "--tools",
        "recommended"
      ]
    }
  }
}

VS Code (command line) · Bash or zsh terminal (macOS, Linux)

code --add-mcp '{"name":"security-suite","type":"stdio","command":"npx","args":["-y","@guardbee/security-suite@0.4.1","serve","--tools","recommended"]}'

Claude Code

claude mcp add --transport stdio security-suite -- npx -y @guardbee/security-suite@0.4.1 serve --tools recommended

Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+

npx @modelcontextprotocol/inspector@2.11.0 -- npx -y @guardbee/security-suite@0.4.1 serve --tools recommended

Arguments are written as the registry entry gives them; a named one as “--name value”, the form the registry documentation shows.
This runs the publisher's code on your machine (npx). Read its README first.
The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Can it be installed, and is it up to date?

Version pin · advisories

Listed version

Registry lists: 0.4.1
Latest stable: 0.4.1
Status: current
Withdrawn: no

Source: registry.npmjs.org · 2026-10-23. About the version the registry lists; a manual install may resolve to a different one.

Dependency advisories

Counted in the full dependency tree as resolved on 2026-10-23 (npm audit). Bars share one scale. The package itself has no known vulnerability (OSV.dev).

Integrity, provenance, license

Integrity: sha512-ab+OHlyT/4JrWeJcF…
Signature: signed and attested
License: MIT

Source: the package registry · 2026-10-23.

Usage

Downloads: 917 in the last month

Source: api.npmjs.org · 2026-10-23.

Does the registry listing match what we found?

Feature #6

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.

Registry says	We found	Result	Source · date
Published package can be started	Started and answered	matches	our test · 2026-10-23
Version 0.4.1 on npm	Exists and can be installed	matches	npm · 2026-10-23
Repository github.com/GuardBee/guardbee-mcp	Opens publicly	matches	api.github.com · 2026-10-23

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace: io.github.GuardBee · 32 servers
GitHub owner: an organization (GuardBee)
Build record: signed and attested

Repository: github.com/GuardBee/guardbee-mcp
Stars: 1
Repository age: 31–90 days
Last push: 0–30 days ago
Archived: no
Security policy: SECURITY.md

Source: the registry entry and api.github.com · 2026-10-23; security policy read from GitHub · 2026-10-23.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Choosing

Record checks

Public records · not a safety rating

9 of 9 record checks met

#3,059 of 15,112 packages by monthly downloads, tied with 3 others (package shared with 1 other registry entry)
Not ranked by stars: 1 star (ranked from 10)
#443 of 1,074 packages meeting all 9 record checks, by downloads, tied with 1 other

MetRegistry entry is active and says how to run itActive, with a package or a remote address.
MetSource repository link opensThe linked GitHub repository is public.
MetRepository is not archivedNot archived.
MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
MetRepository publishes a security policy (SECURITY.md)SECURITY.md found.
MetPackage names its licence with a standard (SPDX) identifierMIT
MetThe version the registry lists can be installed and is not withdrawnThe listed version exists and is current.
Metnpm package carries build provenance (attestation)Signed, with a build attestation naming the source and workflow.
MetNo known critical or high advisory in the package or its dependenciesNone known in the package or its dependency tree.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-23. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating. How each check works · Leaderboards

Common questions about io.github.GuardBee/security-suite

Answered from the data above

Is io.github.GuardBee/security-suite safe to install?

We do not rate servers as safe or unsafe. 9 of its 9 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its npm package carries a build-provenance attestation that names its source repository and build workflow. Its source repository opens publicly. Its repository had a push in the last 90 days. The listed version is the latest stable release. The package itself has no known vulnerability (OSV.dev). Its full dependency tree has no known advisory. 10 of its tools describe changing data (our AI model's reading of the descriptions). These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Has io.github.GuardBee/security-suite been security tested?

Partly. 2 of the 12 checks that apply to it were exercised. We started the package in an isolated sandbox and read what it declares, but this test round was read-only, so its tools were not called. No security verdict is published before verification.

What can io.github.GuardBee/security-suite do?

It lists 31 tools. In our AI model's reading of their descriptions (two runs had to agree, nobody checked it by hand), they include tools that read or search and run code or commands. We did not call any tool, so this describes the text, not the behaviour.

Can io.github.GuardBee/security-suite change or delete data?

10 of its tools say in their description that they create, edit, delete, send or run something (our AI model's reading). We did not call any tool, so we cannot say what actually happens.

Does io.github.GuardBee/security-suite publish a security policy?

Yes: its repository has a public security policy (github.com/guardbee/guardbee-mcp/blob/HEAD/SECURITY.md). That is the publisher's statement, not permission for us to test the server, and we call none of its tools.

Is the listed version current?

Yes. The registry lists 0.4.1, the latest stable release on npm.

Where is the source code of io.github.GuardBee/security-suite?

In github.com/GuardBee/guardbee-mcp, which opens publicly.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Similar servers

Same topic · AI-read

io.github.dengyier/OpenWorkProofalso has tools that runs code or commands, reads or searchescompare with this one
io.github.arthurpanhku/dvalincodealso has tools that runs code or commands, reads or searchescompare with this one
io.github.Servosity/blumira-mcpBlumira MCPalso has tools that runs code or commands, reads or searchescompare with this one
io.github.msaad00/agent-bomagent-bomalso has tools that runs code or commands, reads or searchescompare with this one
io.github.ashlrai/phantom-secrets-mcpPhantom Secretsalso has tools that runs code or commands, reads or searchescompare with this one
io.github.vaaraio/vaara-serverVaara MCP Serveralso has tools that runs code or commands, reads or searchescompare with this one

Active servers whose topic is also “security” and that have at least one tool of the same kind; most kinds in common first, then most GitHub stars. The topic and the tool kinds are an AI model's reading of the publishers' descriptions, not checked by hand. Similar is not a recommendation.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Not probed (read-only run)

We started the package in an isolated sandbox and read what it declares, but this test round was read-only, so its tools were not called. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-10-23

Inventory: exercised
Hidden instructions: exercised
Real execution: not run · our policy
Secret leak: not run · nothing to check it against
Internal addresses: not run · our policy
Unconfirmed changes: not run · our policy
Bad input: not run · our policy
Model requests: not run · nothing to check it against
Sensitive questions: not run · nothing to check it against
Folder boundary: not run · our policy
Log leaks: not run · nothing to check it against
Hidden content: not run · nothing to check it against
Fake assistant turns: not applicable
Token passthrough: not applicable
Token audience: not applicable
Sign-in redirect: not applicable
Consent handling: not applicable
Sign-in metadata: not applicable

2 exercised10 not run (reason given)6 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 2 of the 12 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.

Exercised · 2

1Inventory
tool-listReads the declared tools, resources and prompts.exercised
2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised

Not run, with the reason · 10

3Real execution
real-executionCalls a tool and checks what really happens.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
4Secret leak
canary-leakPlants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
5Internal addresses
ssrfChecks whether a tool can be steered to internal addresses.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
6Unconfirmed changes
write-without-confirmationChecks whether tools that change data act without asking.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
7Bad input
error-handlingSends bad input and watches how the server answers.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
8Model requests
samplingChecks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
9Sensitive questions
elicitation-sensitive-dataChecks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
10Folder boundary
root-boundaryChecks whether the server reaches outside the folders it was given.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
11Log leaks
logging-side-channelChecks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
12Hidden content
audience-hidingChecks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against

Does not apply to this server · 6

13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable
14Token passthrough
token-passthroughChecks whether the server forwards a user's token to other services.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
15Token audience
token-audience-validationChecks whether tokens meant for another service are accepted.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
16Sign-in redirect
open-redirectChecks the sign-in redirect for abuse.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
17Consent handling
confused-deputyChecks consent handling when one service acts for another.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable

Source: our own test in an isolated sandbox, 2026-10-23, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

0 msStarted the published package in an isolated sandbox (read-only mode)
7,458 msConnected after 0 redirects.
Read the inventory: 31 tools, 0 resources, 0 prompts.
8,749 msFinished: 2 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified

security

AI-classified · 2026-10-23

Pricing modelAI-classified

not checked

no website in the registry entry

Programming language

TypeScript

api.github.com · 2026-10-23

Hosting type

local package

registry · 2026-10-23

MCP capability

tools

our test · 2026-10-23

Transport

standard input/output

registry · 2026-10-23

Required credentials

none declared

registry · no declaration is not a guarantee

Package registry

npm

registry · 2026-10-23

Freshness

0–30 days

registry updatedAt · 2026-10-23

Lifecycle status

active

registry · 2026-10-23

License class

permissive

package registry · 2026-10-23

Integrity hash

declared (sri)

package registry · 2026-10-23

Signature / provenance

signed and attested

package registry · 2026-10-23

Dependency advisories

none known

npm audit · 2026-10-23

Popularity

917 downloads a month

package registry · 2026-10-23

Publisher signals

owner: an organization · repository age: 31–90 days · stars: 0–9 · build record: signed and attested

api.github.com · 2026-10-23

Maintenance

active

api.github.com · 2026-10-23

Environment

your machine

where it runs, from the hosting type

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “io.github.GuardBee/security-suite: MCP server record.” Data checked 2026-10-23. https://protocolprobe.com/mcp/servers/io.github.GuardBee/security-suite

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/io.github.GuardBee/security-suite)](https://protocolprobe.com/mcp/servers/io.github.GuardBee/security-suite)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology