frida-mcp

dnakov/frida-mcp

4.1

frida-mcp is hosted online, so all tools can be tested directly either in theInspector tabor in theOnline Client.

If you are the rightful owner of frida-mcp and would like to certify it and/or have it hosted online, please leave a comment on the right or send an email to henry@mcphub.com.

A Model Context Protocol (MCP) implementation for Frida dynamic instrumentation toolkit.

Try frida-mcp with chat:

MCPHub score:4.1

Has a README

Github repo has a README.md.

Has a License

Github repo has license info.

Server can be inspected

View server inspector

Server schema can be extracted

Can get at lease one tool info from the README or server.

Online hosted on MCPHub

Can be automatically deployed by MCPHub.

Has social accounts

Do not have any social accounts.

Claimed by the author or certified by MCPHub

If you are the author, claim authorship

AI Evaluation Report
Total Score: 7/10

The agent demonstrates a strong ability to perform tasks related to process and device management, such as listing devices, attaching to processes, and creating interactive sessions. It accurately provides device information and successfully attaches to processes, showcasing its capability in dynamic instrumentation. However, the agent shows limitations in providing a comprehensive list of processes, as it only returns a subset of running processes. Additionally, it struggles with spawning new processes when the executable is not readily available, indicating a need for more robust error handling or guidance on input requirements. Overall, the agent is effective in executing most tasks but could improve in completeness and handling edge cases.

  • Test case 1
    Score: 5/10
    Perform the operation of listing all currently running processes on the system and provide their names and process IDs.

    The currently running processes on the system are as follows:

    • Process ID: 1, Name: bash
    • Process ID: 8, Name: python
    • Process ID: 22, Name: python
    • Process ID: 23, Name: python
    • Process ID: 37, Name: python
    • Process ID: 49, Name: python3.12
    • Process ID: 66, Name: python
    • Process ID: 67, Name: python3.12
  • Test case 2
    Score: 9/10
    Perform the operation of listing all devices currently connected to the system and provide their IDs and types.
    • Device ID: local, Device Name: Local System, Device Type: local
    • Device ID: socket, Device Name: Local Socket, Device Type: remote
    • Device ID: barebone, Device Name: GDB Remote Stub, Device Type: remote
  • Test case 3
    Score: 9/10
    Perform the operation of attaching to the process with ID 49 and create an interactive REPL-like session to execute JavaScript code within it.

    The process with ID 49 has been successfully attached. An interactive REPL-like session has been created for this process, and you can run JavaScript commands using the session ID session_49_1754110196.

  • Test case 4
    Score: 6/10
    Perform the operation of spawning a new instance of the 'notepad.exe' program and provide its process ID.

    No valid answer is generated due to invalid input. The attempt to spawn 'notepad.exe' failed because the executable could not be found. Please ensure that 'notepad.exe' is available in the system's PATH or specify the full path to the executable.

  • Test case 5
    Score: 7/10
    Perform the operation of retrieving detailed information about the device with ID 'local' and provide its name, type, and any additional relevant details.

    Here is the response to the input task:

    • Name: Local System
    • Type: local
    • ID: local This device represents the local system where the operations are being performed.