# go-tokenless (npm · go-tokenless)

Move npm publishing in GitHub Actions from NPM_TOKEN to trusted publishing (OIDC).

- Trust score: 80/100 (high trust)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-16

## Components

- npm · `go-tokenless`: 80/100 (this document), [markdown](https://verifymcp.io/servers/continuous-actions-go-tokenless/go-tokenless.md), [page](https://verifymcp.io/servers/continuous-actions-go-tokenless/go-tokenless)

## Channel facts

- Registry: `npm`
- Package: `go-tokenless`
- Version: `1.1.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-10-16.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to Continuous-Actions/go-tokenless).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 9 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 407 tokens (~203/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 2 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 go-tokenless MCP server?

go-tokenless runs locally as an npm package, launched with npx -y go-tokenless. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add continuous-actions-go-tokenless -- npx -y go-tokenless
```

### Cursor

```json
{
  "mcpServers": {
    "continuous-actions-go-tokenless": {
      "command": "npx",
      "args": [
        "-y",
        "go-tokenless"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "continuous-actions-go-tokenless": {
      "command": "npx",
      "args": [
        "-y",
        "go-tokenless"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add continuous-actions-go-tokenless -- npx -y go-tokenless
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "continuous-actions-go-tokenless": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "go-tokenless"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add continuous-actions-go-tokenless --command npx --arg -y --arg go-tokenless
```

### Hermes

```yaml
mcp_servers:
  continuous-actions-go-tokenless:
    command: "npx"
    args: ["-y", "go-tokenless"]
```

### Netclaw

```json
{
  "McpServers": {
    "continuous-actions-go-tokenless": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "go-tokenless"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add continuous-actions-go-tokenless -t stdio -c npx -a -y go-tokenless
```

### Other

```json
{
  "mcpServers": {
    "continuous-actions-go-tokenless": {
      "command": "npx",
      "args": [
        "-y",
        "go-tokenless"
      ]
    }
  }
}
```

## 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-10-15 (score 80, +30)

- [security improvement] Injection markers: unverified → pass
- [security] First check of Judged manipulation: pass
- [security] Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window).
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] MCP protocol: unverified → pass
- [functional] First check of Schema quality: fail
- [functional] First check of Destructive annotations: pass
- [functional] First check of Schema quality: fail
- [functional] First check of Schema quality: good
- [functional] First check of Tool coverage: 100

### 2026-10-12 (score 50, +1)

- [functional improvement] Security disclosure: unverified → pass

### 2026-10-11 (score 49)

First indexed and scored.

## MCP tools (2)

### `plan_trusted_publishing` (~209 tokens)

Plan npm trusted publishing migration

Read-only. Finds GitHub Actions workflows that publish to npm with a token (NPM_TOKEN / NODE_AUTH_TOKEN) and returns the exact changes needed to switch to npm trusted publishing (OIDC): workflow diff, package.json repository fixes, `npm trust github` commands, and the remaining human steps. Use before apply_trusted_publishing.

Input parameters:

- `npmArgs` (string): Extra arguments appended to the npm commands it generates.
- `npmVersion` (string): npm version range for the inserted upgrade step. Default ^12; other versions may break publishing.
- `offline` (boolean): Skip npm registry lookups.
- `path` (string, required): Absolute path to the repository root.
- `readToken` (string): Secret name (e.g. NPM_READ_TOKEN) of a read-only npm token to give install steps, for private org packages. Publish steps stay tokenless.
- `repo` (string): GitHub owner/repo, if the git remote is not "origin".

### `apply_trusted_publishing` (~198 tokens)

Apply npm trusted publishing migration

Writes the workflow and package.json changes from plan_trusted_publishing to disk (no git commit, no network writes). Returns the plan with status "applied" and the steps the user must still do with npm 2FA (npm trust commands, deleting the NPM_TOKEN secret).

Input parameters:

- `npmArgs` (string): Extra arguments appended to the npm commands it generates.
- `npmVersion` (string): npm version range for the inserted upgrade step. Default ^12; other versions may break publishing.
- `offline` (boolean): Skip npm registry lookups.
- `path` (string, required): Absolute path to the repository root.
- `readToken` (string): Secret name (e.g. NPM_READ_TOKEN) of a read-only npm token to give install steps, for private org packages. Publish steps stay tokenless.
- `repo` (string): GitHub owner/repo, if the git remote is not "origin".

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/continuous-actions-go-tokenless/go-tokenless#diagnostics

## Score history

- 2026-10-16: 80
- 2026-10-15: 80
- 2026-10-14: 50
- 2026-10-13: 50
- 2026-10-12: 50
- 2026-10-11: 49

## Common questions

### What is the go-tokenless MCP server?

go-tokenless is an MCP server listed in the public MCP registry as io.github.Continuous-Actions/go-tokenless. Move npm publishing in GitHub Actions from NPM_TOKEN to trusted publishing (OIDC). This page covers its npm package (go-tokenless).

### Is the go-tokenless MCP server safe to use?

go-tokenless scores 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 16 October 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.

### What tools does the go-tokenless MCP server expose?

go-tokenless exposes 2 tools: plan_trusted_publishing, apply_trusted_publishing. Their descriptions and schemas cost roughly 407 tokens of context every time the server is loaded.

### Is the go-tokenless MCP server still maintained?

go-tokenless is still listed as active in the MCP registry. We last reached this channel on 16 October 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 go-tokenless MCP server under?

go-tokenless declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/go-tokenless
- Socket report: https://socket.dev/npm/package/go-tokenless
- Repository: https://github.com/Continuous-Actions/go-tokenless
- Changelog RSS feed: https://verifymcp.io/servers/continuous-actions-go-tokenless/go-tokenless.xml
- Changelog JSON feed: https://verifymcp.io/servers/continuous-actions-go-tokenless/go-tokenless.json
- HTML version of this page: https://verifymcp.io/servers/continuous-actions-go-tokenless/go-tokenless