‹ directory
93MCP SCORE
A
tera-studio
https://terastudio.co/mcp
4 tools1 resources~1.9k tok/req100% annot.proto 2026-07-28
Score by pillar
Security ·20100
Tool design ·18100
Schemas / desc ·16100
Reliability ·14100
Context-cost ·1273
Compliance ·12100
Coverage ·860
reliability: LOW (T1 single-shot, not credited - requires T3 >=24h)
Context-cost
1.9ktokens for
tools/listPaid on every request. Lean footprint for 4 tools.
this server1.9k
median≈ 3k
MCP primitive coverage
the quality score covers tools4
Tools
1
Resources
0
Prompts · none
Why this score — causal attribution
Each penalty: measure → mechanism → effect → Δscore.
Compliance · LOW−0.6
no OAuth discovery (.well-known missing) → RFC 9728/8414 not exposed → auth not auto-discoverable by clients
Badge — paste it in your README
[](https://checkmcp.dev/report?url=https%3A%2F%2Fterastudio.co%2Fmcp)Own this server?Get verified — fresh re-audit, badge if you pass ›
About tera-studio — FAQ
Is the tera-studio MCP server safe to use?+
CheckMCP audited tera-studio and gave it an MCP Score of 93/100 (grade A) — strong — no blocking security or design issues were found. 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 tera-studio?+
tera-studio scores 93/100 (grade A) 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 tera-studio expose, and what is its context cost?+
tera-studio exposes 4 tools, and its tools/list response costs roughly 1.9k tokens — paid on every request your agent makes to it. Lower is better for your context budget.
How was tera-studio scored?+
By probing the live MCP endpoint (https://terastudio.co/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.