MCP Risk

Directory / server

app.2ools/mcp

This directory entry reports an automated security scan of app.2ools/mcp, scanned 2026-07-28. Trust grade B rates provenance, transport, known vulnerabilities and instruction integrity; capability risk is reported separately, not folded into the grade.

registry.modelcontextprotocol.io, scanned 2026-07-28, tool surface via remote-tools-list

B 83/100 permalink

Automated checks

StatusCheckPolicyResult
PASS Listed on the official MCP registry §1.1
Listed on registry.modelcontextprotocol.io as app.2ools/mcp. 1 finding
  • Registry entry: app.2ools/mcp ↗
WARN Source repository is public and maintained §1.2

No public source repository could be identified for this server.
INFO Published package is consistent and attested §1.3

No published package associated with this server (remote-only or non-npm/PyPI source).
PASS Tool surface is inspectable and proportionate §2.1–§2.4
40 tool(s) enumerated; no high-risk capability signals. 2 findings
  • Tools exposed: 40
  • Detected capabilities: none
PASS HTTPS-only endpoint §3.1
Endpoint uses HTTPS. 1 finding
  • Endpoint: https://2ools.app/mcp
WARN Authentication required §3.2

Server answers anonymous requests (HTTP 200). Acceptable only for deliberately public, read-only (Low) servers.
PASS OAuth protected-resource metadata published §3.3
Publishes /.well-known/oauth-protected-resource per the June 2025 authorization spec. 1 finding
  • Authorization server: https://2ools.app
INFO No known vulnerabilities (OSV.dev) §4.1

No package to query (remote-only server).
PASS Server-supplied instructions free of poisoning indicators §5.1–§5.4

No poisoning indicators found across 72 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.