# tinyprobe (oci · ghcr.io/kikutano/tinyprobe)

API testing in YAML: inspect, call and run endpoints and workflows, with the guide to write them.

- Trust score: 39/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

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

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/kikutano/tinyprobe`
- Version: `0.23.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-05.

- **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**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (GPL-3.0-only).
  - Actively maintained (last published 0 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 70/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 592 tokens (~148/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **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**: 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; "call" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 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 tinyprobe MCP server?

tinyprobe runs locally as a container image, launched with docker run --rm -i ghcr.io/kikutano/tinyprobe:0.23.0. 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 kikutano-tinyprobe -- docker run --rm -i ghcr.io/kikutano/tinyprobe:0.23.0
```

### Cursor

```json
{
  "mcpServers": {
    "kikutano-tinyprobe": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/kikutano/tinyprobe:0.23.0"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "kikutano-tinyprobe": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/kikutano/tinyprobe:0.23.0"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add kikutano-tinyprobe -- docker run --rm -i ghcr.io/kikutano/tinyprobe:0.23.0
```

### opencode

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

### Hermes

```yaml
mcp_servers:
  kikutano-tinyprobe:
    command: "docker"
    args: ["run", "--rm", "-i", "ghcr.io/kikutano/tinyprobe:0.23.0"]
```

### Netclaw

```json
{
  "McpServers": {
    "kikutano-tinyprobe": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/kikutano/tinyprobe:0.23.0"
      ]
    }
  }
}
```

### Other

```json
{
  "mcpServers": {
    "kikutano-tinyprobe": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/kikutano/tinyprobe:0.23.0"
      ]
    }
  }
}
```

## 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-05 (score 39, +1)

- [functional] Package version: 0.22.0 → 0.23.0

### 2026-11-04 (score 38, 0)

- [security regression] Tool safety: pass → unverified
- [security regression] Stability: 0.10 → unverified
- [functional regression] Capabilities: fail → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified
- [functional] Licence: MIT → GPL-3.0-only
- [functional] Package version: 0.21.0 → 0.22.0

### 2026-11-03 (score 38, +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-10-31 (score 37)

First indexed and scored.

## MCP tools (4)

### `guide` (~68 tokens)

Read the tinyprobe guide

The guide for writing tinyprobe files: the YAML format of API files and workflows, the rules that are easy to get wrong, and the procedures to test a backend or to migrate a Postman collection, an OpenAPI document or another tool's export. Read it before writing or changing tinyprobe files.

### `inspect` (~65 tokens)

Validate a tinyprobe file

Validate a tinyprobe API file or workflow without sending any request. Returns what it defines (endpoints with their params, variables, steps), or every problem with file:line:column and a suggestion.

Input parameters:

- `file` (string, required): The API file or workflow, relative to the workspace.

### `call` (~186 tokens)

Call one endpoint

Send one request to an endpoint of a tinyprobe API file or workflow, and return the request and the whole response (status, headers, body), whatever the status. Use it to see the real shape of a response before writing checks. It remembers nothing: pass a token in 'with' or 'vars'.

Input parameters:

- `endpoint` (string, required): The endpoint name, as in a step's 'call'.
- `env_file` (string): The environment file, for example tinyprobe/env.local.yaml (like -e).
- `file` (string, required): The API file or workflow that defines or imports the endpoint.
- `vars` (object): Variables over the environment file (like --var), as JSON values.
- `with` (object): The endpoint's arguments, as in a step's 'with'. JSON values keep their type: 42 is a number, "42" a string.

### `run` (~211 tokens)

Run workflows

Run tinyprobe workflows: files or folders (a folder is read recursively; API and env files in it are skipped). Every file is validated before the first request; each workflow starts from zero, and a failing one does not stop the others. Returns, for each workflow, whether it passed, its summary and its steps with their checks; failed steps include the request and the response.

Input parameters:

- `env_file` (string): The environment file, for example tinyprobe/env.local.yaml (like -e).
- `paths` (array, required): Workflow files or folders, relative to the workspace, for example ["tinyprobe/workflows"].
- `to` (integer|string): Run to here (like --to): with one workflow file, run up to this step, included, and stop. The step's number as inspect lists the steps (1-based), or its name. Use it to look at one step of a flow.
- `vars` (object): Variables over the environment file (like --var), as JSON values.

## Diagnostics

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

## Score history

- 2026-11-05: 39
- 2026-11-04: 38
- 2026-11-03: 38
- 2026-11-02: 37
- 2026-11-01: 37
- 2026-10-31: 37

## Common questions

### What is the tinyprobe MCP server?

tinyprobe is an MCP server listed in the public MCP registry as io.github.kikutano/tinyprobe. API testing in YAML: inspect, call and run endpoints and workflows, with the guide to write them. This page covers its container image (ghcr.io/kikutano/tinyprobe).

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

tinyprobe 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 tinyprobe MCP server expose?

tinyprobe exposes 4 tools: guide, inspect, call, run. Their descriptions and schemas cost roughly 530 tokens of context every time the server is loaded.

### Is the tinyprobe MCP server still maintained?

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

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

## Links

- GitHub Container Registry: https://ghcr.io/kikutano/tinyprobe
- Repository: https://github.com/kikutano/tinyprobe
- Changelog RSS feed: https://verifymcp.io/servers/kikutano-tinyprobe/ghcr-io-kikutano-tinyprobe.xml
- Changelog JSON feed: https://verifymcp.io/servers/kikutano-tinyprobe/ghcr-io-kikutano-tinyprobe.json
- HTML version of this page: https://verifymcp.io/servers/kikutano-tinyprobe/ghcr-io-kikutano-tinyprobe