Skip to main content
Glama
Sign In
ThreatByte-MCP

ThreatByte-MCP

by anotherik
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to ThreatByte-MCP

Related Servers

  • dvmcp

    ds8282
    A
    license
    Not graded
    quality
    C
    maintenance
    Serves as an intentionally vulnerable training target that exposes eight planted MCP vulnerability challenges—tool poisoning, rug pulls, path traversal, SSRF, command injection, missing auth, prompt-injection chains, and secrets exposure—each with a patched counterpart so users can exploit, detect, and remediate real-world MCP security flaws.
    Apache 2.0

  • MCP Security Lab

    ibrahimsaleem
    F
    license
    Not graded
    quality
    B
    maintenance
    Enables hands-on exploration of common MCP security vulnerabilities through locally runnable vulnerable and fixed servers with accompanying exploits and a dashboard.
    1
    -

  • VAmPI-MCP

    mcropsey
    F
    license
    Not graded
    quality
    C
    maintenance
    Enables interacting with a deliberately vulnerable API through MCP tools, allowing security testing and education by exercising vulnerabilities such as SQL injection, mass assignment, and broken access control.
    -

  • CyberSecurityLab MCP Server

    dbolatti
    F
    license
    Not graded
    quality
    B
    maintenance
    Provides an educational MCP server with cybersecurity examples, exposing a threat-intel lookup tool, an asset inventory resource, and an investigation prompt using simulated data.
    -
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

B3/5.0

Scored across 22 tools

Disambiguation4/5

Most tools have distinct purposes, with clear separation between cases, files, notes, indicators, and tools. However, cases.list and cases.list_all could cause confusion as their descriptions are similar, with list_all implying broader access but lacking clarity on how it differs from list with optional owner_id.

Naming Consistency5/5

Tool names follow a highly consistent pattern using dot notation for grouping (e.g., cases.create, files.list) and verb_noun structure within groups. This makes the tool set predictable and easy to navigate, with no deviations in style.

Tool Count4/5

With 22 tools, the count is on the higher side but reasonable for a security case management domain, covering multiple resource types like cases, files, notes, indicators, and tools. It might feel slightly heavy but each tool appears to serve a specific purpose.

Completeness5/5

The tool set provides comprehensive CRUD and lifecycle coverage for cases, files, and notes, along with search capabilities for indicators and tool management. There are no obvious gaps; agents can perform full workflows from case creation to resolution with file handling and note-taking.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources