Add MseeP.ai badge

[lwsinclair]

Hi there,

This pull request shares a security update on evo-ai.

We also have an entry for evo-ai 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 evo-ai.

You can easily take control over your listing for free: visit it at https://mseep.ai/app/evolutionapi-evo-ai.

Yours Sincerely,

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

---

Here are our latest evaluation results of evo-ai

Security Scan Results

Security Score: 93/100

Risk Level: low

Scan Date: 2025-06-13

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 4 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.

Summary by Sourcery

Documentation:

• Add MseeP.ai security assessment badge with link to the detailed report in the project README

[sourcery-ai]

Reviewer's Guide

This PR adds a MseeP.ai security assessment badge to the project README, enabling users to quickly view third-party security validation and risk metrics for evo-ai.

File-Level Changes

Change	Details	Files
Introduce MseeP.ai security badge in README	Inserted linked badge markdown snippet at the top of the file Added blank line separation before the project title	README.md

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey @lwsinclair - I've reviewed your changes and they look great!

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[jbmendonca]

Noting that PR #40 targets the same MseeP.ai badge addition and has been open longer (307 days). Both PRs appear identical in scope. Could a maintainer confirm which one should be merged and close the other to avoid a double-apply?

[jbmendonca]

Olá!

Este PR (#43) é uma duplicata do PR #40 — ambos adicionam o badge do MseeP.ai e foram enviados pelo mesmo autor (@lwsinclair).

Como o PR #40 foi aberto antes, sugerimos que os mantenedores definam qual será mantido. Se este (#43) for o preferido (por estar mais atualizado ou conter ajustes adicionais), o PR #40 pode ser encerrado. Caso contrário, este pode ser fechado para consolidar o histórico.

Obrigado!