io.github.AImplifier/neuro-mcp
PYPI · NEURO-MCP · SCANNED SEP 20
MCP for NeuroAgents assisting clinicians: MNE processing, EHR store, NeuroII visualization.
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
- 5 of 59 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- 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
- Clear OSI-approved license (BSD-3-Clause).Pass
- Actively maintained (last published 57 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 4693 tokens (~86/item across 54 items; 54 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 Coverage84
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 46% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
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; "apply_ica" implies "remove" 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 55 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the io.github.AImplifier/neuro-mcp server?
io.github.AImplifier/neuro-mcp runs locally as a PyPI package, launched with uvx neuro-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · neuro-mcp
claude mcp add aimplifier-neuro-mcp -- uvx neuro-mcp
{
"mcpServers": {
"aimplifier-neuro-mcp": {
"command": "uvx",
"args": [
"neuro-mcp"
]
}
}
} {
"servers": {
"aimplifier-neuro-mcp": {
"command": "uvx",
"args": [
"neuro-mcp"
]
}
}
} codex mcp add aimplifier-neuro-mcp -- uvx neuro-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"aimplifier-neuro-mcp": {
"type": "local",
"command": [
"uvx",
"neuro-mcp"
],
"enabled": true
}
}
} openclaw mcp add aimplifier-neuro-mcp --command uvx --arg neuro-mcp
mcp_servers:
aimplifier-neuro-mcp:
command: "uvx"
args: ["neuro-mcp"] {
"McpServers": {
"aimplifier-neuro-mcp": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"neuro-mcp"
]
}
}
} assistant mcp add aimplifier-neuro-mcp -t stdio -c uvx -a neuro-mcp
{
"mcpServers": {
"aimplifier-neuro-mcp": {
"command": "uvx",
"args": [
"neuro-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.
- 20 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.
- 19 Sept 26 −3
- Stability: pass → 0.80 functional
- 18 Sept 26 0
- Stability: 0.97 → pass security
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +16
- Malware scan: unverified → pass ▲ security
- 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.
- 11 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 pypi/neuro-mcp@0.1.3
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 59 packages
| Packages resolved | 59 |
|---|---|
| Stale | 4 |
| No linked repository | 1 |
| 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 →
visualize_esi Visualize Esi ~229
Render the EsiView source-imaging viewer as interactive HTML — NEUROII style. Computes a volumetric source estimate on the fsaverage template and shows it on three orthogonal MRI slices (sagittal / coronal / axial) rendered to canvas with a black-blue-white-red activation overlay, crosshair at the peak, L/R and MNI-coordinate labels; the cut planes recentre on each frame's peak. Below, the ERP butterfly carries a red current-time cursor and a blue half-peak marker. Controls: a time slider, a global/frame colormap-scale toggle, and a mask-threshold slider. Requires epochs (epoch_neuro) + montage.
| Name | Type | Req | Description |
|---|---|---|---|
| method | string | – | Inverse method ('dSPM', 'MNE', 'sLORETA', 'eLORETA'). |
| n_frames | integer | – | Number of time points on the slider. |
| out_path | – | – | Output .html (default <data>/viz/esi_<session>.html). |
| session_id | string | – | Session holding the epochs. |
Structured output declared, but exposes no named fields.
No examples provided.
visualize_timeseries Visualize Timeseries ~164
Render the RawView EEG time-series viewer as interactive HTML. Stacked channels on one amplitude scale, with NEUROII's controls: page navigation (⏮ ◀ ▶ ⏭), a page-length box, scroll-to-zoom amplitude, and a grid toggle. Requires a loaded recording (load_neuro / import_recording).
| Name | Type | Req | Description |
|---|---|---|---|
| max_seconds | number | – | How much of the recording to embed (from the start). |
| n_channels | integer | – | Max EEG channels shown (from the top). |
| out_path | – | – | Output .html (default <data>/viz/timeseries_<session>.html). |
| page_len | number | – | Initial page length in seconds. |
| session_id | string | – | Processing session holding the recording. |
Structured output declared, but exposes no named fields.
No examples provided.
void_annotation Void Annotation ~47
Soft-void an annotation (mark 'entered-in-error'); kept, not deleted.
| Name | Type | Req | Description |
|---|---|---|---|
| actor | string | yes | – |
| logical_id | string | yes | – |
| note | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
void_ehr_record Void Ehr Record ~71
Soft-void an EHR record (mark 'entered-in-error'). It is kept, not deleted.
| Name | Type | Req | Description |
|---|---|---|---|
| actor | string | yes | Clinician performing the retraction (audited). |
| logical_id | string | yes | Record to void. |
| note | string | yes | Reason (required for a void). |
Structured output declared, but exposes no named fields.
No examples provided.
What is the io.github.AImplifier/neuro-mcp server?
io.github.AImplifier/neuro-mcp is listed in the public MCP registry as io.github.AImplifier/neuro-mcp. MCP for NeuroAgents assisting clinicians: MNE processing, EHR store, NeuroII visualization. This page covers its PyPI package (neuro-mcp).
Is the io.github.AImplifier/neuro-mcp server safe to use?
io.github.AImplifier/neuro-mcp scores 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 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.AImplifier/neuro-mcp server expose?
io.github.AImplifier/neuro-mcp exposes 54 tools: load_neuro, session_info, list_sessions, reset_session, filter_neuro, and 49 more. Their descriptions and schemas cost roughly 4,417 tokens of context every time the server is loaded.
Is the io.github.AImplifier/neuro-mcp server still maintained?
io.github.AImplifier/neuro-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.
What licence is the io.github.AImplifier/neuro-mcp server under?
io.github.AImplifier/neuro-mcp declares the BSD-3-Clause licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.