‹ directory
89MCP SCORE
B

agentstack

https://agentstack.tech/mcp
1 tools4 resources65 prompts~1.8k tok/req100% annot.proto 2026-07-28
View public page ›
Xin
Raw JSON ›

Score by pillar

Security ·20100
Tool design ·18100
Schemas / desc ·1680
Reliability ·14100
Context-cost ·1273
Compliance ·12100
Coverage ·860

reliability: LOW (T1 single-shot, not credited - requires T3 >=24h)

Context-cost

1.8ktokens for tools/list

Paid on every request. Lean footprint for 1 tools.

this server1.8k
median≈ 3k

MCP primitive coverage

the quality score covers tools
1
Tools
4
Resources
65
Prompts

Badge — paste it in your README

MCP Score badge — agentstack[![MCP Score](https://checkmcp.dev/badge/agentstack-tech.svg?url=https%3A%2F%2Fagentstack.tech%2Fmcp)](https://checkmcp.dev/report?url=https%3A%2F%2Fagentstack.tech%2Fmcp)

About agentstack — FAQ

Is the agentstack MCP server safe to use?+
CheckMCP audited agentstack and gave it an MCP Score of 89/100 (grade B) — good — only minor issues. 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 agentstack?+
agentstack scores 89/100 (grade B) 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 agentstack expose, and what is its context cost?+
agentstack exposes 1 tool, and its tools/list response costs roughly 1.8k tokens — paid on every request your agent makes to it. Lower is better for your context budget.
How was agentstack scored?+
By probing the live MCP endpoint (https://agentstack.tech/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.