Your proof, portable.
Rolemate speaks MCP, the open protocol your coding agent already uses for tools. One line connects your agent to your verified Signal Score and your Trackathon Build Pulse. Candidate-owned, public signal only.
Connect your agent
Pick your agent and click. Each path carries its copy fallback.
claude.ai and Claude Desktop
Works on your phone too. Open Settings, then Connectors, then Add custom connector. Paste this URL and the tools join every chat.
https://rolemateapp.com/api/mcpCursor
One click installs the server. Cursor opens, confirms, done.
VS Code
One click opens VS Code and adds the server to your MCP settings.
Claude Code
For terminal people. The button opens a session with the add command filled in. Read it, press Enter, connected. The same line pastes into any terminal.
claude mcp add --transport http rolemate https://rolemateapp.com/api/mcpCodex and every other MCP agent connect the same way: copy the config and point it at the server URL.
Six tools, one boundary
Every tool reads public, candidate-owned signal. Private repositories, prompts, and employer data are out of scope by design.
rolemate_score_github
The full Signal Score on a public GitHub handle: 0-100, percentile, strengths, gaps, anti-gaming flags.
rolemate_signal_summary
The one-paragraph read: score, percentile, verdict.
rolemate_trackathon_pulse
How you built inside a window: cadence, consistency, momentum, built in-window.
rolemate_trackathon_team_pulse
How your team built together: shared repos, review exchanges, load balance, overlap hours.
rolemate_trackathon_leaderboard
Live standings for a registered event.
rolemate_trackathon_checkpoint
Log an opt-in milestone during an event, the moments a commit log cannot show.
Why this exists
Your agent is where you build, so it is where your proof should live. Score yourself as you ship, read your Build Pulse during an event, and carry a verified record to the roles that fit it. The candidate holds the data; the score travels with you.