Item detail
github.com

IBM/mcp-context-forge

RepoRadar surfaced IBM/mcp-context-forge — a developer tool — into the AI Gateway section, where it sits at Gold tier with a 'try now' verdict. Its strongest signal is workflow potential, scored 9.6 out of 10.

Score8.5
Popularity86.0
Risknone
TierGold
Score breakdown
Usefulness9.0
Novelty8.0
Momentum8.0
Maturity8.4
Open-source/build8.4
Evidence7.2
Workflow potential9.6
Setup ease6.4

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

Why it matters

Useful for platform and infra teams that need a vendor-neutral, production-grade AI gateway to federate the explosion of MCP servers, A2A agents, and REST/gRPC APIs behind one observable, governable endpoint — without standing up a custom Envoy/Istio stack or wiring their own OAuth/registry.

Who should use it

platform teams that need to federate the explosion of MCP servers, A2A agents, and REST/gRPC APIs behind one endpoint infra teams that need a vendor-neutral, observable, governable AI gateway without writing their own Envoy/Istio stack security teams that need OAuth 2.0 (client + server modes), rate limiting, retries, and reverse proxy for AI traffic observability teams that need OpenTelemetry tracing for MCP/A2A/REST calls with Phoenix/Jaeger/Zipkin backends platform teams running multi-cluster K8s that need Redis-backed federation and cache for the AI gateway layer developers who want a PyPI-installable gateway (`mcp-contextforge-gateway`) and a Docker image, not a custom build

Who should skip it

Consider IBM/mcp-context-forge lower priority if you already have a working solution in this category.

About this signal

IBM/mcp-context-forge is tracked by RepoRadar as a developer tool in the AI Gateway section. First seen 2026-06-17; the source record was last checked on 2026-06-17. The current verdict is 'try now' with a Gold tier and moderate setup difficulty. Across RepoRadar's eight signals, IBM/mcp-context-forge is strongest on workflow potential (9.6) and practical usefulness (9.0) and weakest on setup ease (6.4) — a profile worth weighing against your own priorities. 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 IBM/mcp-context-forge record combines a 8.5/10 composite score with separate popularity (86.0), risk (none), and setup (moderate) 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

3,914 stars is healthy but the project is still fast-evolving — pin versions and review changelogs before production; IBM-owned but Apache-2.0 with no CLA on contributions — vendor-neutral on paper, monitor IBM's product direction in case priorities shift.

Evidence links
Closest alternatives / related signals
mcp a2a rest grpc gateway registry proxy opentelemetry
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 →

48 dated snapshots retained from 2026-06-17 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 score8.5 current · +0.0 net
Repository momentum9.3 current · +1.3 net
GitHub stars (observed)4,315 current · +234 net
GitHub stars4,315 exact observation
Versionv1.0.7
Last release2026-08-05T18:07:27Z
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-138.59.34,315nonetry nowactive
2026-08-128.59.34,306nonetry nowactive
2026-08-118.59.34,297nonetry nowactive
2026-08-108.59.34,293nonetry nowactive
2026-08-098.59.34,285nonetry nowactive
2026-08-088.59.64,281nonetry nowactive
2026-08-078.59.34,183nonetry nowactive
2026-08-068.58.0Not recordednonetry nownot recorded
2026-08-058.58.0Not recordednonetry nownot recorded
2026-08-048.59.34,183nonetry nowactive
2026-08-038.59.34,183nonetry nowactive
2026-08-028.59.34,175nonetry nowactive

Why the record changed

stars changed

Stars changed: 4306 → 4315.

stars changed

Stars changed: 4297 → 4306.

stars changed

Stars changed: 4293 → 4297.

stars changed

Stars changed: 4285 → 4293.

stars changed

Stars changed: 4281 → 4285.

version changed

Version changed: v1.0.6 → v1.0.7.

stars changed

Stars changed: 4183 → 4281.

stars changed

Stars changed: 4175 → 4183.

stars changed

Stars changed: 4173 → 4175.

stars changed

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

stars changed

Stars changed: 4150 → 4154.

stars changed

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