Directory / server
ai.sugra/api-mcp
This directory entry reports an automated security scan of ai.sugra/api-mcp, scanned 2026-07-28. Trust grade A rates provenance, transport, known vulnerabilities and instruction integrity; capability risk is reported separately, not folded into the grade.
Automated checks
| Status | Check | Policy | Result |
|---|---|---|---|
| PASS | Listed on the official MCP registry | §1.1 | Listed on registry.modelcontextprotocol.io as ai.sugra/api-mcp. 1 finding
|
| PASS | Source repository is public and maintained | §1.2 | Active repository with a license. 5 findings
|
| WARN | Published package is consistent and attested | §1.3 | Minor integrity gaps: no PyPI trusted-publishing provenance. 5 findings
|
| PASS | Tool surface is inspectable and proportionate | §2.1–§2.4 | 11 tool(s) enumerated; no high-risk capability signals. 2 findings
|
| PASS | HTTPS-only endpoint | §3.1 | Endpoint uses HTTPS. 1 finding
|
| UNVERIFIABLE | Authentication required | §3.2 | Endpoint rejected the probe (HTTP 400); whether it requires authentication could not be determined. |
| PASS | OAuth protected-resource metadata published | §3.3 | Publishes /.well-known/oauth-protected-resource per the June 2025 authorization spec. 1 finding
|
| PASS | No known vulnerabilities (OSV.dev) | §4.1 | No advisories on record for sugra-api-mcp @0.9.1 (PyPI). |
| PASS | Server-supplied instructions free of poisoning indicators | §5.1–§5.4 | No poisoning indicators found across 23 server-supplied text item(s). |
What this grade covers
- Provenance & supply-chain integrity (§1)
- Tool surface & capability risk (§2)
- Transport & authentication (§3)
- Known CVEs via OSV.dev (§4)
- Instruction/tool poisoning patterns (§5)
Limitations: pattern-based only (no semantic injection detection), static npm analysis (live server instructions not retrieved for package-only scans), single-server scope (no cross-server toxic flow analysis). See the full policy.
Methodology: MCP Server Security Policy. Unfamiliar term? See the glossary.