‹ directory
79MCP SCORE
C
portos
https://api.portoperatingsystem.com/mcp
10 tools~110k tok/req100% annot.proto 2026-07-28
Score by pillar
Security ·20100
Tool design ·1885
Schemas / desc ·1690
Reliability ·1480
Context-cost ·1233
Compliance ·1272
Coverage ·870
reliability: LOW (T1 single-shot, not credited - requires T3 >=24h)
Context-cost
110ktokens for
tools/listPaid on every request. Lean footprint for 10 tools.
this server110k
median≈ 3k
MCP primitive coverage
the quality score covers tools10
Tools
0
Resources · none
0
Prompts · none
Why this score — causal attribution
Each penalty: measure → mechanism → effect → Δscore.
Context-cost · HIGH−10.6
~110k tokens (≥p95) → tool defs are paid on EVERY request → exhausts the window + ongoing cost
Compliance · MEDIUM−3.4
JSON-RPC-compliant errors 0/2 → errors not compliant with the JSON-RPC spec → clients break unpredictably
Suggested composite optimizations
subscription_inspect ↔ subscription_list →
renommer pour distinguerBadge — paste it in your README
[](https://checkmcp.dev/report?url=https%3A%2F%2Fapi.portoperatingsystem.com%2Fmcp)Own this server?Get verified — fresh re-audit, badge if you pass ›
About portos — FAQ
Is the portos MCP server safe to use?+
CheckMCP audited portos 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 portos?+
portos 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 portos expose, and what is its context cost?+
portos exposes 10 tools, and its tools/list response costs roughly 110k tokens — paid on every request your agent makes to it. Lower is better for your context budget.
How was portos scored?+
By probing the live MCP endpoint (https://api.portoperatingsystem.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.