Skip to content

Add MseeP.ai badge#500

Open
mseep-ai wants to merge 1 commit intodataelement:mainfrom
mseep-ai:add-mseep-badge
Open

Add MseeP.ai badge#500
mseep-ai wants to merge 1 commit intodataelement:mainfrom
mseep-ai:add-mseep-badge

Conversation

@mseep-ai
Copy link
Copy Markdown

Hi there,

This pull request shares a security update on Clawith.

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

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

Thanks,

The MseeP Team
MCP servers you can trust


MseeP.ai Security Assessment Badge

Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: e97e008412

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Comment thread README.md
@@ -1,3 +1,5 @@
[![MseeP.ai Security Assessment Badge](https://mseep.net/pr/dataelement-clawith-badge.png)](https://mseep.ai/app/dataelement-clawith)
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Remove untrusted third-party badge asset

This adds a README badge that hotlinks an image from mseep.net, so every README view triggers a request to infrastructure outside this project’s control. That creates a persistent privacy/supply-chain risk (viewer metadata leakage and mutable content if that host changes or is compromised) and can also break the top of the README if the domain goes down; use a repository-hosted asset or another trusted, project-controlled badge source instead.

Useful? React with 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant