Item detail
github.com

stacklok/toolhive

RepoRadar surfaced stacklok/toolhive — a developer tool — into the Radar section, where it sits at Silver tier with a 'try now' verdict. Its strongest signal is workflow potential, scored 9.4 out of 10.

Score7.9
Popularity74.0
Risknone
TierSilver
Score breakdown
Usefulness8.0
Novelty7.0
Momentum8.0
Maturity7.3
Open-source/build8.4
Evidence7.2
Workflow potential9.4
Setup ease8.8

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

Why it matters

Useful for developers and platform teams who want to run MCP servers in production with per-request auth, audit logs, and a Kubernetes operator — without rolling their own proxy, registry, and policy layer.

Who should use it

platform teams that need to standardize on MCP across the org with per-request auth and audit logs enterprise teams with SaaS-prohibited data that need a self-hostable MCP registry / gateway / runtime developer teams that want to run MCP servers in production with semantic tool search to cut token cost Kubernetes platform teams that want a Helm-installable MCP operator with OTel + Prometheus observability security teams that need an MCP-specific policy enforcement layer with OIDC / OAuth integration

Who should skip it

Consider stacklok/toolhive lower priority if you already have a working solution in this category.

About this signal

stacklok/toolhive is tracked by RepoRadar as a developer tool in the Radar section. It was first seen on 2026-06-17 and last updated on 2026-06-17. The current verdict is 'try now' with a Silver tier and easy setup difficulty. stacklok/toolhive leads on workflow potential (9.4) and setup ease (8.8); its lowest signal is novelty (7.0), 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. The score, tier, risk label, and verdict on this page are never influenced by sponsorship, ads, or tips — they reflect only the usefulness, popularity, novelty, momentum, maturity, and evidence signals described in the RepoRadar methodology.

How this item is evaluated

RepoRadar assigned stacklok/toolhive a composite score of 7.9 out of 10, placing it in the Silver tier. This score combines weighted sub-signals: usefulness (35%), novelty (18%), momentum (14%), maturity (10%), open-source/build quality (7%), evidence quality (6%), workflow potential (6%), and setup ease (4%). Popularity is tracked separately at 74.0 and never affects the composite score or tier. The risk label of 'none' reflects inherent user-impacting hazards, not generic novelty. Items with no risk flag may still require normal code review before production use.

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

No inherent user-impacting risk is flagged from the captured evidence.

Evidence links
Closest alternatives / related signals
mcp mcp-platform stacklok kubernetes-operator self-hosted oidc oauth semantic-search
Verification record

What RepoRadar actually verified

Discovered

Automated discovery and source capture. Last checked 2026-08-03T18:56:10Z.

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 →

38 dated snapshots retained from 2026-06-17 through 2026-08-03; 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.9 current · +0.0 net
Repository momentum9.0 current · +1.0 net
GitHub stars (observed)1,987 current · +47 net
GitHub stars1,987 exact observation
Versionv0.41.0
Last release2026-07-28T17:10:55Z
Maintenanceactive
Current risknone
Current verdicttry now
Pricing baselineNo structured commercial pricing baseline
Pricing checkedNot applicable or not recorded
Pricing freshnessNo dated commercial pricing review
Integrations baselineModel Context Protocol

Recent dated points

DateScoreMomentumStarsRiskVerdictMaintenance
2026-08-037.99.01,987nonetry nowactive
2026-08-027.99.31,987nonetry nowactive
2026-08-017.99.01,984nonetry nowactive
2026-07-317.98.0Not recordednonetry nownot recorded
2026-07-307.98.0Not recordednonetry nownot recorded
2026-07-297.99.31,979nonetry nowactive
2026-07-287.99.01,977nonetry nowactive
2026-07-217.99.01,948nonetry nowactive
2026-07-207.99.01,948nonetry nowactive
2026-07-197.99.01,948nonetry nowactive
2026-07-187.99.01,948nonetry nowactive
2026-07-177.99.01,948nonetry nowactive

Why the record changed

stars changed

Stars changed: 1984 → 1987.

stars changed

Stars changed: 1977 → 1979.

version changed

Version changed: v0.40.1 → v0.41.0.

stars changed

Stars changed: 1948 → 1977.

version changed

Version changed: v0.39.0 → v0.40.1.

stars changed

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

stars changed

Stars changed: 1940 → 1947.

version changed

Version changed: v0.34.0 → v0.39.0.