io.github.degibug-del/laserbrain
PYPI · LASERBRAIN · SCANNED SEP 21
The drift harness as an MCP server. Offline, no key — a fixed reference an agent checks against.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs setuptools.build_meta at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency6
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 21 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 427 tokens (~61/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
- Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage81
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 43% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
How do I install the io.github.degibug-del/laserbrain MCP server?
io.github.degibug-del/laserbrain runs locally as a PyPI package, launched with uvx laserbrain. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · laserbrain
claude mcp add degibug-del-laserbrain -- uvx laserbrain
{
"mcpServers": {
"degibug-del-laserbrain": {
"command": "uvx",
"args": [
"laserbrain"
]
}
}
} {
"servers": {
"degibug-del-laserbrain": {
"command": "uvx",
"args": [
"laserbrain"
]
}
}
} codex mcp add degibug-del-laserbrain -- uvx laserbrain
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"degibug-del-laserbrain": {
"type": "local",
"command": [
"uvx",
"laserbrain"
],
"enabled": true
}
}
} openclaw mcp add degibug-del-laserbrain --command uvx --arg laserbrain
mcp_servers:
degibug-del-laserbrain:
command: "uvx"
args: ["laserbrain"] {
"McpServers": {
"degibug-del-laserbrain": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"laserbrain"
]
}
}
} assistant mcp add degibug-del-laserbrain -t stdio -c uvx -a laserbrain
{
"mcpServers": {
"degibug-del-laserbrain": {
"command": "uvx",
"args": [
"laserbrain"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Sept 26 +16
- Malware scan: unverified → pass ▲ security
- 19 Sept 26 −3
- Stability: pass → 0.77 functional
- 18 Sept 26 −14
- Malware scan: pass → unverified ▼ security
- Stability: 0.97 → pass security
- 16 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 −3
- Stability: pass → 0.80 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Sept 2026 · Analysed pypi/laserbrain@0.29.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
capabilities ~21
What this server can do offline, and what needs the hosted one.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
check_state ~113
Spell where you are. The FIRST call freezes the ground — every later reading is measured against it, which is what makes this different from asking yourself. Call it each step. Returns one of nine verdicts, Φ, and what to do.
| Name | Type | Req | Description |
|---|---|---|---|
| distance | number | – | How far from done, 0-10. 0 means finished. |
| goal | string | yes | What you are working on, in your own words. |
| progress | string | – | Honestly. A false "advancing" wastes the reading. |
No output schema declared.
No examples provided.
get_history ~32
The checks spelled so far this session, and how many were drifting.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Default 20. |
No output schema declared.
No examples provided.
laserscore ~45
The compact one-line reading of a state, without setting or touching a ground.
| Name | Type | Req | Description |
|---|---|---|---|
| distance | number | – | – |
| goal | string | yes | – |
| progress | string | – | – |
No output schema declared.
No examples provided.
modulate ~118
Check your state AND get the intervention your role should take. Same verdict as check_state, plus a policy decision: whether THIS role returns on THIS drift, and the wording to return with. Pass team + role for a recursion-team preset; without them every drift returns, unstyled. Offline, like everything else here.
| Name | Type | Req | Description |
|---|---|---|---|
| distance | number | – | – |
| goal | string | yes | – |
| progress | string | – | – |
| role | string | – | Which role this agent is playing. |
| team | string | – | A recursion-team preset name. |
No output schema declared.
No examples provided.
reset_task ~52
Start a genuinely new task. Clears the ground so the next check_state sets a fresh one. Use when the user redirects you — NOT to escape a drift verdict, which is the one thing that makes the reading useless.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
similarity ~46
Token overlap between two statements under the same normaliser the harness uses. Useful for asking whether two goals are the same goal.
| Name | Type | Req | Description |
|---|---|---|---|
| a | string | yes | – |
| b | string | yes | – |
No output schema declared.
No examples provided.
What is the io.github.degibug-del/laserbrain MCP server?
io.github.degibug-del/laserbrain is an MCP server listed in the public MCP registry as io.github.degibug-del/laserbrain. The drift harness as an MCP server. Offline, no key, a fixed reference an agent checks against. This page covers its PyPI package (laserbrain).
Is the io.github.degibug-del/laserbrain MCP server safe to use?
io.github.degibug-del/laserbrain scores 69 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.degibug-del/laserbrain MCP server expose?
io.github.degibug-del/laserbrain exposes 7 tools: check_state, modulate, reset_task, get_history, similarity, and 2 more. Their descriptions and schemas cost roughly 427 tokens of context every time the server is loaded.
Is the io.github.degibug-del/laserbrain MCP server still maintained?
io.github.degibug-del/laserbrain is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.