MCP server for forging god-tier GitHub profiles — animated SVGs, bento grids, live data widgets, and full CI automation
GodProfile has 16 tools with inconsistent quality. Most tools have descriptions (good), but parameter schemas are incomplete or missing type information. Many parameters lack descriptions entirely. Tool names are descriptive but some combine multiple concerns (e.g., 'fetch_github_trophies_live' both fetches AND renders). No output schemas documented. Error handling is absent from visible code. The server imports core modules but actual implementations are not visible, making it impossible to verify schema completeness or error handling patterns.
Generates a pure SVG animated banner (800x200) with gradient background and sequential text fade-in, no Playwright required — entirely stdlib SVG generation, optionally saves to file path
Fetches LIVE GitHub stats (stars, commits, PRs, issues, repos, followers) via the GitHub API using stdlib urllib only, then renders an SVG trophy case. Optional personal access token for higher rate limits and private commit counts
Fetches the latest blog posts from Dev.to, Medium, Hashnode, or any RSS/Atom URL and returns a themed SVG card (400x280) displaying up to 5 recent post titles and dates using stdlib urllib only
Fetches the currently playing (or recently played) track from the Spotify API and renders a themed SVG card with track name, artist, and animated equalizer bars
Fetches LIVE coding stats from the WakaTime API (last 7 days) and renders a themed SVG bar chart showing language percentages with animated bars using stdlib only
Parameter schemas incomplete: 'data' and 'stats' parameters are typed as 'object' with no nested schema definition. LLMs cannot infer required fields or structure.
No output schemas documented. Tools return strings (SVG, YAML, etc.) but LLMs cannot plan downstream operations without knowing response structure.
Credentials exposed as parameters: 'github_token', 'api_key', 'access_token' are tool parameters. These will be logged in traces and prompt history.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 52 | 2026-07-28+ | v2 |
Creates a pure SVG infinitely scrolling horizontal band of technology name badges using CSS @keyframes with duplicated rows for seamless infinite loop, no external dependencies
Overhauls simple tech stack lists into visually stunning, data-connected neural network visualizations with Bezier curves and animated particles
Parses a user's standard GitHub Markdown and restructures it into modern, asymmetric bento grid layout
Generates a 400x400 SVG isometric 3D globe using real spherical-to-isometric projection math with 12 longitude + 8 latitude grid lines, optional highlight points, and slow animated rotation via SVG animateTransform
Generates an 800x200 SVG trophy case with up to 6 trophies (Stars, Commits, PRs, Issues, Repos, Followers) ranked S/A/B/C with animated glow for S-rank trophies
Generates a 400x100 SVG 'Now Playing' card mimicking the Spotify UI with animated equalizer bars when is_playing=True, themed colors, and album art placeholder. Also returns a GitHub Actions cron workflow YAML for live Spotify sync if credentials are provided
Generates extremely high-fidelity glassmorphic SVG cards with 12px borders and themed styling
Generates a 600x340 SVG animated terminal window with macOS-style window chrome, alternating shell commands and outputs with sequential animation via CSS @keyframes and blinking cursor at end
Renders a 400x220 SVG horizontal bar chart of coding language activity with placeholder data if data is empty, themed via theme tokens
Generates a GitHub Actions workflow YAML that runs Platane/snk to animate the contribution grid as a snake game, injecting custom theme hex colors into the workflow environment
Generates Python scraper scripts and .github/workflows YAMLs to automate stat synchronization (stars, commits, tracking) into custom SVGs smoothly
Tool names combine multiple actions: 'fetch_github_trophies_live' both fetches stats AND renders SVG. Should split into separate tools for composability.
No error handling visible in code. Tools will fail silently or return raw exceptions. No recovery guidance for LLMs.