Memory Shell Detector MCP
Related Servers
Alternatives to Memory Shell Detector MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceLets AI agents diagnose and debug live Java applications by auto-discovering JVMs and attaching Arthas to run diagnostic commands like thread, trace, watch, and ognl.2MIT
- AlicenseAqualityCmaintenanceEnables AI agents to execute commands on remote servers via SSH with dynamic host discovery through JumpServer and automatic username fallback.6MIT
- AlicenseBqualityCmaintenanceСonnects to live JVMs via JDWP protocol, enabling LLM agents to autonomously debug Java applications — attach to a running process, pause threads, set breakpoints (including conditional), inspect stacks with auto-resolved object fields, evaluate methods, set variable values, and diagnose issues like deadlocks and hung queries.281MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to securely execute remote commands via SSH or JumpServer, with flexible gateway configuration and plugin-based matchers for JumpServer login interfaces.1Apache 2.0
- AlicenseAqualityBmaintenanceEnables AI agents to securely connect to and manage remote servers via SSH, with tools for running commands, file operations, log inspection, service management, and system monitoring under configurable access controls and audit logging.1215 npm1MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to manage remote servers via SSH, including command execution, multi-host batch operations, SFTP file transfer, background job handling, DevOps diagnostics, port tunneling, and safety guardrails like high-risk command blocking and read-only mode.MIT
TDQS
Scored across 9 tools
Each tool has a distinct purpose: network check, download, command execution, report export, system info, process listing, scanning, code viewing, and removal. No overlap exists, and descriptions clearly differentiate them.
Most tools follow verb_noun pattern (check_network, download_detector_tools, export_report, etc.). One outlier, get_system_info_tool, uses 'get' instead of a consistent verb and adds redundant '_tool', slightly breaking consistency.
With 9 tools, the server covers the full workflow from preparation (check, download) to detection (list, scan, view) to remediation (remove, report). The count is well-scoped and not excessive.
The toolset covers the entire memory shell detection lifecycle: network check, tool download, process listing, scanning, code review, removal, and report generation. No obvious gaps for the stated purpose.