coding-agent-audit 0.3.0__tar.gz → 0.3.2__tar.gz

{coding_agent_audit-0.3.0/src/coding_agent_audit.egg-info → coding_agent_audit-0.3.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: coding-agent-audit
-Version: 0.3.0
+Version: 0.3.2
 Summary: Scan your machine for known AI-coding-assistant supply-chain backdoor indicators (Claude Code / Cursor / Windsurf extensions, MCP servers) plus risky hook/permission config patterns. Usable as a CLI or as an MCP server.
 Author-email: StackScribe AI <survivalagent320@gmail.com>
 License: MIT
@@ -21,6 +21,8 @@ Dynamic: license-file
 
 # coding-agent-audit
 
+<!-- mcp-name: io.github.stackscribe-ai/coding-agent-audit -->
+
 A small, open-source CLI that scans your machine for:
 
 1. **Known indicators of compromise (IOCs)** from publicly documented
@@ -131,14 +133,15 @@ any MCP client. Add this to your client's MCP config (e.g. Claude Desktop's
   "mcpServers": {
     "coding-agent-audit": {
       "command": "uvx",
-      "args": ["--from", "coding-agent-audit", "agent-audit-mcp"]
+      "args": ["coding-agent-audit"]
     }
   }
 }
 ```
 
 (No `uv`? `pip install coding-agent-audit` then use `"command": "agent-audit-mcp"`
-with no `args`.) This exposes two tools, `scan_for_known_backdoors` and
+with no `args` — same server, explicit entry-point name.) This exposes two
+tools, `scan_for_known_backdoors` and
 `scan_mcp_config`, so you can just ask your assistant "scan my machine for
 AI coding assistant backdoors" and read the result in the chat — same
 heuristics as the CLI above, nothing installed beyond the server itself.

{coding_agent_audit-0.3.0 → coding_agent_audit-0.3.2}/README.md

@@ -1,5 +1,7 @@
 # coding-agent-audit
 
+<!-- mcp-name: io.github.stackscribe-ai/coding-agent-audit -->
+
 A small, open-source CLI that scans your machine for:
 
 1. **Known indicators of compromise (IOCs)** from publicly documented
@@ -110,14 +112,15 @@ any MCP client. Add this to your client's MCP config (e.g. Claude Desktop's
   "mcpServers": {
     "coding-agent-audit": {
       "command": "uvx",
-      "args": ["--from", "coding-agent-audit", "agent-audit-mcp"]
+      "args": ["coding-agent-audit"]
     }
   }
 }
 ```
 
 (No `uv`? `pip install coding-agent-audit` then use `"command": "agent-audit-mcp"`
-with no `args`.) This exposes two tools, `scan_for_known_backdoors` and
+with no `args` — same server, explicit entry-point name.) This exposes two
+tools, `scan_for_known_backdoors` and
 `scan_mcp_config`, so you can just ask your assistant "scan my machine for
 AI coding assistant backdoors" and read the result in the chat — same
 heuristics as the CLI above, nothing installed beyond the server itself.

{coding_agent_audit-0.3.0 → coding_agent_audit-0.3.2}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "coding-agent-audit"
-version = "0.3.0"
+version = "0.3.2"
 description = "Scan your machine for known AI-coding-assistant supply-chain backdoor indicators (Claude Code / Cursor / Windsurf extensions, MCP servers) plus risky hook/permission config patterns. Usable as a CLI or as an MCP server."
 readme = "README.md"
 requires-python = ">=3.9"
@@ -30,6 +30,7 @@ Homepage = "https://github.com/stackscribe-ai/coding-agent-audit"
 [project.scripts]
 agent-audit = "agentaudit.cli:main"
 agent-audit-mcp = "agentaudit.mcp_server:main"
+coding-agent-audit = "agentaudit.mcp_server:main"
 
 [tool.setuptools.packages.find]
 where = ["src"]

{coding_agent_audit-0.3.0 → coding_agent_audit-0.3.2}/src/agentaudit/__init__.py

@@ -3,4 +3,4 @@ for AI coding assistants (Claude Code, Cursor, Windsurf, VS Code forks, MCP
 servers).
 """
 
-__version__ = "0.3.0"
+__version__ = "0.3.2"

{coding_agent_audit-0.3.0 → coding_agent_audit-0.3.2/src/coding_agent_audit.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: coding-agent-audit
-Version: 0.3.0
+Version: 0.3.2
 Summary: Scan your machine for known AI-coding-assistant supply-chain backdoor indicators (Claude Code / Cursor / Windsurf extensions, MCP servers) plus risky hook/permission config patterns. Usable as a CLI or as an MCP server.
 Author-email: StackScribe AI <survivalagent320@gmail.com>
 License: MIT
@@ -21,6 +21,8 @@ Dynamic: license-file
 
 # coding-agent-audit
 
+<!-- mcp-name: io.github.stackscribe-ai/coding-agent-audit -->
+
 A small, open-source CLI that scans your machine for:
 
 1. **Known indicators of compromise (IOCs)** from publicly documented
@@ -131,14 +133,15 @@ any MCP client. Add this to your client's MCP config (e.g. Claude Desktop's
   "mcpServers": {
     "coding-agent-audit": {
       "command": "uvx",
-      "args": ["--from", "coding-agent-audit", "agent-audit-mcp"]
+      "args": ["coding-agent-audit"]
     }
   }
 }
 ```
 
 (No `uv`? `pip install coding-agent-audit` then use `"command": "agent-audit-mcp"`
-with no `args`.) This exposes two tools, `scan_for_known_backdoors` and
+with no `args` — same server, explicit entry-point name.) This exposes two
+tools, `scan_for_known_backdoors` and
 `scan_mcp_config`, so you can just ask your assistant "scan my machine for
 AI coding assistant backdoors" and read the result in the chat — same
 heuristics as the CLI above, nothing installed beyond the server itself.

{coding_agent_audit-0.3.0 → coding_agent_audit-0.3.2}/src/coding_agent_audit.egg-info/entry_points.txt

@@ -1,3 +1,4 @@
 [console_scripts]
 agent-audit = agentaudit.cli:main
 agent-audit-mcp = agentaudit.mcp_server:main
+coding-agent-audit = agentaudit.mcp_server:main