-
Notifications
You must be signed in to change notification settings - Fork 5
Add MseeP.ai badge #4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
WalkthroughA security assessment badge linked to the MseeP.ai security page was added at the top of the README file. No other files or functional code were changed. Changes
Poem
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 0
🧹 Nitpick comments (1)
README.md (1)
1-2: External badge fetch may leak visitor IPs – consider a shields.io proxy or cached assetFetching the badge directly from
https://mseep.net/...on every page view causes each reader’s browser to hit that domain, disclosing IP / referrer information to a third-party. GitHub security guidelines recommend serving badges through a proxy (e.g.,https://img.shields.io/…) or committing a static image into the repo to minimise tracking surface.If privacy is a concern, replace the remote URL with a shields.io endpoint or host the PNG in the repo:
-[](https://mseep.ai/app/manascb1344-together-mcp-server) +[](https://mseep.ai/app/manascb1344-together-mcp-server)This keeps the README self-contained and avoids unintentional telemetry.
Hi there,
This pull request shares a security update on together-mcp-server.
We also have an entry for together-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 together-mcp-server.
You can easily take control over your listing for free: visit it at https://mseep.ai/app/manascb1344-together-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 together-mcp-server
Security Scan Results
Security Score: 100/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
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 CodeRabbit