Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Elnora MCP Server

NPM · @ELNORA-AI/MCP-SERVER · 2 COMPONENTS

AI-powered bioprotocol optimization — generate, search, and manage lab protocols via MCP

0 this week 44 Trust /100

Last scanned (10 hours ago)

Scores higher than 22% of npm servers

Category Health and Science

Trust breakdown (7 categories)

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 Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 33 of 106 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to Elnora-AI/elnora-mcp-server). View diagnostics → Pass
  • Clear OSI-approved license (Apache-2.0).Pass
  • Actively maintained (last published 1 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability0
  • Schema quality not yet verified: this package installed, but its server did not start, so we have no schema to assess.Unverified
Stability & Change Management0
  • Stability not yet verified: this package installed, but its server did not start, so we have no schema to compare.Unverified
Tool Coverage0
  • Tool coverage not yet verified: this package installed, but its server did not start, so we have no tool definitions to assess.Unverified
Tool Safety0
  • Tool safety not yet verified: this package installed, but its server did not start, so we have no tool text to scan.Unverified
Capabilities0
  • Protocol version not yet verified: this package installed, but its server did not start, so we never saw its MCP handshake.Unverified

Unverified: 5 categories

Categories scored 0 because our sandbox has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →

Changelog

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.

  • 24 Oct 26 −5
    • CVE-2023-54404 affects this package: high ▼ security
    • Known CVEs: pass → fail ▼ security
  • 13 Oct 26 0
    • Security disclosure: unverified → pass ▲ functional
  • 11 Oct 26 0
    • Security disclosure: pass → unverified ▼ functional
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 7 Aug 26 0
    • Known CVEs: partial → pass ▲ security
    • Security disclosure: fail → pass ▲ functional
    • Dependency health: partial → 0.86 functional
Diagnostics

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 5 Nov 2026 · Analysed npm/@elnora-ai/mcp-server@0.1.1

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo Elnora-AI/elnora-mcp-server
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/Elnora-AI/elnora-mcp-server/.github/workflows/publish.yml@refs/tags/v0.1.1
Rekor log index 1016623378
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:def3391c1cf71fa634a8fb887736237e4e8b324372e88371d87117edba6c48667c7581aa10cac6d5e107839b0cd0b97181eed3fda18d6b3792112180e

Background: How many MCP packages publish verified provenance →

Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 106 packages
Packages resolved 106
Stale 33
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools

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 →

Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.

Install

How do I install the Elnora MCP Server server?

Elnora MCP Server runs locally as an npm package, launched with npx -y @elnora-ai/mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @elnora-ai/mcp-server

# add to Claude Code
claude mcp add elnora-ai-elnora-mcp-server -- npx -y @elnora-ai/mcp-server
Common questions

What is the Elnora MCP Server server?

Elnora MCP Server is listed in the public MCP registry as io.github.Elnora-AI/elnora-mcp-server. AI-powered bioprotocol optimization, generate, search, and manage lab protocols via MCP. This page covers its npm package (@elnora-ai/mcp-server).

Is the Elnora MCP Server server safe to use?

Elnora MCP Server scores 44 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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.

Is the Elnora MCP Server server still maintained?

Elnora MCP Server is still listed as active in the MCP registry. We last reached this channel on 5 November 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 Elnora MCP Server server under?

Elnora MCP Server declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.