Item detail
github.com

MarcellM01/TinySearch

MarcellM01/TinySearch is an MCP server in RepoRadar's MCP Servers section, holding Silver tier and a 'try now' verdict. Its strongest signal is workflow potential, scored 9.1 out of 10.

Score7.6
Popularity1.0
Risklow
TierSilver
Score breakdown
Usefulness8.0
Novelty7.0
Momentum8.0
Maturity5.6
Open-source/build8.4
Evidence7.2
Workflow potential9.1
Setup ease8.8

Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.

Why it matters

Useful for any developer or researcher who wants their local or hosted agent to do real web research with grounded sources (not 'here is what the LLM guessed') without depending on a hosted search API. The MCP surface is the right shape — search, crawl, rerank, extract, return a source-grounded prompt — so the calling agent sees a single tool call instead of a five-step shell pipeline. SearXNG by

Who should use it

Any developer or researcher who wants their local or hosted agent to do real web research with grounded sources (not 'here is what the LLM guessed') without depending on a hosted search API — TinySearch returns a source-grounded prompt with attached URLs, so the LLM answer is auditable Privacy-sensitive users who want web research without sending queries to a third party — SearXNG meta-search + local ONNX embeddings by default means the whole stack can run on a laptop end-to-end without an external API call Hosted agent developers who need a real Streamable HTTP MCP surface (not just stdio) — TinySearch is one of the few self-hosted MCP servers that ships Streamable HTTP out of the box, which is the right transport for cloud agents Anyone tired of '5-step install to get web search working in my agent' — the Docker Compose quickstart pulls config directly from GitHub, so the install is one line and there is no config file to author Anyone who needs SearXNG meta-search by default instead of being locked into one search vendor — SearXNG queries dozens of backends, so a TinySearch user inherits vendor-neutral results and is not subject to one vendor's rate limits or content policies Anyone building a multi-MCP-server stack who wants TinySearch's source-grounded prompt surfaced via lazy discovery (instead of dumping every web-search tool's full definition on every request) — pair with Toolport (cycle 330) so TinySearch becomes a meta-tool the agent calls on demand

Who should skip it

Consider MarcellM01/TinySearch lower priority if you already have a working solution in this category.

About this signal

MarcellM01/TinySearch is tracked by RepoRadar as an MCP server in the MCP Servers section. First seen 2026-07-04; the source record was last checked on 2026-07-04. The current verdict is 'try now' with a Silver tier and easy setup difficulty. MarcellM01/TinySearch leads on workflow potential (9.1) and setup ease (8.8); its lowest signal is maturity (5.6), so factor that in before investing setup time. This page summarizes the public evidence on the linked source page and states where additional review is still needed.

How this item is evaluated

The MarcellM01/TinySearch record combines a 7.6/10 composite score with separate popularity (1.0), risk (low), and setup (easy) signals. See the scoring methodology for the current weights and evidence definitions.

Putting this into practice? Read How to vet an AI agent or MCP server before you wire it in for the checklist behind this score.

Risk explanation

Risk label is still being reviewed from the captured evidence. Treat the item as unknown-risk until you review the linked source, permissions, setup path, and data access.

Evidence links
Closest alternatives / related signals
mcp mcp-server web-research searxng duckduckgo fastapi streamable-http local-embeddings
Verification record

What RepoRadar actually verified

Discovered

Automated discovery and source capture. Last checked 2026-08-13T20:20:15Z.

No editorial or hands-on review is claimed. This record remains at Discovered.

Verification sources

Longitudinal intelligence

How this decision record is moving

Raw history JSON →

32 dated snapshots retained from 2026-07-04 through 2026-08-13; see the snapshot index for explicit coverage gaps. Stars, version, release, pricing, integration, risk, maintenance, verdict, score, and momentum fields remain explicit even when a source has not reported them. Repository momentum is a normalized 0–10 RepoRadar signal; GitHub stars appear only where the popularity monitor retained exact timestamped observations.

RepoRadar score7.6 current · +0.0 net
Repository momentum9.0 current · +1.0 net
GitHub stars (observed)181 current · +24 net
GitHub stars181 exact observation
Versionv0.5.0
Last release2026-08-08T10:32:52Z
Maintenanceactive
Current risklow
Current verdicttry now
Pricing baselineNo structured commercial pricing baseline
Pricing checkedNot applicable or not recorded
Pricing freshnessNo dated commercial pricing review
Integrations baselineNo structured integrations recorded

Recent dated points

DateScoreMomentumStarsRiskVerdictMaintenance
2026-08-137.69.0181lowtry nowactive
2026-08-127.69.0181lowtry nowactive
2026-08-117.69.0180lowtry nowactive
2026-08-107.69.0180lowtry nowactive
2026-08-097.68.5180lowtry nowactive
2026-08-087.69.0181lowtry nowactive
2026-08-077.69.0178lowtry nowactive
2026-08-067.68.0Not recordedlowtry nownot recorded
2026-08-057.68.0Not recordedlowtry nownot recorded
2026-08-047.69.0178lowtry nowactive
2026-08-037.69.0178lowtry nowactive
2026-08-027.69.0177lowtry nowactive

Why the record changed

stars changed

Stars changed: 180 → 181.

stars changed

Stars changed: 181 → 180.

version changed

Version changed: v0.4.3 → v0.5.0.

stars changed

Stars changed: 178 → 181.

version changed

Version changed: v0.4.2 → v0.4.3.

stars changed

Stars changed: 177 → 178.

stars changed

Source-observed stars changed: 176 → 177. This reports the retained observation delta and does not infer why the upstream change occurred.

stars changed

Stars changed: 167 → 171.

version changed

Version changed: v0.4.0 → v0.4.1.

stars changed

Stars changed: 162 → 167.

version changed

Version changed: v0.3.2 → v0.4.0.

version changed

Version changed: v0.3.1 → v0.3.2.