Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.
How we verified
Verified is a snapshot. Live keeps it current, and builds your track record.
⚡ Connect GitHub → continuous verification on every pushwhy connect →Who stands behind it
aws-samples
Source: github_code
Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →
Install from
M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.
GIT_PR_MCP_LOG_LEVELno info debug, info, warn, or errorGIT_PR_MCP_TRANSPORTno stdio stdio or sseGITLAB_URLexport ="https://gitlab.example.com"SSO_SESSION_URLno https://your-sso-provider.example.com/api/session-status Endpoint that returns HTTP 200 while the SSO session is validSSO_COOKIE_PATHno ~/.sso/cookie Netscape-format cookie file written by your SSO provider's CLIGITLAB_TOKENexport ="<your-gitlab-pat-with-read_api-scope>"Tool annotations
No tools have read-only/destructive annotations
Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.
All four hints declared on every tool
10/10 tools missing one or more hints — list_pull_requests (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_pull_request_details (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); filter_pull_requests (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +7 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.
For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.
Tool test coverage
Only 2/10 tools referenced in tests (20%)
Write tests that reference each tool by name so every tool has at least one test.
Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.
[](https://m8ven.ai/mcp/aws-samples-sample-mcp-git-1h7xcl)?variant=verified to the badge URL.Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.
https://m8ven.ai/api/mcp/tool-check