tinyprobe
OCI · GHCR.IO/KIKUTANO/TINYPROBE
API testing in YAML: inspect, call and run endpoints and workflows, with the guide to write them.
Available components
Last scanned (1 hour ago)
Scores higher than 39% of OCI servers
Category Testing and QA
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 artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency45
- 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 (GPL-3.0-only).Pass
- Actively maintained (last published 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability70
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 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. See how to fix → Fail
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
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.
- 5 Nov 26 +1
- Package version: 0.22.0 → 0.23.0 functional
- 4 Nov 26 0
- Tool safety: pass → unverified ▼ security
- Stability: 0.10 → unverified ▼ security
- Capabilities: fail → unverified ▼ functional
- 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 functional
- 3 Nov 26 +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.
- 31 Oct 26 37
First indexed and scored.
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 5 Nov 2026 · Analysed oci/ghcr.io/kikutano/tinyprobe@0.23.0
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 →
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 →
call Call one endpoint ~186
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'.
| Name | Type | Req | Description |
|---|---|---|---|
| endpoint | string | yes | 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 | yes | 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. |
No output schema declared.
No examples provided.
guide Read the tinyprobe guide ~68
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
inspect Validate a tinyprobe file ~65
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.
| Name | Type | Req | Description |
|---|---|---|---|
| file | string | yes | The API file or workflow, relative to the workspace. |
No output schema declared.
No examples provided.
run Run workflows ~211
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.
| Name | Type | Req | Description |
|---|---|---|---|
| env_file | string | – | The environment file, for example tinyprobe/env.local.yaml (like -e). |
| paths | array | yes | 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. |
No output schema declared.
No examples provided.
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.
oci · ghcr.io/kikutano/tinyprobe
claude mcp add kikutano-tinyprobe -- docker run --rm -i ghcr.io/kikutano/tinyprobe:0.23.0
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.