Add MseeP.ai badge

[mseep-ai]

Hi there,

This pull request shares a security update on Claude-Code-Agent-Monitor.

We also have an entry for Claude-Code-Agent-Monitor in our directory, MseeP.ai, where we provide regular security and trust updates on your app.

We invite you to add our badge for your MCP server to your README to help your users learn from a third party that provides ongoing validation of Claude-Code-Agent-Monitor.

You can easily take control over your listing for free: visit it at https://mseep.ai/app/hoangsonww-claude-code-agent-monitor.

Thanks,

The MseeP Team
MCP servers you can trust

---

Here are our latest evaluation results of Claude-Code-Agent-Monitor

Security Scan Results

Security Score: 38/100

Risk Level: critical

Scan Date: 2026-07-04

Score starts at 100, deducts points for security issues, and adds points for security best practices

Detected Vulnerabilities

High Severity

• concurrently

  • ['shell-quote']
  • Fixed in version: unknown

• shell-quote

  • [{'source': 1120422, 'name': 'shell-quote', 'dependency': 'shell-quote', 'title': 'shell-quote quote() does not escape newlines in object .op values', 'url': 'https://github.com/advisories/GHSA-w7jw-789q-3m8p', 'severity': 'critical', 'cwe': ['CWE-77', 'CWE-78'], 'cvss': {'score': 8.1, 'vectorString': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H'}, 'range': '>=1.1.0 <=1.8.3'}]
  • Fixed in version: unknown

Medium Severity

• @redocly/openapi-core

  • ['js-yaml']
  • Fixed in version: unknown

• body-parser

  • ['qs']
  • Fixed in version: unknown

• express

  • ['qs']
  • Fixed in version: unknown

• ... and 7 more medium severity vulnerabilities

Security Findings

Medium Severity Issues

• semgrep: Insecure WebSocket Detected. WebSocket Secure (wss) should be used for all WebSocket connections.

  • Location: README-CN.md
  • Line: 1226

• semgrep: Insecure WebSocket Detected. WebSocket Secure (wss) should be used for all WebSocket connections.

  • Location: README-VN.md
  • Line: 1234

• ... and 6 more medium severity issues

This security assessment was conducted by MseeP.ai, an independent security validation service for MCP servers. Visit our website to learn more about our security reviews.

[github-actions]

Thank you for your submission, we really appreciate it. Like many open-source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution. You can sign the CLA by just posting a Pull Request Comment same as the below format.

---

I have read the CLA Document and I hereby sign the CLA

---

_{You can retrigger this bot by commenting recheck in this Pull Request. Posted by the CLA Assistant Lite bot.}

[gemini-code-assist]

Code Review

This pull request adds a security assessment badge to the top of the README.md file. The reviewer suggests moving this badge below the main heading to follow standard markdown practices and prevent potential issues with document parsing, accessibility, and SEO.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[gemini-code-assist]

Placing badges above the main document heading (# Agent Dashboard for Claude Code) is not standard markdown practice and can negatively impact document parsing, accessibility, and SEO. It is highly recommended to place the badge below the main heading or group it with the other existing badges starting at line 9.

To fix this, please remove the badge from the very top of the file and place it below the main heading instead.

[hoangsonww]

i know this may be automatically created but many "vulnerabilities" are quoted from the READMEs... E.g.

Medium Severity Issues

semgrep: Insecure WebSocket Detected. WebSocket Secure (wss) should be used for all WebSocket connections.

Location: README-CN.md
Line: 1226
semgrep: Insecure WebSocket Detected. WebSocket Secure (wss) should be used for all WebSocket connections.

Location: README-VN.md
Line: 1234

And also since this is intended to be local-only this repo is not really affected by these "vulnerabilities"...