io.github.lintsure/lintsure
Lintsure
Is the Lintsure MCP server down? No. It answered initialize and tools/list in the probe of 2026-11-14.
Compliance readiness checks for code: EU AI Act, GDPR, OWASP, CWE, Cyber Resilience Act. Local.
alive probed 2026-11-14
- Run it
- npx -y @lintsure/mcp@0.3.10 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Reports itself as
- lintsure 0.3.10
- Capabilities
- prompts, tools
- Instructions
- 2 274 characters
- Of a 1M window
- 0.3 % of a 1M context window
- Count
- 2.8k tokens in Claude Opus 5.5, exact, measured 2026-11-14. With the Claude Code prefix mcp__…__ on each tool name: 2.9k. The o200k_base estimate is 1.7k. Counted again when the tool definitions change. Method.
- Repository
- https://github.com/lintsure/lintsure
- Website
- https://lintsure.com/docs/mcp
- Registry
- active, updated 2026-11-13 · registry entry
- Changes
- 4 recorded, reachable in 4 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.65×.
| Tool | ≈ Claude tokens | o200k estimate | Share of this server |
|---|---|---|---|
| classify | 1 262 | 767 | 45 % |
| scan | 900 | 547 | 32 % |
| explain_framework | 380 | 231 | 13 % |
| explain_rule | 283 | 172 | 10 % |
Compare this server with others.
More servers
Other registry entries on npmjs.com, the ones next to this name; all of them.
- io.github.liminalpepe/x402-repohealth-mcp · alive
- LemonLDAP::NG MCP Server io.github.linagora/llng-mcp · alive
- io.github.linhnnmt/genai-capture · install failed
- Linq io.github.linq-team/linq · alive
- DeepThonk io.github.linxule/deepthonk · alive
- MinerU io.github.linxule/mineru · alive
- liquefy-ui io.github.liquefy-ui/liquefy-ui · alive
- io.github.lisamaraventano-spine/firstdollar · alive
Servers that mention compliance or resilience.
- BlueNexus Universal MCP ai.bluenexus/universal-mcp · needs auth
- Clarid Compliance ai.clarid/compliance · no DNS
- Duskly ai.duskly/duskly · alive
- ai.kanonik/kanonik · needs auth
- ai.ssid/ssid-mcp · alive
- ThinkNEO Control Plane ai.thinkneo/control-plane · no DNS
- ClearPolicy app.clearpolicy/clearpolicy · needs auth
- EuroComply — EU Regulatory Compliance app.eurocomply/compliance · alive
History
We add a row when the result changes. A server with no change keeps its last row.
| Probed | Result | Init | Tools | Claude | o200k |
|---|---|---|---|---|---|
| 2026-11-14 08:08 | alive | 290 ms | 4 | 2.8k | 1.7k |
| 2026-11-11 08:29 | alive | 310 ms | 4 | 2.4k | 1.5k |
| 2026-11-09 08:45 | alive | 234 ms | 4 | 952 | 522 |
| 2026-11-08 08:04 | alive | 222 ms | 4 | 936 | 512 |
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 server answers initialize and tools/list. Nothing to fix.