Remote MCP server for vibestreak, exposing AI-coding streak leaderboards, developer profiles, heatmaps and daily activity.
What you can do
Read leaderboards of AI-assisted developers ranked by active days, AI co-authored commits, streak or tokens, filtered by date range, AI tool or GitHub verification
Read any developer's public profile: current and longest streak, level, totals, AI tools and a text heatmap
Read the connected user's own profile, including hidden profiles, with streak status and days to next level
See who has coded with AI today, with their streaks and whose streak ends at midnight
When to use it
Useful when you want an assistant to look up vibestreak streaks, compare developers on the leaderboard, or check whether your own streak is still alive today.
Requirements
A remote streamable HTTP endpoint; no local package or runtime. The personal profile tool needs a vibestreak CLI token sent as an Authorization Bearer header; the other tools need no declared credentials.
Before you install
The personal profile tool requires a vibestreak CLI token as an Authorization Bearer header, so treat it as a secret. Counts are self-reported by the vibestreak CLI, and only GitHub-verified profiles have shipped days backed by public contribution calendars. Handles are GitHub usernames, so lookups expose public developer activity.
Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.hattray%2Fvibestreak/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.
The vibestreak leaderboard of AI-assisted developers, ranked by consistency (active days), commits shipped with an AI co-author, current streak, or tokens. Optionally a date range, one or more AI tools, or only GitHub-verified profiles. Use `you` to include a particular person's rank.
A developer's public vibestreak profile: current and longest streak, streak level, whether they were active today, totals (active days, commits shipped with AI, messages, tokens), their AI tools, and a text heatmap of recent weeks.
Parameterstoolweekshandlerequired
get_my_profile
My vibestreak profile
The profile of the person this connection belongs to (it needs their vibestreak CLI token as `Authorization: Bearer …`), even if their profile is hidden: streak, whether today is done or the streak ends at midnight, the days to their next level, totals and a heatmap.
Parameterstoolweeks
get_today
Coding with AI today
Who on vibestreak has coded with AI today (each in their own timezone), with their streaks, and whose streak ends at midnight unless they code today.
Takes no parameters.
Version history
1
v0.3.5LatestOct 26, 2026
Score
83%
83% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listedRequired15 pts
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.