vibestreak
REMOTE · VIBESTREAK.DEV
AI coding streaks and leaderboards: profiles, heatmaps, who coded with AI today.
Available components
Last scanned (18 hours ago)
Scores higher than 54% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Developer Tools
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability66
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 598 tokens (~149/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
- Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 26 Oct 26 65
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Probed https://vibestreak.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=vibestreak.dev | CN=WE1,O=Google Trust Services,C=US | 26 Oct 2026 | 24 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 88cd36d119e6621c0e802488e2eea3a6 |
| SANs: vibestreak.dev, www.vibestreak.dev, *.www.vibestreak.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of vibestreak.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| vibestreak.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://vibestreak.dev/mcp | Verified | 200 | |
| http (plaintext) | http://vibestreak.dev/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_leaderboard vibestreak leaderboard ~258
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.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | Start of a custom range (YYYY-MM-DD); needs `to`; replaces period. |
| limit | integer | – | How many rows. Default 10. |
| metric | string | – | What ranks people. Default consistency. |
| period | string | – | The window: today, the last 7/30/90 days in each person's own timezone, or all time. Default 30d. |
| to | string | – | End of a custom range (YYYY-MM-DD). |
| tool | string | – | Only this AI coding tool (claude = Claude Code). Default: all tools. |
| tools | array | – | Several AI tools at once: a day counts if any of them was used. Default: all tools. |
| verified | boolean | – | Only profiles whose shipped days GitHub's public calendars back up. |
| you | string | – | A handle whose row to include wherever it ranks. |
No output schema declared.
No examples provided.
get_my_profile My vibestreak profile ~106
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.
| Name | Type | Req | Description |
|---|---|---|---|
| tool | string | – | Only this AI coding tool (claude = Claude Code). Default: all tools. |
| weeks | integer | – | Heatmap weeks. Default 20. |
No output schema declared.
No examples provided.
get_profile vibestreak profile ~117
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.
| Name | Type | Req | Description |
|---|---|---|---|
| handle | string | yes | The vibestreak handle (their GitHub username), with or without @. |
| tool | string | – | Only this AI coding tool (claude = Claude Code). Default: all tools. |
| weeks | integer | – | Heatmap weeks. Default 20. |
No output schema declared.
No examples provided.
get_today Coding with AI today ~41
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the vibestreak MCP server?
vibestreak is a hosted endpoint at https://vibestreak.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · vibestreak.dev
claude mcp add --transport http hattray-vibestreak 'https://vibestreak.dev/mcp'
What is the vibestreak MCP server?
vibestreak is an MCP server listed in the public MCP registry as io.github.hattray/vibestreak. AI coding streaks and leaderboards: profiles, heatmaps, who coded with AI today. This page covers its hosted endpoint (https://vibestreak.dev/mcp).
Is the vibestreak MCP server safe to use?
vibestreak scores 69 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the vibestreak MCP server expose?
vibestreak exposes 4 tools: get_leaderboard, get_profile, get_my_profile, get_today. Their descriptions and schemas cost roughly 522 tokens of context every time the server is loaded.
Does the vibestreak MCP server require authentication?
No. We connected to vibestreak without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the vibestreak MCP server still maintained?
vibestreak is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.