io.github.MarcellM01/tinysearch
PYPI · TINYSUITE-SEARCH · 2 COMPONENTS
Self-hosted web research for MCP agents.
Available components
Last scanned (16 hours ago)
Scores higher than 8% of PyPI servers
Category Search and Retrieval
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 Security32
- Malware scan not yet available for this package.Unverified
- CVE check failed: a known high-severity CVE affects pypdf 6.14.2, a direct dependency. A fixed version is available. View diagnostics → Fail
- Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 9 of 110 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency74
- Repository check failed: the declared repository URL redirects; it must resolve directly. See how to fix → View diagnostics → Fail
- Cryptographically verified build provenance (signed, bound to MarcellM01/TinySearch). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 6 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability0
- Schema quality not yet verified: this package installed, but its server did not start, so we have no schema to assess.Unverified
Stability & Change Management0
- Stability not yet verified: this package installed, but its server did not start, so we have no schema to compare.Unverified
Tool Coverage0
- Tool coverage not yet verified: this package installed, but its server did not start, so we have no tool definitions to assess.Unverified
Tool Safety0
- Tool safety not yet verified: this package installed, but its server did not start, so we have no tool text to scan.Unverified
Capabilities0
- Protocol version not yet verified: this package installed, but its server did not start, so we never saw its MCP handshake.Unverified
Unverified: 5 categories
Categories scored 0 because our sandbox has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →
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.
- 4 Nov 26 −15
- CVE-2026-115585 affects this package: high ▼ security
- CVE-2026-103000 affects this package: high ▼ security
- CVE-2026-71870 affects this package: high ▼ security
- CVE-2026-84309 affects this package: high ▼ security
- CVE-2026-119209 affects this package: high ▼ security
- CVE-2026-102996 affects this package: high ▼ security
- CVE-2026-82398 affects this package: high ▼ security
- CVE-2026-115572 affects this package: high ▼ security
- CVE-2026-119207 affects this package: high ▼ security
- CVE-2026-113789 affects this package: high ▼ security
- CVE-2026-119206 affects this package: high ▼ security
- CVE-2026-113794 affects this package: high ▼ security
- CVE-2026-102995 affects this package: high ▼ security
- CVE-2026-115580 affects this package: high ▼ security
- CVE-2026-113786 affects this package: high ▼ security
- CVE-2026-102998 affects this package: high ▼ security
- CVE-2026-119208 affects this package: high ▼ security
- CVE-2026-119205 affects this package: high ▼ security
- CVE-2026-84311 affects this package: high ▼ security
- CVE-2026-113795 affects this package: high ▼ security
- CVE-2026-102993 affects this package: high ▼ security
- CVE-2026-102999 affects this package: high ▼ security
- CVE-2026-119203 affects this package: high ▼ security
- CVE-2026-84310 affects this package: high ▼ security
- CVE-2026-119204 affects this package: high ▼ security
- CVE-2026-102994 affects this package: high ▼ security
- CVE-2026-113793 affects this package: high ▼ security
- CVE-2026-113792 affects this package: high ▼ security
- CVE-2026-71852 affects this package: high ▼ security
- CVE-2026-113790 affects this package: high ▼ security
- CVE-2026-102997 affects this package: high ▼ security
- CVE-2026-113791 affects this package: high ▼ security
- Malware scan: pass → unverified ▼ security
- 3 Nov 26 0
- CVE-2026-115572 affects this package: high ▼ security
- CVE-2026-102996 affects this package: high ▼ security
- CVE-2026-115585 affects this package: high ▼ security
- CVE-2026-119209 affects this package: high ▼ security
- CVE-2026-71870 affects this package: high ▼ security
- CVE-2026-84309 affects this package: high ▼ security
- CVE-2026-103000 affects this package: high ▼ security
- CVE-2026-113791 affects this package: high ▼ security
- CVE-2026-102997 affects this package: high ▼ security
- CVE-2026-113790 affects this package: high ▼ security
- CVE-2026-71852 affects this package: high ▼ security
- CVE-2026-113792 affects this package: high ▼ security
- CVE-2026-113793 affects this package: high ▼ security
- CVE-2026-102994 affects this package: high ▼ security
- CVE-2026-119204 affects this package: high ▼ security
- CVE-2026-84310 affects this package: high ▼ security
- CVE-2026-119203 affects this package: high ▼ security
- CVE-2026-102999 affects this package: high ▼ security
- CVE-2026-102993 affects this package: high ▼ security
- CVE-2026-113795 affects this package: high ▼ security
- CVE-2026-84311 affects this package: high ▼ security
- CVE-2026-119205 affects this package: high ▼ security
- CVE-2026-119208 affects this package: high ▼ security
- CVE-2026-102998 affects this package: high ▼ security
- CVE-2026-113786 affects this package: high ▼ security
- CVE-2026-115580 affects this package: high ▼ security
- CVE-2026-102995 affects this package: high ▼ security
- CVE-2026-113794 affects this package: high ▼ security
- CVE-2026-119206 affects this package: high ▼ security
- CVE-2026-113789 affects this package: high ▼ security
- CVE-2026-119207 affects this package: high ▼ security
- CVE-2026-82398 affects this package: high ▼ security
- 2 Nov 26 0
- CVE-2026-115572 affects this package: high ▼ security
- CVE-2026-82398 affects this package: high ▼ security
- CVE-2026-102996 affects this package: high ▼ security
- CVE-2026-119209 affects this package: high ▼ security
- CVE-2026-115585 affects this package: high ▼ security
- CVE-2026-71870 affects this package: high ▼ security
- CVE-2026-84309 affects this package: high ▼ security
- CVE-2026-103000 affects this package: high ▼ security
- CVE-2026-113791 affects this package: high ▼ security
- CVE-2026-102997 affects this package: high ▼ security
- CVE-2026-113790 affects this package: high ▼ security
- CVE-2026-71852 affects this package: high ▼ security
- CVE-2026-113792 affects this package: high ▼ security
- CVE-2026-113793 affects this package: high ▼ security
- CVE-2026-102994 affects this package: high ▼ security
- CVE-2026-119204 affects this package: high ▼ security
- CVE-2026-84310 affects this package: high ▼ security
- CVE-2026-119203 affects this package: high ▼ security
- CVE-2026-102999 affects this package: high ▼ security
- CVE-2026-102993 affects this package: high ▼ security
- CVE-2026-113795 affects this package: high ▼ security
- CVE-2026-84311 affects this package: high ▼ security
- CVE-2026-119205 affects this package: high ▼ security
- CVE-2026-119208 affects this package: high ▼ security
- CVE-2026-102998 affects this package: high ▼ security
- CVE-2026-113786 affects this package: high ▼ security
- CVE-2026-115580 affects this package: high ▼ security
- CVE-2026-102995 affects this package: high ▼ security
- CVE-2026-113794 affects this package: high ▼ security
- CVE-2026-119206 affects this package: high ▼ security
- CVE-2026-113789 affects this package: high ▼ security
- CVE-2026-119207 affects this package: high ▼ security
- 1 Nov 26 +15
- CVE-2026-115585 affects this package: high ▼ security
- CVE-2026-71870 affects this package: high ▼ security
- CVE-2026-84309 affects this package: high ▼ security
- CVE-2026-103000 affects this package: high ▼ security
- CVE-2026-113791 affects this package: high ▼ security
- CVE-2026-102997 affects this package: high ▼ security
- CVE-2026-113790 affects this package: high ▼ security
- CVE-2026-71852 affects this package: high ▼ security
- CVE-2026-113792 affects this package: high ▼ security
- CVE-2026-113793 affects this package: high ▼ security
- CVE-2026-102994 affects this package: high ▼ security
- CVE-2026-119204 affects this package: high ▼ security
- CVE-2026-84310 affects this package: high ▼ security
- CVE-2026-119203 affects this package: high ▼ security
- CVE-2026-102999 affects this package: high ▼ security
- CVE-2026-102993 affects this package: high ▼ security
- CVE-2026-113795 affects this package: high ▼ security
- CVE-2026-84311 affects this package: high ▼ security
- CVE-2026-119205 affects this package: high ▼ security
- CVE-2026-119208 affects this package: high ▼ security
- CVE-2026-102998 affects this package: high ▼ security
- CVE-2026-113786 affects this package: high ▼ security
- CVE-2026-115580 affects this package: high ▼ security
- CVE-2026-102995 affects this package: high ▼ security
- CVE-2026-113794 affects this package: high ▼ security
- CVE-2026-119206 affects this package: high ▼ security
- CVE-2026-113789 affects this package: high ▼ security
- CVE-2026-119207 affects this package: high ▼ security
- CVE-2026-115572 affects this package: high ▼ security
- CVE-2026-82398 affects this package: high ▼ security
- CVE-2026-102996 affects this package: high ▼ security
- CVE-2026-119209 affects this package: high ▼ security
- Malware scan: unverified → pass ▲ security
- 31 Oct 26 −15
- CVE-2026-115585 affects this package: high ▼ security
- CVE-2026-71870 affects this package: high ▼ security
- CVE-2026-84309 affects this package: high ▼ security
- CVE-2026-103000 affects this package: high ▼ security
- CVE-2026-113791 affects this package: high ▼ security
- CVE-2026-102997 affects this package: high ▼ security
- CVE-2026-113790 affects this package: high ▼ security
- CVE-2026-71852 affects this package: high ▼ security
- CVE-2026-113792 affects this package: high ▼ security
- CVE-2026-113793 affects this package: high ▼ security
- CVE-2026-102994 affects this package: high ▼ security
- CVE-2026-119204 affects this package: high ▼ security
- CVE-2026-84310 affects this package: high ▼ security
- CVE-2026-119203 affects this package: high ▼ security
- CVE-2026-102999 affects this package: high ▼ security
- CVE-2026-102993 affects this package: high ▼ security
- CVE-2026-113795 affects this package: high ▼ security
- CVE-2026-84311 affects this package: high ▼ security
- CVE-2026-119205 affects this package: high ▼ security
- CVE-2026-119208 affects this package: high ▼ security
- CVE-2026-102998 affects this package: high ▼ security
- CVE-2026-113786 affects this package: high ▼ security
- CVE-2026-115580 affects this package: high ▼ security
- CVE-2026-102995 affects this package: high ▼ security
- CVE-2026-113794 affects this package: high ▼ security
- CVE-2026-119206 affects this package: high ▼ security
- CVE-2026-113789 affects this package: high ▼ security
- CVE-2026-119207 affects this package: high ▼ security
- CVE-2026-115572 affects this package: high ▼ security
- CVE-2026-82398 affects this package: high ▼ security
- CVE-2026-102996 affects this package: high ▼ security
- CVE-2026-119209 affects this package: high ▼ security
- Malware scan: pass → unverified ▼ security
- 30 Oct 26 +15
- CVE-2026-102997 affects this package: high ▼ security
- CVE-2026-71870 affects this package: high ▼ security
- CVE-2026-84309 affects this package: high ▼ security
- CVE-2026-103000 affects this package: high ▼ security
- CVE-2026-113791 affects this package: high ▼ security
- CVE-2026-113790 affects this package: high ▼ security
- CVE-2026-71852 affects this package: high ▼ security
- CVE-2026-113792 affects this package: high ▼ security
- CVE-2026-113793 affects this package: high ▼ security
- CVE-2026-102994 affects this package: high ▼ security
- CVE-2026-84310 affects this package: high ▼ security
- CVE-2026-102999 affects this package: high ▼ security
- CVE-2026-102993 affects this package: high ▼ security
- CVE-2026-113795 affects this package: high ▼ security
- CVE-2026-84311 affects this package: high ▼ security
- CVE-2026-102998 affects this package: high ▼ security
- CVE-2026-113786 affects this package: high ▼ security
- CVE-2026-115580 affects this package: high ▼ security
- CVE-2026-102995 affects this package: high ▼ security
- CVE-2026-113794 affects this package: high ▼ security
- CVE-2026-113789 affects this package: high ▼ security
- CVE-2026-115572 affects this package: high ▼ security
- CVE-2026-82398 affects this package: high ▼ security
- CVE-2026-102996 affects this package: high ▼ security
- CVE-2026-115585 affects this package: high ▼ security
- Malware scan: unverified → pass ▲ security
- 29 Oct 26 −15
We did not load change detail this far back for this component, so this day may have recorded more than is shown.
- CVE-2026-113790 affects this package: high ▼ security
- CVE-2026-84309 affects this package: high ▼ security
- CVE-2026-71870 affects this package: high ▼ security
- CVE-2026-102997 affects this package: high ▼ security
- CVE-2026-113791 affects this package: high ▼ security
- CVE-2026-103000 affects this package: high ▼ security
- CVE-2026-102995 affects this package: high ▼ security
- 28 Oct 26 +15
We did not load change detail this far back for this component, so this day may have recorded more than is shown.
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 4 Nov 2026 · Analysed pypi/tinysuite-search@0.4.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | MarcellM01/TinySearch |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/MarcellM01/TinySearch/.github/workflows/pypi-publish.yml@refs/tags/v0.4.0 |
| Rekor log index | 2260476083 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:6ebb1e09908e5d8434dc20f626cdf28bc10174b3edfe9cbe23c76bf15004aa45 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Vulnerabilities 46 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-23w6-3w8w-8484 | CVE-2026-84310 | medium | yes | |
| GHSA-39mj-jf6j-2qj3 | CVE-2026-113794 | medium | 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-5hx5-vpf9-5wcv | CVE-2026-113786 | low | yes | |
| GHSA-5jq2-8x83-x246 | CVE-2026-102994 | high | yes | |
| GHSA-62m5-6wh8-28x7 | CVE-2026-119208 | high | yes | |
| GHSA-6c7f-9265-g8fw | CVE-2026-115572 | high | yes | |
| GHSA-6vvc-x485-93v7 | CVE-2026-113789 | medium | yes | |
| GHSA-763m-79hh-57f2 | CVE-2026-84311 | medium | yes | |
| GHSA-7mh2-4gg2-979f | CVE-2026-113795 | medium | yes | |
| GHSA-9mx8-4j7g-633p | CVE-2026-113793 | medium | yes | |
| GHSA-cgf9-327m-v77c | CVE-2026-113791 | medium | yes | |
| GHSA-cggf-277g-3q54 | CVE-2026-119204 | high | yes | |
| GHSA-f54x-cmq8-qg57 | CVE-2026-113790 | medium | yes | |
| GHSA-fc8x-2rww-xw9m | CVE-2026-82398 | medium | yes | |
| GHSA-fp3f-mc75-235c | CVE-2026-71870 | medium | yes | |
| GHSA-fp3h-c4fm-7vvf | CVE-2026-102995 | high | yes | |
| GHSA-fwg2-594c-jp42 | CVE-2026-71852 | medium | yes | |
| GHSA-g9cg-prrw-2r8q | CVE-2026-102996 | high | yes | |
| GHSA-gmh7-3g9r-mjh5 | CVE-2026-115580 | high | yes | |
| GHSA-jp53-mhqp-8xcg | CVE-2026-84309 | medium | yes | |
| GHSA-jr96-gvgh-j3r4 | CVE-2026-115585 | high | yes | |
| GHSA-jw7q-gvrg-4vj3 | CVE-2026-102997 | high | yes | |
| GHSA-mfr5-77xh-9j7h | CVE-2026-119205 | high | yes | |
| GHSA-php9-fj8v-98fj | CVE-2026-102998 | high | yes | |
| GHSA-qfv9-64jg-mh7p | CVE-2026-113792 | medium | yes | |
| GHSA-qv6h-rv94-w285 | CVE-2026-102993 | high | yes | |
| GHSA-v247-6f48-mgcj | CVE-2026-102999 | high | yes | |
| GHSA-w23x-9jrw-r45c | CVE-2026-103000 | high | yes | |
| GHSA-x3rh-gjgm-fmqc | CVE-2026-119209 | high | yes | |
| PYSEC-2026-3655 | CVE-2026-71870 | none | yes | |
| PYSEC-2026-3656 | CVE-2026-71852 | none | yes | |
| PYSEC-2026-3910 | CVE-2026-84310 | none | yes | |
| PYSEC-2026-3911 | CVE-2026-84311 | none | yes | |
| PYSEC-2026-3912 | CVE-2026-82398 | none | yes | |
| PYSEC-2026-3913 | CVE-2026-84309 | none | yes | |
| PYSEC-2026-4153 | CVE-2026-102994 | none | yes | |
| PYSEC-2026-4154 | CVE-2026-102995 | none | yes | |
| PYSEC-2026-4155 | CVE-2026-102996 | none | yes | |
| PYSEC-2026-4156 | CVE-2026-102997 | none | yes | |
| PYSEC-2026-4157 | CVE-2026-102998 | none | yes | |
| PYSEC-2026-4158 | CVE-2026-102993 | none | yes | |
| PYSEC-2026-4159 | CVE-2026-102999 | none | yes | |
| PYSEC-2026-4160 | CVE-2026-103000 | none | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 110 packages
| Packages resolved | 110 |
|---|---|
| Stale | 8 |
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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.
How do I install the io.github.MarcellM01/tinysearch MCP server?
io.github.MarcellM01/tinysearch runs locally as a PyPI package, launched with uvx tinysuite-search. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · tinysuite-search
claude mcp add marcellm01-tinysearch -- uvx tinysuite-search
What is the io.github.MarcellM01/tinysearch MCP server?
io.github.MarcellM01/tinysearch is an MCP server listed in the public MCP registry as io.github.MarcellM01/tinysearch. Self-hosted web research for MCP agents. This page covers its PyPI package (tinysuite-search).
Is the io.github.MarcellM01/tinysearch MCP server safe to use?
io.github.MarcellM01/tinysearch scores 24 out of 100 on VerifyMCP. We recorded 46 known advisories against it as of 4 November 2026. 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.
Is the io.github.MarcellM01/tinysearch MCP server still maintained?
io.github.MarcellM01/tinysearch is still listed as active in the MCP registry. We last reached this channel on 4 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.MarcellM01/tinysearch MCP server under?
io.github.MarcellM01/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.