Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.TinySuiteHQ/tinysearch

OCI · DOCKER.IO/MARCELLM01/TINYSEARCH · 2 COMPONENTS

Fast discovery search and self-hosted web research for MCP agents.

0 this week 10 Trust /100

Last scanned (1 hour ago)

Scores higher than 23% of OCI servers

Category Search and Retrieval

Trust breakdown (7 categories)

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 image's dependency list comes from an SBOM its publisher attached, which nothing verifies, so we will not report it as a clean result. View diagnostics → Unverified
  • Install-script risk not yet assessed.Unverified
  • Dependency health could not be checked: this image's dependency list comes from an SBOM its publisher attached. It names packages and versions but not whether each is deprecated, still maintained or linked to its source, so there is nothing we can fairly grade.Unverified
Provenance & Transparency48
  • 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 (MIT).Pass
  • Actively maintained (last published 7 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability0
  • Schema quality not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to assess.Unverified
Stability & Change Management0
  • Stability not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to compare.Unverified
Tool Coverage0
  • Tool coverage not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool definitions to assess.Unverified
Tool Safety0
  • Tool safety not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool text to scan.Unverified
Capabilities0
  • Protocol version not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we never saw its MCP handshake.Unverified

Unverified: 6 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.

Changelog

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.

  • 29 Oct 26 0
    • 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. security
    • 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
    • Capabilities: Protocol version not yet verified: we do not have a sandbox capture of the MCP handshake this version of the package performs yet. 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
    • Package version: v0.6.7 → v0.6.8 functional
  • 28 Oct 26 0
    • 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. security
    • 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
    • Capabilities: Protocol version not yet verified: we do not have a sandbox capture of the MCP handshake this version of the package performs yet. 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
    • Package version: v0.6.6 → v0.6.7 functional
  • 15 Oct 26 0
    • Stability: Stability not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to compare. security
    • Tool safety: Tool safety not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool text to scan. security
    • Capabilities: Protocol version not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we never saw its MCP handshake. functional
    • Tool coverage: Tool coverage not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool definitions to assess. functional
    • Schema quality: Schema quality not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to assess. functional
  • 13 Oct 26 0
    • Provenance: unverified → fail ▼ security
  • 12 Oct 26 0
    • Provenance: fail → unverified ▼ security
  • 9 Oct 26 10

    First indexed and scored.

Diagnostics

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/docker.io/marcellm01/tinysearch@v0.6.8

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 →

Vulnerabilities 8 ungraded findings

From the publisher's SBOM, not graded. These advisories match packages listed in the SBOM the publisher attached to this image. A publisher naming a vulnerable package in their own image is credible, so we show them. Nothing verifies that SBOM, though, so the Known CVEs signal does not grade the image from it.

ID CVE Severity Vector Fix available
GHSA-xcq7-p3pf-p88h CVE-2026-114603 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L yes
GHSA-42gh-23hr-vphw CVE-2026-119206 high yes
GHSA-4vqv-7265-gm2w CVE-2026-119207 high yes
GHSA-5849-834g-hvw5 CVE-2026-119203 high yes
GHSA-62m5-6wh8-28x7 CVE-2026-119208 high yes
GHSA-cggf-277g-3q54 CVE-2026-119204 high yes
GHSA-mfr5-77xh-9j7h CVE-2026-119205 high yes
GHSA-x3rh-gjgm-fmqc CVE-2026-119209 high yes

Background: What a vulnerability scan can and cannot prove →

MCP tools

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 →

Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.

Install

How do I install the io.github.TinySuiteHQ/tinysearch MCP server?

io.github.TinySuiteHQ/tinysearch runs locally as a container image, launched with docker run --rm -i -e MCP_TRANSPORT -e TINYSEARCH_CONFIG_PATH -e SEARXNG_URL -e TINYSEARCH_EMBEDDING_BACKEND -e TINYSEARCH_EMBEDDING_MODEL -e OTEL_SERVICE_NAME -e OTEL_EXPORTER_OTLP_ENDPOINT -e OTEL_EXPORTER_OTLP_PROTOCOL -e OTEL_EXPORTER_OTLP_HEADERS -e OTEL_RESOURCE_ATTRIBUTES -e OTEL_TRACES_EXPORTER -e OTEL_METRICS_EXPORTER -e OTEL_SDK_DISABLED docker.io/marcellm01/tinysearch:v0.6.8. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

oci · docker.io/marcellm01/tinysearch

# add to Claude Code
claude mcp add tinysuitehq-tinysearch -- docker run --rm -i -e MCP_TRANSPORT -e TINYSEARCH_CONFIG_PATH -e SEARXNG_URL -e TINYSEARCH_EMBEDDING_BACKEND -e TINYSEARCH_EMBEDDING_MODEL -e OTEL_SERVICE_NAME -e OTEL_EXPORTER_OTLP_ENDPOINT -e OTEL_EXPORTER_OTLP_PROTOCOL -e OTEL_EXPORTER_OTLP_HEADERS -e OTEL_RESOURCE_ATTRIBUTES -e OTEL_TRACES_EXPORTER -e OTEL_METRICS_EXPORTER -e OTEL_SDK_DISABLED docker.io/marcellm01/tinysearch:v0.6.8

This image reads MCP_TRANSPORT, TINYSEARCH_CONFIG_PATH, SEARXNG_URL, TINYSEARCH_EMBEDDING_BACKEND, TINYSEARCH_EMBEDDING_MODEL, OTEL_SERVICE_NAME, OTEL_EXPORTER_OTLP_ENDPOINT, OTEL_EXPORTER_OTLP_PROTOCOL, OTEL_EXPORTER_OTLP_HEADERS, OTEL_RESOURCE_ATTRIBUTES, OTEL_TRACES_EXPORTER, OTEL_METRICS_EXPORTER and OTEL_SDK_DISABLED. Set them in your client's env block for this server; docker run -e passes each one through to the container.

Common questions

What is the io.github.TinySuiteHQ/tinysearch MCP server?

io.github.TinySuiteHQ/tinysearch is an MCP server listed in the public MCP registry as io.github.TinySuiteHQ/tinysearch. Fast discovery search and self-hosted web research for MCP agents. This page covers its container image (docker.io/marcellm01/tinysearch).

Is the io.github.TinySuiteHQ/tinysearch MCP server safe to use?

io.github.TinySuiteHQ/tinysearch scores 10 out of 100 on VerifyMCP. The SBOM its publisher attached lists packages with 8 known advisories as of 5 November 2026. We do not grade that SBOM, as nothing verifies it. 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.

Is the io.github.TinySuiteHQ/tinysearch MCP server still maintained?

io.github.TinySuiteHQ/tinysearch 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 io.github.TinySuiteHQ/tinysearch MCP server under?

io.github.TinySuiteHQ/tinysearch declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.