mcpcost

com.securealy/mcp

Securealy

Is the Securealy MCP server down? No. It answered initialize and tools/list in the probe of 2026-10-27.

Grade a URL as an attacker and a customer would see it; scan a repo; check Supabase, Stripe, Vercel.

alive probed 2026-11-14 · unchanged since 2026-10-27

9tools
3.3ktokens in Claude Opus 5.5
1.6 %of Claude's 200k window
1.3×the median server
634 msto initialize
50 msto list tools
Run it
npx -y securealy-mcp@0.1.6 (stdio, probed in a container with the network off)
Host
npmjs.com
Reports itself as
securealy 0.1.6
Capabilities
resources, tools
Instructions
840 characters
Of a 1M window
0.3 % of a 1M context window
Count
3.3k tokens in Claude Opus 5.5, exact, measured 2026-10-27. With the Claude Code prefix mcp__…__ on each tool name: 3.3k. The o200k_base estimate is 2.0k. Counted again when the tool definitions change. Method.
Repository
https://github.com/securealy/securealy
Website
https://securealy.com
Registry
active, updated 2026-10-14 · registry entry
Changes
2 recorded, reachable in 2 of them. A row is added when the result, the tool count or the cost changes.

Most expensive tools

The Claude column scales the o200k estimate of each tool by this server's ratio of exact to estimate, 1.63×.

Tool≈ Claude tokenso200k estimateShare of this server
grade_url90255228 %
scan_repo39524212 %
check_rls39023912 %
check_vercel_env36422311 %
post_result32319810 %

Compare this server with others.

More servers

Other registry entries on npmjs.com, the ones next to this name; all of them.

Servers that mention attacker or customer.

History

We add a row when the result changes. A server with no change keeps its last row.

ProbedResultInitToolsClaudeo200k
2026-10-27 06:51alive494 ms93.3k2.0k
2026-10-20 06:39alive634 ms92.0k

Badge for the README

mcpcost: alive

The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.

Atom feed

A mail when this server changes

Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.

For the publisher