‹ directory
79MCP SCORE
C
loophole tape
https://api.loopholetape.com/mcp
34 tools5 resources4 prompts~11k tok/req100% annot.proto 2026-07-28
Score by pillar
Security ·20100
Tool design ·1838
Schemas / desc ·16100
Reliability ·1480
Context-cost ·1253
Compliance ·12100
Coverage ·880
reliability: LOW (T1 single-shot, not credited - requires T3 >=24h)
Context-cost
11ktokens for
tools/listPaid on every request. Lean footprint for 34 tools.
this server11k
median≈ 3k
MCP primitive coverage
the quality score covers tools34
Tools
5
Resources
4
Prompts
Suggested composite optimizations
rhc_swap_build_checked ↔ swap_build_checked →
renommer pour distinguerBadge — paste it in your README
[](https://checkmcp.dev/report?url=https%3A%2F%2Fapi.loopholetape.com%2Fmcp)Own this server?Get verified — fresh re-audit, badge if you pass ›
About loophole tape — FAQ
Is the loophole tape MCP server safe to use?+
CheckMCP audited loophole tape and gave it an MCP Score of 79/100 (grade C) — moderate — some quality or security gaps worth reviewing. The audit runs an OWASP MCP Top 10 security pass (tool poisoning, hardcoded secrets, command injection, the lethal trifecta) against the live endpoint; see the per-pillar breakdown and the "why this score" attribution on this page, and re-audit anytime at checkmcp.dev.
What is the MCP Score of loophole tape?+
loophole tape scores 79/100 (grade C) on CheckMCP's vendor-neutral audit across six weighted pillars — security, tool design, schemas, context-cost, compliance and coverage — with reliability measured and shown but not yet credited.
How many tools does loophole tape expose, and what is its context cost?+
loophole tape exposes 34 tools, and its tools/list response costs roughly 11k tokens — paid on every request your agent makes to it. Lower is better for your context budget.
How was loophole tape scored?+
By probing the live MCP endpoint (https://api.loopholetape.com/mcp), inspecting its tools, schemas and protocol compliance, running an OWASP MCP Top 10 security pass, and measuring the token cost of tools/list — then attributing every penalty as measure → mechanism → effect. The methodology is open: checkmcp.dev/#methodology.