Skip to main content
Glama
v0idravl

sliver-mcp

by v0idravl
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to sliver-mcp

No user-submitted related servers found.

    Related Servers

    • MCP Red Team Server

      canstralian
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server for orchestrating red team security assessments, enabling LLMs to manage agents, targets, operations, and findings aligned with MITRE ATT&CK framework.
      MIT

    • ghidraMCP

      albertlab0
      A
      license
      Not graded
      quality
      D
      maintenance
      An Model Context Protocol server that enables LLMs to autonomously reverse engineer applications by exposing Ghidra's decompilation and analysis tools. It allows AI agents to list code structures, rename methods, and analyze binaries directly through MCP-compatible clients.
      Apache 2.0

    • pwncat-mcp

      Vip3r-MC
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for the pwncat post-exploitation platform. It exposes 40+ tools for session management, file operations, command execution, enumeration, privilege escalation, implants, and config to AI agents.
      MIT

    • Binary Ninja MCP Server

      rsprudencio
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that enables Large Language Models to interact with Binary Ninja for reverse engineering tasks like viewing assembly code, decompiled code, renaming functions, and adding comments.
      3
      MIT
    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.2/5.0

    Scored across 37 tools

    Disambiguation4/5

    Most tools have distinct purposes, but execute and execute_command overlap significantly; also generate_beacon and generate_implant could be confused despite their descriptions. Overall, an agent can distinguish most tools.

    Naming Consistency5/5

    Naming uses a consistent snake_case with verb_noun pattern (e.g., list_beacons, kill_job). Common unix-like commands (cd, ls, rm) fit the pattern and are expected. No mixing of styles.

    Tool Count3/5

    37 tools is high but justified for a C2 framework covering listeners, implants, sessions, beacons, file ops, and noise management. Some redundancy (execute vs execute_command) suggests potential for consolidation.

    Completeness4/5

    Covers essential C2 operations: connect, manage listeners, generate implants, control sessions/beacons, file operations, event polling, and handoff import/export. Minor gaps like editing implant profiles, but core workflows are complete.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources