SecAIQ Watch shows which AI tools run on your Mac, what files and permissions they can reach, which MCP servers they use and where their traffic goes. Read-only, 100% local, no account. 14-day free trial, then $19.99/year.
SecAIQ Watch for Mac already recognizes the common AI coding tools, agents, MCP servers and IDE extensions. New ones appear every month, so the list is never finished.
Which tool do you use that you would want it to recognize? Tell me the name and what you'd want to see about it (its permissions, the servers it talks to, its config files).
SecAIQ Watch checks AI tools for risky settings, for example auto-approve modes, over-broad file access, unknown MCP servers and API keys left in config files. It shows the finding, never a copy of the secret.
If you had to pick, which of these worries you most? And is there a risk I'm not checking yet?
A monitoring app has to earn trust, so here is the short version.
It reads: running AI-tool processes and their start-up flags, config and settings files of AI tools, which servers they connect to, and usage logs the tools write themselves. Everything is stored on your Mac.
Hi Product Hunt, I'm Safa, the maker of SecAIQ Watch. Some of you may know the free open-source edition I launched here last month. This is its native Mac sibling, built from your feedback.
AI coding agents, desktop assistants and MCP servers now run on our Macs with our own user rights. They read project files, run shell commands and talk to the network. I wanted plain answers to three questions and couldn't find one place that gave them:
What AI tools are running on my Mac?
What can they reach?
Where does their data go?
SecAIQ Watch is a native Mac app that answers them, on your machine:
Finds about 37 AI tool families (Claude Code and Desktop, Codex, Cursor, Windsurf, Copilot, Gemini CLI, Ollama, LM Studio, MCP servers, IDE extensions and more)
Permissions matrix: what each tool can access, what it actually did, and what changed since your first scan
Network activity per tool: destinations and data volumes, plus a session incident report you can export
Approvals view: spots risky start-up flags such as --dangerously-skip-permissions
Plain-language findings with evidence, and a posture grade from A to F
What it is not: monitoring is read-only. It never blocks, intercepts or changes anything on its own. There is no cloud analysis, no account for monitoring, and no prompts or file contents are collected. Everything stays on your Mac. The app only contacts secaiq.com to check your license and look for updates.
It has limits, and I say so in the app: file access is sampled, very short-lived processes can be missed, and a setting shows what a tool is configured to do, not proof of how it behaves. The screenshots here use the built-in demo data.
Pricing: 14-day free trial (no card, no account), then $19.99/year for one Mac. For Product Hunt: 50% off the first year for the first 50 buyers, applied automatically at checkout. A Windows version is in development. There is also a free open-source PHP edition on GitHub for macOS, Linux and Windows.
I'd love your feedback: which AI tools should I add next, and which risks should it flag first? I'll be here all day answering questions.
Report
Maker
I’ll be honest, I’m feeling a little disappointed and confused by how quiet this launch has been.
I built SecAIQ Watch for Mac entirely on my own, investing considerable time and effort into creating a security tool for the growing AI coding ecosystem.
What makes this particularly confusing is that I've seen another open-source app in a similar space, with a more limited feature set, receive around 65 upvotes here on Product Hunt.
Meanwhile, SecAIQ Watch for Mac has received just 3.
I'm genuinely trying to understand why. Is it the way I presented the product? Did I launch at the wrong time? Am I simply not reaching the right audience?
I'm not expecting hundreds of upvotes, and I know nobody owes me their support. But as an independent developer, it's difficult not to question what went wrong when something you've worked so hard on barely gets noticed.
I'd genuinely appreciate some honest feedback from the community. What am I missing?
Even constructive criticism would mean more to me than silence.
Thanks to everyone who took the time to check out SecAIQ Watch. 💙
Report
Maker
SecAIQ Watch for Mac 1.4.0 is out. What's new:
• Topology map: one picture of your AI tools, the MCP servers they load and the providers they connect to. Moving dots are connections open right now.
• Access view: which tool reaches which sensitive area (SSH keys, secrets, Full Disk Access, shell...), whether it was seen in use, granted by settings or inherited, plus the access paths to look at first.
• Developer security report (HTML export): what to fix first, what each AI tool can reach, MCP server trust and recent permission changes.
• Five more tools recognised: Trae, Void, Cherry Studio, Chatbox and Perplexity Comet.
Still read-only, 100% local, no account. Screens and details: secaiq.com/watch. Feedback is very welcome.
Hi Product Hunt, I'm Safa, the maker of SecAIQ Watch. Some of you may know the free open-source edition I launched here last month. This is its native Mac sibling, built from your feedback.
AI coding agents, desktop assistants and MCP servers now run on our Macs with our own user rights. They read project files, run shell commands and talk to the network. I wanted plain answers to three questions and couldn't find one place that gave them:
What AI tools are running on my Mac?
What can they reach?
Where does their data go?
SecAIQ Watch is a native Mac app that answers them, on your machine:
Finds about 37 AI tool families (Claude Code and Desktop, Codex, Cursor, Windsurf, Copilot, Gemini CLI, Ollama, LM Studio, MCP servers, IDE extensions and more)
Permissions matrix: what each tool can access, what it actually did, and what changed since your first scan
Network activity per tool: destinations and data volumes, plus a session incident report you can export
Approvals view: spots risky start-up flags such as --dangerously-skip-permissions
Plain-language findings with evidence, and a posture grade from A to F
What it is not: monitoring is read-only. It never blocks, intercepts or changes anything on its own. There is no cloud analysis, no account for monitoring, and no prompts or file contents are collected. Everything stays on your Mac. The app only contacts secaiq.com to check your license and look for updates.
It has limits, and I say so in the app: file access is sampled, very short-lived processes can be missed, and a setting shows what a tool is configured to do, not proof of how it behaves. The screenshots here use the built-in demo data.
Pricing: 14-day free trial (no card, no account), then $19.99/year for one Mac. For Product Hunt: 50% off the first year for the first 50 buyers, applied automatically at checkout. A Windows version is in development. There is also a free open-source PHP edition on GitHub for macOS, Linux and Windows.
I'd love your feedback: which AI tools should I add next, and which risks should it flag first? I'll be here all day answering questions.
I’ll be honest, I’m feeling a little disappointed and confused by how quiet this launch has been.
I built SecAIQ Watch for Mac entirely on my own, investing considerable time and effort into creating a security tool for the growing AI coding ecosystem.
What makes this particularly confusing is that I've seen another open-source app in a similar space, with a more limited feature set, receive around 65 upvotes here on Product Hunt.
Meanwhile, SecAIQ Watch for Mac has received just 3.
I'm genuinely trying to understand why. Is it the way I presented the product? Did I launch at the wrong time? Am I simply not reaching the right audience?
I'm not expecting hundreds of upvotes, and I know nobody owes me their support. But as an independent developer, it's difficult not to question what went wrong when something you've worked so hard on barely gets noticed.
I'd genuinely appreciate some honest feedback from the community. What am I missing?
Even constructive criticism would mean more to me than silence.
Thanks to everyone who took the time to check out SecAIQ Watch. 💙
SecAIQ Watch for Mac 1.4.0 is out. What's new:
• Topology map: one picture of your AI tools, the MCP servers they load and the providers they connect to. Moving dots are connections open right now.
• Access view: which tool reaches which sensitive area (SSH keys, secrets, Full Disk Access, shell...), whether it was seen in use, granted by settings or inherited, plus the access paths to look at first.
• Developer security report (HTML export): what to fix first, what each AI tool can reach, MCP server trust and recent permission changes.
• Five more tools recognised: Trae, Void, Cherry Studio, Chatbox and Perplexity Comet.
Still read-only, 100% local, no account. Screens and details: secaiq.com/watch. Feedback is very welcome.