io.github.labarilem/brainfaq-mcp
NPM · BRAINFAQ-MCP · SCANNED SEP 20
MCP server for the BrainFuck programming language
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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency31
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: the license (Attribution-ShareAlike 4.0 International) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 245 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability74
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 301 tokens (~50/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage85
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 56% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "step" implies "execute" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.labarilem/brainfaq-mcp server?
io.github.labarilem/brainfaq-mcp runs locally as an npm package, launched with npx -y brainfaq-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · brainfaq-mcp
claude mcp add labarilem-brainfaq-mcp -- npx -y brainfaq-mcp
{
"mcpServers": {
"labarilem-brainfaq-mcp": {
"command": "npx",
"args": [
"-y",
"brainfaq-mcp"
]
}
}
} {
"servers": {
"labarilem-brainfaq-mcp": {
"command": "npx",
"args": [
"-y",
"brainfaq-mcp"
]
}
}
} codex mcp add labarilem-brainfaq-mcp -- npx -y brainfaq-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"labarilem-brainfaq-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"brainfaq-mcp"
],
"enabled": true
}
}
} openclaw mcp add labarilem-brainfaq-mcp --command npx --arg -y --arg brainfaq-mcp
mcp_servers:
labarilem-brainfaq-mcp:
command: "npx"
args: ["-y", "brainfaq-mcp"] {
"McpServers": {
"labarilem-brainfaq-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"brainfaq-mcp"
]
}
}
} assistant mcp add labarilem-brainfaq-mcp -t stdio -c npx -a -y brainfaq-mcp
{
"mcpServers": {
"labarilem-brainfaq-mcp": {
"command": "npx",
"args": [
"-y",
"brainfaq-mcp"
]
}
}
} 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.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 −2
- Stability: pass → 0.83 functional
- 16 Sept 26 0
- Stability: 0.97 → pass security
- 15 Sept 26 +1
- Security disclosure: unverified → fail ▼ functional
- 14 Sept 26 0
- Security disclosure: fail → unverified ▼ functional
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 −3
- Stability: pass → 0.77 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 20 Sept 2026 · Analysed npm/brainfaq-mcp@1.0.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| 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 →
add_input ~35
Append characters to input buffer. Use when status is WAITING_FOR_INPUT. Outputs the engine status.
| Name | Type | Req | Description |
|---|---|---|---|
| input | string | yes | – |
No output schema declared.
No examples provided.
get_state ~60
Get the current full state (memory, pointers, output). When windowRadius is not specified, returns the entire tape which may be a large amount of data.
| Name | Type | Req | Description |
|---|---|---|---|
| windowRadius | number | – | Optional radius around data pointer. When omitted, returns entire tape. |
No output schema declared.
No examples provided.
load_code ~101
Reset the debugger and load new Brainfuck source code.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | – |
| initial_input | string | – | – |
| maxValue | number | – | Maximum allowed value for tape cells (default: 9007199254740991) |
| minValue | number | – | Minimum allowed value for tape cells (default: -9007199254740991) |
| tapeSize | integer | – | Size of the memory tape (default: 30000) |
No output schema declared.
No examples provided.
read_output ~17
Get the full output string generated so far.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
run ~54
Run the program until it finishes or waits for input. Infinite loops WILL hang the server. Then outputs the summary of the current state.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Optional limit if you still want one. Omit to run forever. |
No output schema declared.
No examples provided.
step ~34
Execute a specific number of instructions (default 1). Then outputs the summary of the current state.
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | – | – |
No output schema declared.
No examples provided.
What is the io.github.labarilem/brainfaq-mcp server?
io.github.labarilem/brainfaq-mcp is listed in the public MCP registry as io.github.labarilem/brainfaq-mcp. MCP server for the BrainFuck programming language. This page covers its npm package (brainfaq-mcp).
Is the io.github.labarilem/brainfaq-mcp server safe to use?
io.github.labarilem/brainfaq-mcp scores 77 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. 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.labarilem/brainfaq-mcp server expose?
io.github.labarilem/brainfaq-mcp exposes 6 tools: load_code, step, run, add_input, get_state, read_output. Their descriptions and schemas cost roughly 301 tokens of context every time the server is loaded.
Is the io.github.labarilem/brainfaq-mcp server still maintained?
io.github.labarilem/brainfaq-mcp is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.