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.

OSF CLI Go

OCI · GHCR.IO/EDITHATOGO/OSF-CLI-GO-OSF-MCP:0.3.2

Read-only MCP tools for authenticated Open Science Framework projects and files.

0 this week 55 Trust /100

Last scanned (17 hours ago)

Scores higher than 93% of OCI servers

Category Education and Research

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 Security0
  • No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
  • Known CVEs could not be checked: this image's dependency list comes from an SBOM its publisher attached, which nothing verifies, so we will not report it as a clean result.Unverified
  • Install-script risk not yet assessed.Unverified
  • Dependency health could not be checked: this image's dependency list comes from an SBOM its publisher attached. It names packages and versions but not whether each is deprecated, still maintained or linked to its source, so there is nothing we can fairly grade.Unverified
Provenance & Transparency48
  • 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 (Apache-2.0).Pass
  • Actively maintained (last published 114 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability77
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 200 tokens (~33/item across 6 items; 6 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

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.

  • 1 Nov 26 0
    • Stability: 0.97 → pass security
  • 31 Oct 26 0
    • Stability: pass → 0.97 functional
  • 20 Oct 26 0
    • Stability: 0.97 → pass security
  • 19 Oct 26 0
    • Stability: pass → 0.97 functional
  • 17 Oct 26 +1
    • Stability: 0.87 → pass security
  • 16 Oct 26 +1

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

  • 14 Oct 26 −2
    • Stability: pass → 0.80 functional
  • 13 Oct 26 0
    • Stability: 0.97 → 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 4 Nov 2026 · Analysed oci/ghcr.io/edithatogo/osf-cli-go-osf-mcp:0.3.2

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem oci
Reason No attestation published

Background: How many MCP packages publish verified provenance →

MCP tools · 6 exposed · ~200 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
osf_components_list ~36

List immediate child components for an OSF project or component.

NameTypeReqDescription
idstringyesOSF project/component id or URL
NameTypeReqDescription
nodesnull|arrayyes–

No examples provided.

osf_contributors_list ~35

List contributors for an OSF project or component.

NameTypeReqDescription
idstringyesOSF project/component id or URL
NameTypeReqDescription
contributorsnull|arrayyes–

No examples provided.

osf_files_list ~54

List OSF Storage files and folders for a project/component, optionally below a path.

NameTypeReqDescription
idstringyesOSF project/component id or URL
pathstring–optional path below OSF Storage
NameTypeReqDescription
filesnull|arrayyes–

No examples provided.

osf_project_get ~36

Get an OSF project or component by id or URL.

NameTypeReqDescription
idstringyesOSF project/component id or URL
NameTypeReqDescription
nodeobjectyes–

No examples provided.

osf_projects_list ~20

List projects owned by the authenticated OSF user.

Input schema present but exposes no named parameters.

NameTypeReqDescription
nodesnull|arrayyes–

No examples provided.

osf_whoami ~19

Return the authenticated OSF user profile.

Input schema present but exposes no named parameters.

NameTypeReqDescription
userobjectyes–

No examples provided.

Install

How do I install the OSF CLI Go MCP server?

OSF CLI Go runs locally as a container image, launched with docker run --rm -i -e OSF_TOKEN -e OSF_USERNAME -e OSF_PASSWORD ghcr.io/edithatogo/osf-cli-go-osf-mcp:0.3.2. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

oci · ghcr.io/edithatogo/osf-cli-go-osf-mcp:0.3.2

# add to Claude Code
claude mcp add edithatogo-osf-cli-go -- docker run --rm -i -e OSF_TOKEN -e OSF_USERNAME -e OSF_PASSWORD ghcr.io/edithatogo/osf-cli-go-osf-mcp:0.3.2

This image reads OSF_TOKEN, OSF_USERNAME and OSF_PASSWORD. Set them in your client's env block for this server; docker run -e passes each one through to the container.

Common questions

What is the OSF CLI Go MCP server?

OSF CLI Go is an MCP server listed in the public MCP registry as io.github.edithatogo/osf-cli-go. Read-only MCP tools for authenticated Open Science Framework projects and files. This page covers its container image (ghcr.io/edithatogo/osf-cli-go-osf-mcp:0.3.2).

Is the OSF CLI Go MCP server safe to use?

OSF CLI Go scores 55 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 OSF CLI Go MCP server expose?

OSF CLI Go exposes 6 tools: osf_components_list, osf_contributors_list, osf_files_list, osf_project_get, osf_projects_list, osf_whoami. Their descriptions and schemas cost roughly 200 tokens of context every time the server is loaded.

Is the OSF CLI Go MCP server still maintained?

OSF CLI Go is still listed as active in the MCP registry. We last reached this channel on 4 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 OSF CLI Go MCP server under?

OSF CLI Go 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.