vibestreak
io.github.hattray/vibestreakhattraystreamable-httpv0.3.5Scanned
AI coding streaks and leaderboards: profiles, heatmaps, who coded with AI today.
4 tools: 4 only read.
- Reads private data · 2
- Reads text others write · 1
- Can send data out · 0
- No findings
Anlyon alternative
Run the operations that matter as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
4 tools
Only reads 4Show 4 read-only tools
get_leaderboardThe vibestreak leaderboard of AI-assisted developers, ranked by consistency (active days), commits shipped with an AI co-author, current streak, or tokens.Reads private dataNo findings
Why it is in this group
- The name "get_leaderboard" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "commit": it reads repositories.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_my_profileThe 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 d…No findings
Why it is in this group
- The name "get_my_profile" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_profileA 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), …Reads private dataReads text others writeNo findings
Why it is in this group
- The name "get_profile" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "commit": it reads repositories.
- untrusted-inputThe description's first sentence says "message": it reads messages, which other people can write.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_todayWho 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.No findings
Why it is in this group
- The name "get_today" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.
- Reads private data2
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 0.3.5. Values in angle brackets are yours to fill in.
claude mcp add --transport http vibestreak https://vibestreak.dev/mcpclaude mcp add --transport http vibestreak https://vibestreak.dev/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__vibestreak__get_leaderboard",
"mcp__vibestreak__get_profile",
"mcp__vibestreak__get_my_profile",
"mcp__vibestreak__get_today"
],
"ask": [],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as vibestreak. Review it before you use it.
Capability tags behind 2 rules
- mcp__vibestreak__get_leaderboard private-data
- mcp__vibestreak__get_profile private-data, untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://anlyon.dev/api/v1/servers/io.github.hattray/vibestreak/verify?hash=0f9baa24bc54622af92d38a6d3c20ecfd0e7e502439d856a798878b70a0e561e" | jq -e '.changed == false'Pinned hash 0f9baa24bc54, from Oct 26, 2026, 06:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://anlyon.dev/servers/io.github.hattray/vibestreak/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://anlyon.dev/servers/io.github.hattray/vibestreak)Source: MCP Registry. Synced Oct 26, 2026, 06:17 UTC.