Star Trajectory
Classify a repo’s GitHub star momentum and get a calibrated odds-style read on hitting 100 stars within 48 hours before you commit to building or promoting it.
Overview
Star Trajectory is an MCP server for the Idea phase that classifies GitHub star momentum with explicit rules and projects calibrated 100-star/48h outcomes for repos you evaluate with your agent.
What is this MCP server?
- Rule-based, transparent trajectory labels instead of opaque ML-only scores
- Calibrated projection for reaching 100 stars within a 48-hour window
- Stdio MCP transport via PyPI package `star-trajectory` (uvx runtime)
- Use from Claude Code, Cursor, or Codex to reason about launch timing with your agent
- Server version 0.1.0
- Single stdio transport package on PyPI (identifier star-trajectory)
- Projection target framed as 100 stars within 48 hours
What problem does it solve?
You cannot tell from a single star count whether a repo is quietly accelerating, stalling, or worth cloning before you invest a weekend build.
Who is it for?
Builders comparing GitHub repos, OSS launch candidates, or competitor traction during early research with Claude Code or Cursor.
Skip if: Teams that need enterprise analytics warehouses, private GitHub org metrics, or guaranteed growth forecasts without public star history.
What do I get? / Deliverables
After registering the server, your agent can return labeled trajectories and a calibrated short-window star projection you can cite in go/no-go notes.
- Transparent trajectory classification for a target GitHub repo
- Calibrated 100-star-within-48h style projection output usable in agent research notes
Recommended MCP Servers
Journey fit
Solo builders research traction signals in the idea phase before picking repos, templates, or open-source bets to fork or imitate. Star-trajectory scoring fits discovery and trend research—not implementation—when you compare GitHub projects side by side.
How it compares
GitHub traction analytics MCP, not a code generator or deployment skill.
Common Questions / FAQ
Who is star-trajectory for?
Indie and solo builders who use AI coding agents to research GitHub repos and want explainable star-momentum signals before they commit to a build or launch.
When should I use star-trajectory?
Use it during idea and competitor research when you need a quick, rule-based trajectory label and a calibrated 100-star/48h projection for public repositories.
How do I add star-trajectory to my agent?
Add the stdio MCP server using the PyPI identifier `star-trajectory` with the uvx runtime hint, then point Claude Code, Cursor, or another MCP client at that server entry.