# ScienceLogo (oci · ghcr.io/sciencelogo/sciencelogo-mcp)

Write and validate ScienceLogo workflows from any AI agent.

- Trust score: 39/100 (low)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- oci · `ghcr.io/sciencelogo/sciencelogo-mcp`: 39/100 (this document), [markdown](https://verifymcp.io/servers/sciencelogo-sciencelogo-mcp/ghcr-io-sciencelogo-sciencelogo-mcp.md), [page](https://verifymcp.io/servers/sciencelogo-sciencelogo-mcp/ghcr-io-sciencelogo-sciencelogo-mcp)

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/sciencelogo/sciencelogo-mcp`
- Version: `0.2.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Supply Chain Security**: 0/100
  - 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.
  - Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
- **Provenance & Transparency**: 32/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - License check failed: no license is declared.
  - Actively maintained (last published 11 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 71/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 1983 tokens (~79/item across 25 items; 24 tools + 1 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 40/100
  - Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "remove_item" implies "remove" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 26 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

**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.

## Install

### How do I install the ScienceLogo MCP server?

ScienceLogo runs locally as a container image, launched with docker run --rm -i ghcr.io/sciencelogo/sciencelogo-mcp:0.2.0, plus the required --mount and --workdir, which you supply. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add sciencelogo-sciencelogo-mcp -- docker run --rm -i ghcr.io/sciencelogo/sciencelogo-mcp:0.2.0
```

Incomplete: the registry marks --mount and --workdir as required and gives no value we can show, so they are not in this command. Add them before you run it.

### Cursor

```json
{
  "mcpServers": {
    "sciencelogo-sciencelogo-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/sciencelogo/sciencelogo-mcp:0.2.0"
      ]
    }
  }
}
```

Incomplete: the registry marks --mount and --workdir as required and gives no value we can show, so they are not in this command. Add them before you run it.

### VS Code

```json
{
  "servers": {
    "sciencelogo-sciencelogo-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/sciencelogo/sciencelogo-mcp:0.2.0"
      ]
    }
  }
}
```

Incomplete: the registry marks --mount and --workdir as required and gives no value we can show, so they are not in this command. Add them before you run it.

### Codex

```bash
codex mcp add sciencelogo-sciencelogo-mcp -- docker run --rm -i ghcr.io/sciencelogo/sciencelogo-mcp:0.2.0
```

Incomplete: the registry marks --mount and --workdir as required and gives no value we can show, so they are not in this command. Add them before you run it.

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "sciencelogo-sciencelogo-mcp": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "ghcr.io/sciencelogo/sciencelogo-mcp:0.2.0"
      ],
      "enabled": true
    }
  }
}
```

Incomplete: the registry marks --mount and --workdir as required and gives no value we can show, so they are not in this command. Add them before you run it.

### Hermes

```yaml
mcp_servers:
  sciencelogo-sciencelogo-mcp:
    command: "docker"
    args: ["run", "--rm", "-i", "ghcr.io/sciencelogo/sciencelogo-mcp:0.2.0"]
```

Incomplete: the registry marks --mount and --workdir as required and gives no value we can show, so they are not in this command. Add them before you run it.

### Netclaw

```json
{
  "McpServers": {
    "sciencelogo-sciencelogo-mcp": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/sciencelogo/sciencelogo-mcp:0.2.0"
      ]
    }
  }
}
```

Incomplete: the registry marks --mount and --workdir as required and gives no value we can show, so they are not in this command. Add them before you run it.

### Other

```json
{
  "mcpServers": {
    "sciencelogo-sciencelogo-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/sciencelogo/sciencelogo-mcp:0.2.0"
      ]
    }
  }
}
```

Incomplete: the registry marks --mount and --workdir as required and gives no value we can show, so they are not in this command. Add them before you run it.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-20 (score 39, +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.

### 2026-11-18 (score 38, +1)

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

### 2026-11-16 (score 37, +1)

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

### 2026-11-14 (score 36, +1)

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

### 2026-11-12 (score 35, +1)

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

### 2026-11-10 (score 34, +1)

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

### 2026-11-09 (score 33)

First indexed and scored.

## MCP tools (24)

### `check` (~76 tokens)

Check a workflow or library with the ScienceLogo reader, without running it.

\`entry` is the main file; the files it includes are read too. Returns
status "valid" with the structural assessment and readability advice,
or status "invalid" with the reader's message, file, line and column.

Input parameters:

- `entry` (string, required)

### `outline` (~51 tokens)

The structure of a valid workflow or library: its title and summary,
every item with its kind, name and file, and its stages, phases,
procedures, performers and imports.

Input parameters:

- `entry` (string, required)

### `read_workflow` (~90 tokens)

The text of a workflow or library, in verbose (default) or compact syntax.

With `item` (`kind:name`), only that item. A workflow the current reader
rejects is returned as stored, with the reader's error, so it can be
rewritten in the current release.

Input parameters:

- `entry` (string, required)
- `item`
- `syntax_form` (string)

### `language_reference` (~72 tokens)

The ScienceLogo documentation of the installed release.

With no topic, the list of topics and examples. A topic is a manual
page (such as "stages" or "procedures"), "grammar-ebnf", "changelog",
or "example:<name>" for an example file.

Input parameters:

- `topic`

### `create_workflow` (~44 tokens)

Start a new workflow in a new main file, with its title and summary.

Input parameters:

- `about`
- `file` (string, required)
- `title` (string, required)

### `create_library` (~73 tokens)

Start a library project in a new main file (usually library.rkt).

A library holds procedures, record interfaces, includes and imports.
\`language` is the language version it is written for (default: the
installed release).

Input parameters:

- `file` (string, required)
- `language`
- `name` (string, required)

### `write_fragment` (~146 tokens)

Write any ScienceLogo text, checked by the reader before it is saved.

By default the text goes at the end of `file` (relative to the main file;
default the main file itself). `after`, `before` or `replaces` place it
next to or in place of an item (`kind:name`). A new `file` gets its
header and an `include` line in the main file, after `include_after` or
after the last include.

Input parameters:

- `after`
- `before`
- `entry` (string, required)
- `file`
- `include_after`
- `replaces`
- `text` (string, required)

### `remove_item` (~36 tokens)

Remove an item (`kind:name`) with the comments just before it.

Input parameters:

- `entry` (string, required)
- `item` (string, required)

### `move_item` (~65 tokens)

Move an item (`kind:name`) with its comments to another file.

A new file is created and included where the item was, so the method
keeps its order.

Input parameters:

- `entry` (string, required)
- `item` (string, required)
- `to_file` (string, required)

### `set_workflow` (~45 tokens)

Set the workflow's title and its summary (about); either can be left as it is.

Input parameters:

- `about`
- `entry` (string, required)
- `title`

### `declare_performer` (~81 tokens)

Declare who or what carries out work, for example
fields {"kind": "human", "role": "scientist"}. Values are JSON; null is
unknown; {"expr": "..."} is a ScienceLogo expression.

Input parameters:

- `entry` (string, required)
- `fields` (object, required)
- `file`
- `name` (string, required)

### `declare_resource` (~62 tokens)

Declare a resource the method uses, such as an instrument or a data
source, with its fields (values as in declare_performer).

Input parameters:

- `entry` (string, required)
- `fields` (object, required)
- `file`
- `name` (string, required)

### `declare_proposition` (~86 tokens)

Declare a hypothesis, assumption or conclusion. `children` is optional
ScienceLogo text for nested propositions, such as
\`hypotheses = [h1 = [text = "..."]]`.

Input parameters:

- `children`
- `entry` (string, required)
- `file`
- `name` (string, required)
- `statement` (string, required)
- `type` (string, required)

### `declare_interface` (~118 tokens)

Declare a record interface: the fields a record must or may have.

Each field has a `name` and optionally `type` (number, text, boolean,
list, record or an interface), `default`, `unit` and `required`
(default true). `body` is optional ScienceLogo text for conditions and
other interface entries.

Input parameters:

- `body`
- `entry` (string, required)
- `extends`
- `fields` (array, required)
- `file`
- `name` (string, required)
- `version`

### `declare_procedure` (~179 tokens)

Declare a procedure. For a step done outside ScienceLogo, describe it as
a method, never by file paths or code: `about` says what it does,
\`inputs` what goes in, `result` the fields of what comes out (each with
name, type and unit), and `uncertainty` where the result's uncertainty
comes from (each with name and description, or omitted: true). The
server writes the result's record interface and an output of that
record. `body` is ScienceLogo commands, when the work is written in
ScienceLogo itself.

Input parameters:

- `about` (string, required)
- `body`
- `entry` (string, required)
- `file`
- `inputs` (array, required)
- `name` (string, required)
- `result`
- `uncertainty`

### `add_stage` (~93 tokens)

Add or replace a simple stage: a named section of the method with its
commands (ScienceLogo text). A new stage gets its own file under stages/
unless `file`, `after` or `before` place it.

Input parameters:

- `about`
- `after`
- `before`
- `commands`
- `entry` (string, required)
- `file`
- `name` (string, required)

### `add_paired_stage` (~166 tokens)

Add or replace a paired stage, which states what is known when it
starts and ends.

\`entry_state` has information, environment and factors (records as
JSON). Each call has `procedure`, optional `performer`, `inputs`
(input name to location, such as "information.elapsed") and `into` (a
location). The exit state is derived from the entry state plus every
\`into` location unless `exit_state` is given.

Input parameters:

- `about`
- `after`
- `before`
- `calls`
- `commands`
- `entry` (string, required)
- `entry_state` (object, required)
- `exit_state`
- `file`
- `name` (string, required)
- `performer`

### `add_phase` (~67 tokens)

Add or replace a phase: a named group of workflow-level stages or other
phases, in method order, with its own summary.

Input parameters:

- `about`
- `entry` (string, required)
- `file`
- `members` (array, required)
- `name` (string, required)

### `add_requirement` (~63 tokens)

Require that the method calls a procedure (`call`, one target) or runs
stages in order (`stage_order`, two or more stages).

Input parameters:

- `entry` (string, required)
- `file`
- `kind` (string, required)
- `targets` (array, required)

### `add_mapping` (~51 tokens)

State that a record (`target`) implements a record interface.

Input parameters:

- `after`
- `entry` (string, required)
- `file`
- `implements` (string, required)
- `target` (string, required)

### `import_library` (~75 tokens)

Import a library pinned to a Git tag or commit, under an alias. The
reader fetches it with Git when it checks the workflow. `describe_library`
shows what a library provides.

Input parameters:

- `alias` (string, required)
- `entry` (string, required)
- `url` (string, required)
- `version` (string, required)

### `describe_library` (~78 tokens)

What a library provides, before importing it: its name, the language
version it is written for, and its procedures (inputs and summary) and
record interfaces (fields). The reader fetches it with Git, pinned to
\`version` (a tag or commit).

Input parameters:

- `url` (string, required)
- `version` (string, required)

### `convert_syntax` (~58 tokens)

Rewrite the files of a workflow or library in verbose or compact
syntax with the reference translator, keeping comments. With `file`,
only that file.

Input parameters:

- `entry` (string, required)
- `file`
- `to` (string, required)

### `add_include` (~51 tokens)

Include an existing file (relative to the main file), after the item
\`after` or after the last include.

Input parameters:

- `after`
- `entry` (string, required)
- `path` (string, required)

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/sciencelogo-sciencelogo-mcp/ghcr-io-sciencelogo-sciencelogo-mcp#diagnostics

## Score history

- 2026-11-21: 39
- 2026-11-20: 39
- 2026-11-19: 38
- 2026-11-18: 38
- 2026-11-17: 37
- 2026-11-16: 37
- 2026-11-15: 36
- 2026-11-14: 36
- 2026-11-13: 35
- 2026-11-12: 35
- 2026-11-11: 34
- 2026-11-10: 34
- 2026-11-09: 33

## Common questions

### What is the ScienceLogo MCP server?

ScienceLogo is an MCP server listed in the public MCP registry as io.github.ScienceLogo/sciencelogo-mcp. Write and validate ScienceLogo workflows from any AI agent. This page covers its container image (ghcr.io/sciencelogo/sciencelogo-mcp).

### Is the ScienceLogo MCP server safe to use?

ScienceLogo scores 39 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 ScienceLogo MCP server expose?

ScienceLogo exposes 24 tools: check, outline, read_workflow, language_reference, create_workflow, and 19 more. Their descriptions and schemas cost roughly 1,926 tokens of context every time the server is loaded.

### Is the ScienceLogo MCP server still maintained?

ScienceLogo is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the ScienceLogo MCP server?

VerifyMCP ran 12 checks on ScienceLogo, covering Source repository, Provenance, License, Maintenance and 8 more. 4 items could not be completed, a gap on our side rather than a finding about ScienceLogo: Malware scan, Known CVEs, Install scripts and Dependency health. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a container image, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- GitHub Container Registry: https://ghcr.io/sciencelogo/sciencelogo-mcp
- Repository: https://github.com/ScienceLogo/MCP
- Changelog RSS feed: https://verifymcp.io/servers/sciencelogo-sciencelogo-mcp/ghcr-io-sciencelogo-sciencelogo-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/sciencelogo-sciencelogo-mcp/ghcr-io-sciencelogo-sciencelogo-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/sciencelogo-sciencelogo-mcp/ghcr-io-sciencelogo-sciencelogo-mcp.json
- HTML version of this page: https://verifymcp.io/servers/sciencelogo-sciencelogo-mcp/ghcr-io-sciencelogo-sciencelogo-mcp
