dev.assurly/mcp-server
assurly
Pre-deploy ship gate AI agents call before shipping. Also audits the agent's own MCP config.
alive probed 2026-10-19
5tools
≈ 640tokens, estimate
≈ 0.3 %of Claude's 200k window
0.4×the median server
507 msto initialize
7 msto list tools
- Run it
- npx -y @assurly/mcp-server@1.2.2 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Reports itself as
- assurly 1.2.2
- Capabilities
- tools
- Instructions
- 129 characters
- Of a 1M window
- ≈ <0.1 % of a 1M context window, estimate
- Claude count
- The count_tokens endpoint refused the tool schemas: invalid x-api-key. The estimate stands in.
- Website
- https://assurly.dev/mcp
- Registry
- active, updated 2026-08-22 · registry entry
- Reachable
- 1 of the last 1 probe
Most expensive tools
Estimates with the o200k_base tokenizer.
| Tool | o200k estimate | Share of this server |
|---|---|---|
| assurly_verdict | 199 | 31 % |
| assurly_scan_files | 134 | 21 % |
| assurly_scan_agent | 126 | 20 % |
| assurly_explain_rule | 91 | 14 % |
| assurly_scan_path | 90 | 14 % |
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
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
- The Anthropic count_tokens endpoint refused the tool schemas (invalid x-api-key). A client that validates schemas can refuse them too.