algorithmaide-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_hook_packsB | List built-in hook templates that can be applied to a target app. |
| read_target_stateC | Read the current target state, including config, AppSwitch, log sources, and LSPosed scope. |
| apply_algorithm_aide_configC | Write files/config/.json safely and verify the config provider readback. |
| add_custom_hooksC | Add or replace custom hook entries, then sync config, AppSwitch, LSPosed, and optionally relaunch the target. |
| sync_appswitch_stateC | Sync AppSwitch.json and logList.json, then verify both storage layers. |
| sync_lsposed_scopeC | Sync the LSPosed scope for AlgorithmAide and return the readback. |
| replace_frida_scriptC | Replace a Frida script under /data/system/junge//frida and verify the write. |
| collect_runtime_logsD | Collect runtime logs, prioritizing the SQLite database and frida.log. |
| search_hook_logsC | Search the structured hook log database by keyword across class, method, details, and call stack fields. |
| get_hook_log_contextB | Expand one structured hook log entry into a short surrounding time-window context. |
| inspect_hook_candidateC | Summarize one dynamic candidate into short hits, short context, jadx-ai-mcp hints, and draft add_custom_hooks suggestions. |
| query_hook_logsC | Pull runtime logs and query recent hook records from algorithmAidePro.db and frida.log. |
| query_agent_logsC | Build a short unified log view from sqlite hits, short context, and frida.log supplements. |
| query_frida_logsC | Pull frida.log and view a short keyword or time-window slice. |
| inject_frida_scriptC | Enable one Frida script for a target package and sync config, AppSwitch, and LSPosed in one step. |
| run_verified_workflowC | Run the minimal verified loop: stop apps, write state, start AlgorithmAide, sync LSPosed, then optionally launch the target. |
| add_r0capture_hooksC | Generate the built-in r0capture-style network hooks and apply them with the verified workflow. |
| reset_target_configC | Reset the target config to an empty template and apply it through the verified workflow. |
| save_hook_profileC | Save a hook configuration profile locally. |
| list_hook_profilesA | List locally saved hook configuration profiles. |
| apply_hook_profileC | Load a saved profile and apply it with the verified workflow. |
| import_hook_jsonB | Low-level config import for compatibility. Prefer apply_algorithm_aide_config for normal use. |
| collect_exported_logsC | Compatibility tool for pulling legacy exported log files only. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/vwww-droid/algorithmaide-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server