Conversation
JiwaniZakir
left a comment
There was a problem hiding this comment.
The badge is added at the very top of README.md (line 1), which places it above the ## DISCLAIMER: section — arguably the most important content for new users of this project. Consider moving it after the disclaimer, or grouping it with other project metadata badges if any are added in the future, so it doesn't visually bury critical project context. Also worth noting: the badge image is served from mseep.net while the link target points to mseep.ai — two different domains — which could be a reliability concern if either domain changes independently. Finally, the badge lacks any surrounding context in the README explaining what MseeP.ai is or what the assessment covers, which may leave readers uncertain about its significance.
Hi there,
This pull request shares a security update on WilmerAI.
We also have an entry for WilmerAI 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 WilmerAI.
You can easily take control over your listing for free: visit it at https://mseep.ai/app/someoddcodeguy-wilmerai.
Yours Sincerely,
Lawrence W. Sinclair
CEO/SkyDeck AI
Founder of MseeP.ai
MCP servers you can trust
Here are our latest evaluation results of WilmerAI
Security Scan Results
Security Score: 74/100
Risk Level: moderate
Scan Date: 2025-06-18
Score starts at 100, deducts points for security issues, and adds points for security best practices
Security Findings
Medium Severity Issues
semgrep: Avoiding SQL string concatenation: untrusted input concatenated with raw SQL query can result in SQL Injection. In order to execute raw query safely, prepared statement should be used. SQLAlchemy provides TextualSQL to easily used prepared statement with named parameters. For complex SQL composition, use SQL Expression Language or Schema Definition Language. In most cases, SQLAlchemy ORM will be a better option.
semgrep: Avoiding SQL string concatenation: untrusted input concatenated with raw SQL query can result in SQL Injection. In order to execute raw query safely, prepared statement should be used. SQLAlchemy provides TextualSQL to easily used prepared statement with named parameters. For complex SQL composition, use SQL Expression Language or Schema Definition Language. In most cases, SQLAlchemy ORM will be a better option.
... and 3 more medium severity issues
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.