Add MseeP.ai badge

[lwsinclair]

Hi there,

This pull request shares a security update on zen-mcp-server.

We also have an entry for zen-mcp-server 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 zen-mcp-server.

You can easily take control over your listing for free: visit it at https://mseep.ai/app/beehiveinnovations-zen-mcp-server.

Yours Sincerely,

Lawrence W. Sinclair
CEO/SkyDeck AI
Founder of MseeP.ai
MCP servers you can trust

---

Here are our latest evaluation results of zen-mcp-server

Security Scan Results

Security Score: 100/100

Risk Level: low

Scan Date: 2025-06-17

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

Security Findings

Low Severity Issues

• semgrep: Use of base64 decoding detected. This might indicate obfuscated code.
• ... and 1 more low 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.

[gemini-code-assist]

Summary of Changes

Hello @lwsinclair, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request integrates a MseeP.ai security assessment badge into the project's README.md file. The primary purpose is to provide users with a quick, third-party validated overview of the zen-mcp-server's security posture, as assessed by MseeP.ai.

Highlights

• README Update: Added a MseeP.ai security assessment badge to the very top of the README.md file. This badge serves as a visual indicator of the project's security status as assessed by MseeP.ai, linking directly to the detailed assessment page.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in issue comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist is currently in preview and may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments to provide feedback.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request adds a security badge from MseeP.ai to the README.md. My review focuses on the security and maintainability implications of this change.

The primary concern is the unsolicited nature of this PR, which appears to be for promotional purposes. I've raised a high-severity issue regarding the need to verify the legitimacy of the external service before adding their badge, as this has security implications for the project and its users.

Additionally, I've provided a suggestion to improve the placement of the badge to align with common markdown style conventions, should you decide to merge this change.

[gemini-code-assist]

Hello! Thank you for your contribution.

This pull request appears to be from an external service to add a promotional badge. While we appreciate the interest in our project, we need to be cautious about adding external links and endorsements from unsolicited PRs.

• Security and Trust: Before merging, I strongly recommend verifying the legitimacy and value of MseeP.ai. Adding badges from unvetted sources can pose a security risk to our users (e.g., phishing, tracking) and affect the project's credibility.

• Placement and Style: From a stylistic perspective, badges are conventionally placed after the main H1 header, not before it. This improves the document's structure and readability.

If you decide to keep the badge after verification, I suggest moving it below the main title as follows:

Suggested change

	[](https://mseep.ai/app/beehiveinnovations-zen-mcp-server)
	# Zen MCP: Many Workflows. One Context.
	# Zen MCP: Many Workflows. One Context.
	[](https://mseep.ai/app/beehiveinnovations-zen-mcp-server)