Add MseeP.ai badge

[lwsinclair]

Hi there,

This pull request shares a security update on mcp-openapi-schema-explorer.

We also have an entry for mcp-openapi-schema-explorer 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 mcp-openapi-schema-explorer.

You can easily take control over your listing for free: visit it at https://mseep.ai/app/kadykov-mcp-openapi-schema-explorer.

Yours Sincerely,

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

---

Here are our latest evaluation results of mcp-openapi-schema-explorer

Security Scan Results

Security Score: 100/100

Risk Level: low

Scan Date: 2025-04-29

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.

[Copilot]

Pull Request Overview

This PR adds a security assessment badge provided by MseeP.ai to the README, showcasing the validated security score for mcp-openapi-schema-explorer.

• Added a markdown badge linking to the MseeP.ai security review
• Inserts the badge at the top of the README for immediate visibility

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

see 1 file with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[kadykov]

Hi Lawrence,

Thank you for scanning the MCP server for security issues, and for your PR adding the MseeP security badge to the README.

The badge you proposed is quite large and visually prominent, which tends to shift the focus from the project to the badge itself. While it does include the "Audited" label, it doesn’t provide much detail beyond stating that the project was reviewed by MseeP — so it's not very informative in terms of ongoing security status.

To keep the README clean and consistent with standard practices, I’d prefer using a smaller, more standard-sized badge that fits in alongside the others. I've added a MseeP verification badge next to the existing badges in the README — feel free to check it out.

Thanks again for your contribution!

Best regards,
Aleksandr Kadykov