# minitok (npm · @flotic/minitok)

Verified coding workflows with planning, verification, bounded retries, evidence, and evolution.

- Trust score: 40/100 (low)
- Change this week: −3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-27

## Components

- npm · `@flotic/minitok`: 40/100 (this document), [markdown](https://verifymcp.io/servers/dev-minitok-minitok/flotic-minitok.md), [page](https://verifymcp.io/servers/dev-minitok-minitok/flotic-minitok)

## Channel facts

- Registry: `npm`
- Package: `@flotic/minitok`
- Version: `1.4.10`
- 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-09-27.

- **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.
  - 0 of 4 dependencies flagged as unhealthy.
- **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: the license (SEE LICENSE IN LICENSE) isn't a recognized OSI-approved license.
  - Actively maintained (last published 2 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 0/100
  - Schema quality not yet verified: our sandbox run could not list this package's tools (it declared tools, or its tool listing failed outright), so the captured schema is incomplete.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: one of the two schema captures we compare could not list the server's tools (the server declared tools, or its tool listing failed outright). Comparing them would report every tool as removed, or find nothing to compare at all.
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: our sandbox run could not list this package's tools (it declared tools, or its tool listing failed outright).
- **Tool Safety**: 0/100
  - Tool safety not yet verified: our sandbox run could not list this package's tools (it declared tools, or its tool listing failed outright).
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**Unverified: 4 categories.** Categories scored 0 because we could not verify them: 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 minitok MCP server?

minitok runs locally as an npm package, launched with npx -y @flotic/minitok. 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 dev-minitok-minitok -- npx -y @flotic/minitok
```

### Cursor

```json
{
  "mcpServers": {
    "dev-minitok-minitok": {
      "command": "npx",
      "args": [
        "-y",
        "@flotic/minitok"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-minitok-minitok": {
      "command": "npx",
      "args": [
        "-y",
        "@flotic/minitok"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add dev-minitok-minitok -- npx -y @flotic/minitok
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-minitok-minitok": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@flotic/minitok"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-minitok-minitok --command npx --arg -y --arg @flotic/minitok
```

### Hermes

```yaml
mcp_servers:
  dev-minitok-minitok:
    command: "npx"
    args: ["-y", "@flotic/minitok"]
```

### Netclaw

```json
{
  "McpServers": {
    "dev-minitok-minitok": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@flotic/minitok"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-minitok-minitok -t stdio -c npx -a -y @flotic/minitok
```

### Other

```json
{
  "mcpServers": {
    "dev-minitok-minitok": {
      "command": "npx",
      "args": [
        "-y",
        "@flotic/minitok"
      ]
    }
  }
}
```

## 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-09-25 (score 40, −5)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-24 (score 45, +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-09-22 (score 44, +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-09-20 (score 43, +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-09-19 (score 42, +2)

- [security] Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- [security] Tool safety: Tool safety not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet.
- [functional regression] Capabilities: pass → unverified
- [functional improvement] Stability: unverified → 0.13
- [functional] Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- [functional] Tool coverage: Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet.
- [functional] Package version: 1.4.6 → 1.4.10

### 2026-09-16 (score 40, +26)

- [security improvement] Malware scan: unverified → pass
- [security improvement] Known CVEs: unverified → pass
- [functional improvement] Dependency health: unverified → 1.00

### 2026-09-15 (score 14)

First indexed and scored.

## MCP tools (0)

The sandbox run completed and this package exposed no tools.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/dev-minitok-minitok/flotic-minitok#diagnostics

## Score history

- 2026-09-27: 40
- 2026-09-26: 40
- 2026-09-25: 40
- 2026-09-24: 45
- 2026-09-23: 44
- 2026-09-22: 44
- 2026-09-21: 43
- 2026-09-20: 43
- 2026-09-19: 42
- 2026-09-18: 40
- 2026-09-17: 40
- 2026-09-16: 40
- 2026-09-15: 14

## Common questions

### What is the minitok MCP server?

minitok is an MCP server listed in the public MCP registry as dev.minitok/minitok. Verified coding workflows with planning, verification, bounded retries, evidence, and evolution. This page covers its npm package (@flotic/minitok).

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

minitok scores 40 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 27 September 2026. It declares no install or post-install scripts. 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 minitok MCP server expose?

minitok exposes no tools. We connected to it and read its tool list, and it was empty, so it offers an MCP client nothing to call.

### Is the minitok MCP server still maintained?

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

## Links

- npm package: https://www.npmjs.com/package/@flotic/minitok
- Socket report: https://socket.dev/npm/package/@flotic/minitok
- Repository: https://github.com/floticinfo/minitok
- Website: https://minitok.dev/docs
- Changelog RSS feed: https://verifymcp.io/servers/dev-minitok-minitok/flotic-minitok.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-minitok-minitok/flotic-minitok.json
- HTML version of this page: https://verifymcp.io/servers/dev-minitok-minitok/flotic-minitok