72hours security check
Server Details
Scan a public GitHub repo, explain risks, get fix prompts and rescan to confirm fixes.
The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
- Status
- Unhealthy
- Uptime
- 0.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- maebsy/YMCA-hackathon-2026
- GitHub Stars
- 0
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 15 tools
Most tools have distinct lifecycle roles, and descriptions clarify the difference between one-call audit_repository, lower-level start_scan/get_scan, rescan, and check_fix. There is still some overlap among scan/status/audit tools because several tools can expose scan state or trigger scanning, but the boundaries are generally workable.
The set is mostly consistent snake_case with clear verb_noun patterns such as create_workspace, start_scan, get_analysis, and generate_report. A few names deviate from the pattern, notably rescan, incident_report, and service_info, but they remain readable and unambiguous.
Fifteen tools is a well-scoped size for a security auditing workflow that includes workspace management, scanning, GPU analysis, fix verification, reporting, and demo verification. Each tool appears to earn its place rather than bloating the surface.
The tool set covers the full workflow from service discovery and workspace creation through scanning, polling, analysis, fix-prompt retrieval, rescanning after fixes, demo verification, reporting, and incident drafting. The only intentional limitation is that incident reporting is draft-only, which is clearly stated and not a functional gap.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Read-only scan of a public GitHub repo for leaked secrets, with a 0-100 grade.
Screens public GitHub repos and PRs to generate risk maps, findings, and merge-readiness signals.
Scan a GitHub repository for vulnerabilities, with proof for every finding, from your coding agent.
Audit and repair any public GitHub repo. Free survey; paid source, unified diffs and a pull request.
Related MCP Servers
- AlicenseNot gradedqualityAmaintenanceDetect live website vulnerabilities and security flaws in GitHub repositories using automated DAST and SAST scanning. Safeguard applications by identifying exposed secrets, insecure dependencies, and common code patterns prone to exploitation. Receive structured fix plans with precise code remediation steps to resolve identified risks and improve security posture.2MIT
- FlicenseNot gradedqualityCmaintenanceScans GitHub repositories for security vulnerabilities by cloning, performing static analysis, secret detection, build verification, and AI-powered OWASP-aligned code review, producing a scored SECURITY.md report.-
- AlicenseNot gradedqualityCmaintenanceEnables auditing public GitHub repositories over MCP Streamable HTTP, including classifying URLs, cloning repositories, scanning manifests, CI workflows, and credential signals, and producing findings, file trees, summaries, and PDF reports.MIT
- AlicenseAqualityBmaintenanceSecurity checks for apps built with AI coding tools (Lovable, Bolt, Cursor, Claude Code). Scans a public GitHub repo for open Supabase tables, exposed keys, unprotected server functions and unverified webhooks, and returns each finding with the file and a fix prompt.2419 npmMIT
Glama MCP Gateway
Add one secure layer between your agents and this server.