Elabftw MCP Server

@sura_ai/elabftw npm v0.5.0

Published by @sura_ai — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

Model Context Protocol toolkit for elabftw (electronic lab notebook). Stdio MCP server + programmatic eLabFTW v2 client. Search, read, and write experiments, items, attachments, comments, steps, and links from any MCP-aware AI client.

Trust grade
A
96/100
Last scanned get badge →
Trust
A · 96/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Moderate
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 96/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 4 = 96. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−3 capability blast radius (moderate) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 2

medium Tool "elab_unlink_entities" can modify the filesystemMTC-CAP-002

Tool "elab_unlink_entities" can write, overwrite or delete files (keyword "unlink" in tool name). Verify it is scoped to a safe directory.

Fix: Constrain file operations to an explicit, non-sensitive root; reject path traversal.

Location: tool elab_unlink_entities

low Mutating tool "elab_unlink_entities" declares no destructiveHintMTC-CAP-005

Tool "elab_unlink_entities" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.

Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.

Location: tool elab_unlink_entities

Tools 63

Each tool and what it can reach — statically extracted from the published source.

  • elab_download_attachmentingests untrusted input
  • elab_unlink_entitieswrites files
  • elab_add_commentno sensitive capability
  • elab_add_stepno sensitive capability
  • elab_add_tagno sensitive capability
  • elab_bloxbergno sensitive capability
  • elab_clone_extra_fields_schemano sensitive capability
  • elab_configured_teamsno sensitive capability
  • elab_create_compoundno sensitive capability
  • elab_create_compound_from_pubchemno sensitive capability
Show 53 more tools ↓
  • elab_create_entityno sensitive capability
  • elab_create_tagno sensitive capability
  • elab_delete_commentno sensitive capability
  • elab_delete_compoundno sensitive capability
  • elab_delete_entityno sensitive capability
  • elab_delete_stepno sensitive capability
  • elab_delete_tagno sensitive capability
  • elab_duplicate_entityno sensitive capability
  • elab_exportno sensitive capability
  • elab_getno sensitive capability
  • elab_get_bulkno sensitive capability
  • elab_get_compoundno sensitive capability
  • elab_get_revisionno sensitive capability
  • elab_get_userno sensitive capability
  • elab_infono sensitive capability
  • elab_link_entitiesno sensitive capability
  • elab_list_attachmentsno sensitive capability
  • elab_list_commentsno sensitive capability
  • elab_list_eventsno sensitive capability
  • elab_list_experiments_categoriesno sensitive capability
  • elab_list_experiments_statusno sensitive capability
  • elab_list_extra_field_namesno sensitive capability
  • elab_list_extra_fieldsno sensitive capability
  • elab_list_items_statusno sensitive capability
  • elab_list_items_typesno sensitive capability
  • elab_list_linksno sensitive capability
  • elab_list_revisionsno sensitive capability
  • elab_list_stepsno sensitive capability
  • elab_list_tagsno sensitive capability
  • elab_list_team_usersno sensitive capability
  • elab_list_teamsno sensitive capability
  • elab_list_templatesno sensitive capability
  • elab_list_unfinished_stepsno sensitive capability
  • elab_lockno sensitive capability
  • elab_meno sensitive capability
  • elab_remove_extra_fieldno sensitive capability
  • elab_remove_tagno sensitive capability
  • elab_searchno sensitive capability
  • elab_search_all_teamsno sensitive capability
  • elab_search_compoundsno sensitive capability
  • elab_search_pubchemno sensitive capability
  • elab_search_usersno sensitive capability
  • elab_set_extra_fieldno sensitive capability
  • elab_set_extra_field_groupsno sensitive capability
  • elab_signno sensitive capability
  • elab_timestampno sensitive capability
  • elab_toggle_stepno sensitive capability
  • elab_unlockno sensitive capability
  • elab_update_commentno sensitive capability
  • elab_update_compoundno sensitive capability
  • elab_update_entityno sensitive capability
  • elab_update_extra_fieldno sensitive capability
  • elab_update_stepno sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.5.0 latest A 96/100 2 1.13.0 2026-09-07

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 96/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/sura-ai-elabftw/badge.svg)](https://mcptrustchecker.com/registry/sura-ai-elabftw)
HTML
<a href="https://mcptrustchecker.com/registry/sura-ai-elabftw"><img src="https://mcptrustchecker.com/registry/sura-ai-elabftw/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/sura-ai-elabftw/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan @sura_ai/elabftw --online

Use the free API → How scoring works

More in Learning & Documentation