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.

Noodle Biomedical Literature Discovery MCP

REMOTE · API.HELENA.BIO · SCANNED SEP 20

Search biomedical papers, inspect publication records, and traverse citation or semantic graphs.

Available components

+3 this week 80 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security66
Transport & Reachability100
Schema Quality & AI Usability86
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 630 tokens (~78/item across 8 items; 7 tools + 1 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management73
  • Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
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 9 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
Install

How do I install the Noodle Biomedical Literature Discovery MCP server?

Noodle Biomedical Literature Discovery MCP is a hosted endpoint at https://api.helena.bio/noodle/v1/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · api.helena.bio

# add to Claude Code
claude mcp add --transport http helena-bioinformatics-noodle 'https://api.helena.bio/noodle/v1/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "helena-bioinformatics-noodle": {
      "url": "https://api.helena.bio/noodle/v1/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "helena-bioinformatics-noodle": {
      "type": "http",
      "url": "https://api.helena.bio/noodle/v1/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.helena-bioinformatics-noodle]
url = "https://api.helena.bio/noodle/v1/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "helena-bioinformatics-noodle": {
      "type": "remote",
      "url": "https://api.helena.bio/noodle/v1/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add helena-bioinformatics-noodle --url 'https://api.helena.bio/noodle/v1/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  helena-bioinformatics-noodle:
    url: "https://api.helena.bio/noodle/v1/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "helena-bioinformatics-noodle": {
      "Transport": "http",
      "Url": "https://api.helena.bio/noodle/v1/mcp"
    }
  }
}
# add to Vellum
assistant mcp add helena-bioinformatics-noodle -t streamable-http -u 'https://api.helena.bio/noodle/v1/mcp'
// mcp.json
{
  "mcpServers": {
    "helena-bioinformatics-noodle": {
      "type": "http",
      "url": "https://api.helena.bio/noodle/v1/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

  • 19 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

  • 8 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 6 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 4 Sept 26 +2
    • DNSSEC: fail → pass security
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 20 Sept 2026 · Probed https://api.helena.bio/noodle/v1/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=api.helena.bio CN=YE1,O=Let's Encrypt,C=US 31 Jul 2026 29 Oct 2026 ECDSA 256 ECDSA-SHA384 6771d20c762914c9ce8e1bf90853ecaba4c
SANs: api.helena.bio
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of api.helena.bio. Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
bio. present 16334 8 Verified
helena.bio. present 22743 13 Verified
api.helena.bio. Verified address RRset verified with the apex keys
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.helena.bio/noodle/v1/mcp Verified 200
http (plaintext) http://api.helena.bio/noodle/v1/mcp Inconclusive 404
MCP tools · 7 exposed · ~511 tokens

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 →

Tool Tokens
get_corpus_summary ~37

Return public corpus coverage, source, freshness, and count metadata. Results are for literature discovery and professional review, not diagnosis or treatment.

Input schema present but exposes no named parameters.

NameTypeReqDescription
contract_versionstringyes
countsyes
deduplication_keysarrayyes
generated_atstringyes
scopestringyes
sourcesarrayyes

No examples provided.

get_publication_details ~70

Retrieve one complete public bibliographic record by PMID after search. Results are for literature discovery and professional review, not diagnosis or treatment.

NameTypeReqDescription
pmidstringyesOne PubMed identifier to look up in Noodle's current public corpus, as 1 to 12 digits without a PMID prefix.
NameTypeReqDescription
contract_versionstringyes
publicationyes
usage_boundaryobjectyes

No examples provided.

get_publication_neighborhood ~72

Retrieve the bounded citation and semantic neighborhood around one PMID. Results are for literature discovery and professional review, not diagnosis or treatment.

NameTypeReqDescription
from_work_idOptional prior work ID for a reversible graph path.
pmidstringyesOne PubMed identifier, as 1 to 12 digits.
NameTypeReqDescription
anchor_node_idstringyes
anchor_pmid
anchor_work_id
contract_versionstringyes
edgesarrayyes
freshnessstringyes
generated_atstringyes
graph_versionstringyes
nodesarrayyes
policy_versionstringyes
release_channelstringyes
stale_afterstringyes
usage_boundaryyes

No examples provided.

get_work_details ~52

Retrieve one complete public bibliographic record by Noodle work identifier. Results are for literature discovery and professional review, not diagnosis or treatment.

NameTypeReqDescription
work_idstringyesCanonical Noodle Literature Corpus work identifier.
NameTypeReqDescription
contract_versionstringyes
publicationyes
usage_boundaryobjectyes

No examples provided.

get_work_neighborhood ~72

Retrieve the bounded citation and semantic neighborhood around one Noodle work identifier. Results are for literature discovery and professional review, not diagnosis or treatment.

NameTypeReqDescription
from_work_idOptional prior work ID for a reversible graph path.
work_idstringyesCanonical work identifier to place at the graph center.
NameTypeReqDescription
anchor_node_idstringyes
anchor_pmid
anchor_work_id
contract_versionstringyes
edgesarrayyes
freshnessstringyes
generated_atstringyes
graph_versionstringyes
nodesarrayyes
policy_versionstringyes
release_channelstringyes
stale_afterstringyes
usage_boundaryyes

No examples provided.

search_biomedical_literature ~173

Semantically search Noodle's public PubMed-derived biomedical corpus. Include known PMID, DOI, or PMCID identifiers in the query so they can act as exact anchors. Results are for literature discovery and professional review, not diagnosis or treatment.

NameTypeReqDescription
cursorOpaque continuation cursor from the preceding response for the same query and sort order; omit for the first page.
limitintegerMaximum number of publications to return, from 1 to 25.
querystringyesNatural-language literature question or exact PMID, DOI, PMCID, gene, variant, phenotype, HPO, or OMIM query. Include every known publication identifier when comparing or finding related papers.
sortstringResult ordering: relevance-ranked, newest publication first, or oldest publication first.
NameTypeReqDescription
contract_versionstringyes
graph_degraded_reason
graph_usedboolean
graph_version
has_moreboolean
next_cursor
querystringyes
resultsarrayyes
returned_countintegeryes
searchable_fieldsarrayyes
semantic_degraded_reason
semantic_index_usedboolean
usage_boundaryobjectyes

No examples provided.

support_helena ~35

Learn about the separate Helena Good MCP. This opt-in information action initiates no payment or outreach and changes no scientific result.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

Common questions

What is the Noodle Biomedical Literature Discovery MCP server?

Noodle Biomedical Literature Discovery MCP is listed in the public MCP registry as io.github.helena-bioinformatics/noodle. Search biomedical papers, inspect publication records, and traverse citation or semantic graphs. This page covers its hosted endpoint (https://api.helena.bio/noodle/v1/mcp).

Is the Noodle Biomedical Literature Discovery MCP server safe to use?

Noodle Biomedical Literature Discovery MCP scores 80 out of 100 on VerifyMCP. 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 Noodle Biomedical Literature Discovery MCP server expose?

Noodle Biomedical Literature Discovery MCP exposes 7 tools: search_biomedical_literature, get_publication_details, get_work_details, get_publication_neighborhood, get_work_neighborhood, and 2 more. Their descriptions and schemas cost roughly 511 tokens of context every time the server is loaded.

Does the Noodle Biomedical Literature Discovery MCP server require authentication?

No. We connected to Noodle Biomedical Literature Discovery MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Noodle Biomedical Literature Discovery MCP server still maintained?

Noodle Biomedical Literature Discovery 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.