LASIK
Score = points from our five tests (install, handshake, maintenance, docs, license). Not a quality or security rating. Methodology
- Install20/20
- Handshake30/30
- Maintenance25/25
- Docs10/15
- License10/10
New / early find
New / early find: first tested 2026-11-11. Tested npm lasik-agents 0.3.0 (MIT; repo pktq/lasik, 83 GitHub stars when tested, created 2026-11-09; not listed on Glama or mcp.so when checked, PulseMCP not checked). Static deobfuscator that strips BLA anti-agent hardening so coding agents can read a protected build; it never runs the input. `lasik mcp` over stdio: initialize and tools/list succeeded with no credentials and listed 4 tools. Real calls on a 2-line local JS test file: lasik_scan, lasik_read, lasik_heal (wrote a cleaned copy) and lasik_firewall all returned isError false. The test file had no BLA protection, so the deobfuscation itself was not exercised, and lasik_firewall returned our planted 'IGNORE ALL PREVIOUS INSTRUCTIONS' sentence unredacted.
Tool-call test (2026-11-11, direct MCP stdio client, no LLM): pass. 4 of 4 calls returned without error. Deobfuscation on a BLA-protected build not tested. Evidence: local test run, Nov 11, 2026.
Transport (tested 2026-11-11): stdio
Token cost (estimate): approx. 499 tokens, cl100k estimate (4 tools, measured 2026-11-11, version 0.3.0). This is an estimate from our testing of the tool names, descriptions and input schemas, counted with cl100k_base.
Permissions: 3 read, 1 write (state-changing), 0 unclassified · Auth: none · Rate limit: unknown · Pricing unit: unknown
Auth: none. Rate limit: unknown. Pricing unit: unknown.
lasik_firewall— readlasik_heal— write (state-changing)lasik_read— readlasik_scan— read
handshake and tools listed without a recorded key or OAuth
Score 95/100 · Tools 4 · Token cost approx. 499 tokens · Compare · Last tested 2026-11-11 · Version tested 0.3.0 · Package lasik-agents · Repo pktq/lasik
Summary: LASIK completed an MCP handshake without credentials and exposed 4 tools.
Evidence summary
- Handshake
- pass
- Tools listed
- 4
- Context cost
- approx. 499 tokens, cl100k estimate (4 tools, measured 2026-11-11, version 0.3.0; an estimate) ranking · add up your servers' context cost
- API key
- No key needed for the tools we called
- Tested
- 2026-11-11
Test results
| Test | Result | Points | Evidence |
|---|---|---|---|
| install | pass | 20 | npm install lasik-agents (Node 20, Linux) succeeded in 1s. |
| handshake | pass | 30 | MCP initialize + tools/list over stdio succeeded with no credentials; 4 tools listed in 0.2s. |
| maintenance | pass | 25 | Repo pushed 1 days before test; 83 GitHub stars. |
| docs | partial | 10 | README over 3,000 chars; install instructions present. Check of the package's own README (README shipped in npm package). |
| license | pass | 10 | MIT (OSI-approved). |
Local-model readiness
Token cost (estimate): approx. 499 tokens, cl100k estimate for 4 tools · about 6% of an 8k context. This is an estimate from our testing (counted with cl100k_base).
Small-model friendly (schema heuristic, not a model result): unknown.
Not tested
Small-model task runs: Not yet tested.
What we tested and what we didn't
Tested on 2026-11-11
- Install from the registry
- We connected with no credentials and asked for its tool list: it listed 4 tools (Method details: MCP
initializethentools/list) - Maintenance signals (last push, archived/deprecated status)
- Docs (README length, install and config example)
- License (OSI-approved or not)
- Token cost (estimate)
Not tested
- Security: not audited (no code review, no permission or data-flow analysis)
- Real tasks (no functional task runs yet)
- Behaviour with real credentials or a real account
- Performance, rate limits or load
- Correctness of results beyond the listed tasks
Methodology: how we test. A high score means it installs and responds, not that giving it access to your data carries no risk.
Known security issues
Not yet checked.
Monthly roundup: MCP security issues, October 2026.
Tool list changes
Baseline recorded from the 2026-11-11 test run; changes appear after the next test.
Snapshot hash (fingerprint of the tool list)
cf5ca17b5401: SHA-256 of the canonical tool names, descriptions and input schemas. If it changes, the tool list changed.
Raw test record (JSON)
{
"name": "lasik-agents",
"version": "0.3.0",
"registry": "npm",
"status": "working",
"tested": "2026-11-11",
"tools_count": 4,
"deprecated": false,
"archived": false,
"tests": {
"install": [
"pass",
20,
"`npm install lasik-agents` (Node 20, Linux) succeeded in 1s."
],
"handshake": [
"pass",
30,
"MCP `initialize` + `tools/list` over stdio succeeded with no credentials; 4 tools listed in 0.2s."
],
"maintenance": [
"pass",
25,
"Repo pushed 1 days before test; 83 GitHub stars."
],
"docs": [
"partial",
10,
"README over 3,000 chars; install instructions present. Check of the package's own README (README shipped in npm package)."
],
"license": [
"pass",
10,
"MIT (OSI-approved)."
]
}
}Install
npx -y lasik-agents mcp
Pin the version we tested
npx -y lasik-agents@0.3.0 mcp
tested 2026-11-11. Newer versions may differ and were not tested by us.
{
"mcpServers": {
"lasik": {
"command": "npx",
"args": [
"-y",
"lasik-agents@0.3.0",
"mcp"
]
}
}
}Tools listed
lasik_firewall, lasik_heal, lasik_read, lasik_scan
Tool history: captured Nov 11, 2026. All tool history.
Quick config
{
"mcpServers": {
"lasik": {
"command": "npx",
"args": [
"-y",
"lasik-agents",
"mcp"
]
}
}
}Add to config Opens the config generator with this server selected.
Setup
- Install. Run
npm install lasik-agents(Node 20). This is the exact command we ran on 2026-11-11. - Configure. Add the mcpServers entry below to your MCP client config.
- Verify. Restart the client and check that tools/list returns tools (4 in our test).
{
"mcpServers": {
"lasik": {
"command": "npx",
"args": [
"-y",
"lasik-agents",
"mcp"
]
}
}
}Test history
- 2026-11-11: New
FAQ
Is LASIK deprecated?
No. lasik-agents was not deprecated or archived when we last tested it on 2026-11-11.
What replaces LASIK?
Nothing; LASIK is not deprecated as of 2026-11-11.
Does LASIK need an API key?
No. It completed an MCP handshake with no credentials and listed 4 tools.
Embed the badge
Every tested server gets a free embeddable badge. It shows the current score and test date and expires after 90 days. Testing is free; payment never changes a score.