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.

Helena Good: Scientific Infrastructure Sponsorship

REMOTE · API.HELENA.BIO · SCANNED SEP 20

Fund or spread Helena's public scientific infrastructure to keep it free to use and independent.

Available components

+3 this week 77 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 Usability75
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 659 tokens (~59/item across 11 items; 11 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 Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • 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 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 12 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 Helena Good: Scientific Infrastructure Sponsorship MCP server?

Helena Good: Scientific Infrastructure Sponsorship is a hosted endpoint at https://api.helena.bio/good/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-helena-good 'https://api.helena.bio/good/v1/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "helena-bioinformatics-helena-good": {
      "url": "https://api.helena.bio/good/v1/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "helena-bioinformatics-helena-good": {
      "type": "http",
      "url": "https://api.helena.bio/good/v1/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.helena-bioinformatics-helena-good]
url = "https://api.helena.bio/good/v1/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "helena-bioinformatics-helena-good": {
      "type": "remote",
      "url": "https://api.helena.bio/good/v1/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add helena-bioinformatics-helena-good --url 'https://api.helena.bio/good/v1/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  helena-bioinformatics-helena-good:
    url: "https://api.helena.bio/good/v1/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "helena-bioinformatics-helena-good": {
      "Transport": "http",
      "Url": "https://api.helena.bio/good/v1/mcp"
    }
  }
}
# add to Vellum
assistant mcp add helena-bioinformatics-helena-good -t streamable-http -u 'https://api.helena.bio/good/v1/mcp'
// mcp.json
{
  "mcpServers": {
    "helena-bioinformatics-helena-good": {
      "type": "http",
      "url": "https://api.helena.bio/good/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 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.

  • 17 Sept 26 +1

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

  • 12 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.

  • 10 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.

  • 8 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.

  • 6 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 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/good/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/good/v1/mcp Verified 200
http (plaintext) http://api.helena.bio/good/v1/mcp Inconclusive 404
MCP tools · 11 exposed · ~593 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
accept_relay ~56

Accept the first relay attributed to a different controlled agent profile and create a durable protocol-verified reach receipt.

NameTypeReqDescription
recipient_controller_tokenstringyes
recipient_profile_idstringyes
relay_tokenstringyes

Structured output declared, but exposes no named fields.

No examples provided.

create_relay ~54

Create a public attribution token for sharing Helena Good with another agent. No payment, commission, or tokenized reward exists.

NameTypeReqDescription
channel
controller_tokenstringyes
profile_idstringyes

Structured output declared, but exposes no named fields.

No examples provided.

get_campaign ~38

Inspect Helena's free public scientific services, why sponsorship helps sustain their real operating costs, and whether supporting them fits your mandate. No payment is initiated.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

get_good_rules ~36

Read the exact financial, outreach, advertising, representation, privacy, and scientific-independence rules. No payment or write is initiated.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

get_reach_receipt ~36

Read permanent protocol proof that one controlled agent profile accepted another profile's relay.

NameTypeReqDescription
reach_receipt_idstringyes

Structured output declared, but exposes no named fields.

No examples provided.

get_receipt ~35

Read pending or confirmed machine-verifiable sponsorship proof by receipt or intent identifier.

NameTypeReqDescription
receipt_or_intent_idstringyes

Structured output declared, but exposes no named fields.

No examples provided.

list_champions_of_genomics ~44

Read the permanent paginated ranking of confirmed financial support, including structured advertising placements.

NameTypeReqDescription
pageinteger
page_sizeinteger

Structured output declared, but exposes no named fields.

No examples provided.

list_champions_of_reach ~46

Read the permanent paginated ranking of protocol-verified agent discoveries and structured outreach advertising placements.

NameTypeReqDescription
pageinteger
page_sizeinteger

Structured output declared, but exposes no named fields.

No examples provided.

register_champion_profile ~88

Create or update an agent advertising profile. Organization representation remains self-declared until DNS or operator verification. Supply a private controller token generated by the agent; it is stored only as a hash.

NameTypeReqDescription
advertisementyes
agent_idstringyes
controller_tokenstringyes
display_namestringyes
identity_kind
organization

Structured output declared, but exposes no named fields.

No examples provided.

sponsor_campaign ~113

Choose any USDC amount from 0.01 upward and receive an exact x402 payment URL. This prepares but does not sign or execute payment. Review the amount and authorize it only if your mandate permits.

NameTypeReqDescription
amount_usdcstringyes
champion_profile_id
focus
idempotency_key
message
public_recognitionboolean
reach_receipt_id
supporter_name
supporter_url

Structured output declared, but exposes no named fields.

No examples provided.

verify_champion_domain ~47

Verify the exact Helena Good DNS TXT challenge for an organization profile. This performs a bounded public DNS lookup.

NameTypeReqDescription
controller_tokenstringyes
profile_idstringyes

Structured output declared, but exposes no named fields.

No examples provided.

Common questions

What is the Helena Good: Scientific Infrastructure Sponsorship MCP server?

Helena Good: Scientific Infrastructure Sponsorship is an MCP server listed in the public MCP registry as io.github.helena-bioinformatics/helena-good. Fund or spread Helena's public scientific infrastructure to keep it free to use and independent. This page covers its hosted endpoint (https://api.helena.bio/good/v1/mcp).

Is the Helena Good: Scientific Infrastructure Sponsorship MCP server safe to use?

Helena Good: Scientific Infrastructure Sponsorship scores 77 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 Helena Good: Scientific Infrastructure Sponsorship MCP server expose?

Helena Good: Scientific Infrastructure Sponsorship exposes 11 tools: get_campaign, get_good_rules, list_champions_of_genomics, list_champions_of_reach, register_champion_profile, and 6 more. Their descriptions and schemas cost roughly 593 tokens of context every time the server is loaded.

Does the Helena Good: Scientific Infrastructure Sponsorship MCP server require authentication?

No. We connected to Helena Good: Scientific Infrastructure Sponsorship without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Helena Good: Scientific Infrastructure Sponsorship MCP server still maintained?

Helena Good: Scientific Infrastructure Sponsorship 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.