Automagik Tools MCP Server

automagik-tools PyPI v0.9.19

Published by namastexlabs — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

A monorepo package for MCP tools with dynamic loading capabilities - featuring Evolution API v2 WhatsApp integration

Trust grade
A
93/100
Last scanned get badge →
Trust
A · 93/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
High
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 93/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 7 = 93. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−6 capability blast radius (high) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 4

high Shell/command execution in server code (automagik_tools/cli.py)MTC-SRC-002

In the server's implementation (`automagik_tools/cli.py:576`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: script result = subprocess.run(cmd, capture_output=True, text=True) if result.returncode == 0:

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server automagik_tools/cli.py

medium Untrusted input can drive an external actionMTC-FLOW-005

Untrusted-input tools ([download_media, read_messages, download_document]) co-exist with external-action tools ([send_message]). A prompt injection could cause unwanted external actions, though no direct sensitive-data leak path was found.

Evidence: untrusted [download_media, read_messages, download_document] → sinks [send_message]

Fix: Require confirmation for state-changing/egress actions triggered after processing untrusted content.

Location: flow download_media → send_message

low Shell/command execution in packaging/dev tooling (tests/test_cli_simple.py)MTC-SRC-002

In a packaging/dev/install script (shipped, but not the server runtime) (`tests/test_cli_simple.py:47`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: t help result = subprocess.run( ["python", "-c", "from automagik_tools.cli import app; app(['--help'

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server tests/test_cli_simple.py

low Shell/command execution in packaging/dev tooling (tests/test_integration.py)MTC-SRC-002

In a packaging/dev/install script (shipped, but not the server runtime) (`tests/test_integration.py:115`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: "0"} process = subprocess.Popen( [ sys.executable, "-m",

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server tests/test_integration.py

Tools 153

Each tool and what it can reach — statically extracted from the published source.

  • download_documentingests untrusted input
  • download_mediaingests untrusted input
  • read_messagesingests untrusted input
  • send_messagenetwork egress
  • access_mcp_resourceno sensitive capability
  • activate_promptno sensitive capability
  • add_contactno sensitive capability
  • add_sourceno sensitive capability
  • ask_genieno sensitive capability
  • call_mcp_toolno sensitive capability
Show 143 more tools ↓
  • chat_agentno sensitive capability
  • check_is_whatsappno sensitive capability
  • check_new_messagesno sensitive capability
  • check_playground_statusno sensitive capability
  • check_workflow_progressno sensitive capability
  • configure_mcp_serversno sensitive capability
  • connection_statusno sensitive capability
  • consult_geminino sensitive capability
  • continue_agent_conversationno sensitive capability
  • convert_json_to_docsno sensitive capability
  • create_instanceno sensitive capability
  • create_mcp_serverno sensitive capability
  • create_memories_batchno sensitive capability
  • create_memoryno sensitive capability
  • create_promptno sensitive capability
  • create_scheduleno sensitive capability
  • create_userno sensitive capability
  • deactivate_promptno sensitive capability
  • delete_agent_conversationno sensitive capability
  • delete_mcp_serverno sensitive capability
  • delete_memoryno sensitive capability
  • delete_messageno sensitive capability
  • delete_promptno sensitive capability
  • delete_scheduleno sensitive capability
  • delete_sessionno sensitive capability
  • delete_sourceno sensitive capability
  • delete_taskno sensitive capability
  • delete_team_collaborationno sensitive capability
  • delete_userno sensitive capability
  • delete_workflowno sensitive capability
  • delete_workflow_executionno sensitive capability
  • disable_scheduleno sensitive capability
  • enable_scheduleno sensitive capability
  • end_sessionno sensitive capability
  • execute_workflowno sensitive capability
  • extract_placeholdersno sensitive capability
  • find_chatsno sensitive capability
  • find_messageno sensitive capability
  • find_personno sensitive capability
  • genie_clear_memoriesno sensitive capability
  • genie_memory_statsno sensitive capability
  • get_claude_code_healthno sensitive capability
  • get_claude_code_run_statusno sensitive capability
  • get_gemini_requestsno sensitive capability
  • get_group_membersno sensitive capability
  • get_healthno sensitive capability
  • get_health_statusno sensitive capability
  • get_instance_infono sensitive capability
  • get_mcp_healthno sensitive capability
  • get_mcp_serverno sensitive capability
  • get_memoryno sensitive capability
  • get_promptno sensitive capability
  • get_remote_workflowno sensitive capability
  • get_run_statusno sensitive capability
  • get_scheduleno sensitive capability
  • get_service_infono sensitive capability
  • get_session_historyno sensitive capability
  • get_sourceno sensitive capability
  • get_specific_agent_conversationno sensitive capability
  • get_taskno sensitive capability
  • get_team_collaboration_detailsno sensitive capability
  • get_team_detailsno sensitive capability
  • get_userno sensitive capability
  • get_workflowno sensitive capability
  • get_workflow_detailsno sensitive capability
  • get_workflow_execution_detailsno sensitive capability
  • hub_infono sensitive capability
  • list_agent_mcp_toolsno sensitive capability
  • list_agentsno sensitive capability
  • list_all_channelsno sensitive capability
  • list_all_groupsno sensitive capability
  • list_available_agentsno sensitive capability
  • list_available_teamsno sensitive capability
  • list_available_workflowsno sensitive capability
  • list_claude_code_workflowsno sensitive capability
  • list_mcp_server_resourcesno sensitive capability
  • list_mcp_server_toolsno sensitive capability
  • list_mcp_serversno sensitive capability
  • list_memoriesno sensitive capability
  • list_mounted_toolsno sensitive capability
  • list_promptsno sensitive capability
  • list_remote_workflowsno sensitive capability
  • list_schedulesno sensitive capability
  • list_sessionsno sensitive capability
  • list_sourcesno sensitive capability
  • list_tasksno sensitive capability
  • list_templatesno sensitive capability
  • list_usersno sensitive capability
  • list_workflowsno sensitive capability
  • manage_chatsno sensitive capability
  • manage_contactsno sensitive capability
  • manage_instancesno sensitive capability
  • manage_profilesno sensitive capability
  • manage_tracesno sensitive capability
  • my_connectionsno sensitive capability
  • my_contactsno sensitive capability
  • my_conversationsno sensitive capability
  • my_whatsapp_infono sensitive capability
  • react_withno sensitive capability
  • remove_contactno sensitive capability
  • rename_agent_conversationno sensitive capability
  • rename_team_collaborationno sensitive capability
  • rename_workflow_executionno sensitive capability
  • restart_mcp_serverno sensitive capability
  • run_agentno sensitive capability
  • run_agent_asyncno sensitive capability
  • run_claude_code_workflowno sensitive capability
  • run_workflowno sensitive capability
  • searchno sensitive capability
  • send_audiono sensitive capability
  • send_contactno sensitive capability
  • send_locationno sensitive capability
  • send_mediano sensitive capability
  • send_pollno sensitive capability
  • send_presenceno sensitive capability
  • send_reactionno sensitive capability
  • send_stickerno sensitive capability
  • send_text_messageno sensitive capability
  • send_whatsappno sensitive capability
  • share_documentno sensitive capability
  • start_agent_conversationno sensitive capability
  • start_google_authno sensitive capability
  • start_mcp_serverno sensitive capability
  • start_team_collaborationno sensitive capability
  • stop_mcp_serverno sensitive capability
  • sync_workflowno sensitive capability
  • talkno sensitive capability
  • update_contactno sensitive capability
  • update_mcp_serverno sensitive capability
  • update_memoryno sensitive capability
  • update_messageno sensitive capability
  • update_promptno sensitive capability
  • update_scheduleno sensitive capability
  • update_sourceno sensitive capability
  • update_userno sensitive capability
  • upload_templateno sensitive capability
  • validate_json_datano sensitive capability
  • view_agent_conversation_historyno sensitive capability
  • view_agent_memoriesno sensitive capability
  • view_team_collaboration_historyno sensitive capability
  • view_team_memoriesno sensitive capability
  • view_workflow_execution_historyno sensitive capability
  • wait_minutesno sensitive capability

Toxic flows 1

Cross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.9.19 latest A 93/100 4 1.13.0 2026-08-25

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 93/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/automagik-tools/badge.svg)](https://mcptrustchecker.com/registry/automagik-tools)
HTML
<a href="https://mcptrustchecker.com/registry/automagik-tools"><img src="https://mcptrustchecker.com/registry/automagik-tools/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/automagik-tools/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan automagik-tools --online --registry pypi

Use the free API → How scoring works

More in Productivity & Workflow