Skip to content

cockroachdb/cockroachdb-mcp-server

Star momentum, maintenance concentration, contributor health, and codebase change — one report built from public repository data.

Open on GitHub
Stars
3
History since
2026
Latest star
Jul 2026

Star history

Last 30 days
+3
Last 90 days
+3
Stars / day
0.2
Cumulative stars

stars from July 3, 2026 to July 22, 2026, peaking at 3.3 STARS1 MO3JUL 2026JUL 2026

3 stars on July 22, 2026.

stars by date
Datestars
July 3, 20261
July 7, 20262
July 22, 20263

The commit history reads cockroachdb/cockroachdb-mcp-server a second time

methodology

Fix-labelled changes, file change frequency, ownership concentration and maintenance cadence, each computed from this repository's analyzed commit window. None of them is derived from stars, which is why they are allowed to disagree with the curve above.

Fix-labelled changes
Fix-labelled changes for cockroachdb/cockroachdb-mcp-server
File change frequency
File change frequency for cockroachdb/cockroachdb-mcp-server
Bus factor
Bus factor for cockroachdb/cockroachdb-mcp-server
Maintenance pulse
Maintenance pulse for cockroachdb/cockroachdb-mcp-server
Contributors
Contributors for cockroachdb/cockroachdb-mcp-server
Language activity
Language activity for cockroachdb/cockroachdb-mcp-server
Commit activity
Commit activity for cockroachdb/cockroachdb-mcp-server
Recent TODO/FIXME movement
Recent TODO/FIXME movement for cockroachdb/cockroachdb-mcp-server

Attention is not adoption.

Stars against usage

No published package was detected for this repository, so there is nothing to lay over star growth.

Earned badges

badge studio

Maintenance, ownership and star-momentum signals, computed from the same commit and star history and embeddable as static images.

Reading badge evidence for cockroachdb/cockroachdb-mcp-server.

Notes on cockroachdb/cockroachdb-mcp-server

How many stars does cockroachdb/cockroachdb-mcp-server have?
GitHub currently reports 3 stars for cockroachdb/cockroachdb-mcp-server, with about 3 of them added in the last 90 days.
How fast is cockroachdb-mcp-server growing?
cockroachdb/cockroachdb-mcp-server gained about 3 stars over the last 90 days of its history (about 3 in the last 30) — figures are approximate for older repos, whose star history is downsampled.
Is cockroachdb-mcp-server still active?
cockroachdb/cockroachdb-mcp-server is still attracting attention — about 3 new GitHub stars in the most recent 30 days of its history. For commit-level signals, see the commit activity heatmap, commit trend, and contributors charts on this page.
When was cockroachdb-mcp-server created?
cockroachdb/cockroachdb-mcp-server was created on November 10, 2025 and earned its first GitHub star in Jul 2026.

Put this drawing in your README

markdown for agents

The block below publishes the chart with its source and coverage date stated beside it — the same three facts the title block above shows, as text a reader can check. The prompt underneath hands a coding agent the badges and repo-health charts as well.

README.md · cockroachdb/cockroachdb-mcp-server star history
<a href="https://gitdebt.com/cockroachdb/cockroachdb-mcp-server?ref=readme">
  <picture>
    <source media="(prefers-color-scheme: dark)" srcset="https://api.gitdebt.com/api/repos/cockroachdb/cockroachdb-mcp-server/chart.svg?theme=dark" />
    <img alt="cockroachdb/cockroachdb-mcp-server star history" src="https://api.gitdebt.com/api/repos/cockroachdb/cockroachdb-mcp-server/chart.svg?theme=light" />
  </picture>
</a>

<sub>Star history source: GitHub star history · Covers through November 14, 2026 · Still updating — <a href="https://gitdebt.com/cockroachdb/cockroachdb-mcp-server?ref=readme">gitdebt</a></sub>

Light and dark variants, alt text, and one provenance line. Provenance is text in your README, never baked into the image URL, so the chart stays cacheable.

Paste it into Claude Code, Cursor, Codex, or any coding agent with your checkout open. It carries the measured numbers, the exact snippets, and the rules — including replacing an existing star-history widget in place rather than stacking a second chart under it.