Astro-LLM
An MCP server that enables agents to evaluate LLMs daily through capability benchmarks and value alignment tests, providing tools to list models, get almanac, judge dilemmas, match user values, and score models.
README
大模型黄历 · Astro-LLM
The LLM almanac. One dashboard that tells you, every day, (1) which model is sharp today and whether you should spend or save your tokens, and (2) which model actually shares your values — all wrapped in an astrology / weather-report skin that's fun on the surface and a real personal eval harness underneath.
It looks like a fortune-telling almanac. It's actually a benchmark.
▶ Live demo: https://2-actual-hack.vercel.app · Repo: https://github.com/EthanPany/astro-llm

Five completely different themed layouts (almanac · oracle · court · ink · aurora), a step-by-step value-match quiz, and a live model-fortune board. Full walkthrough:
docs/showcase.mp4.
Why
Coding plans (Claude Code, Codex, …) feel slightly different day to day — sometimes the same model thinks longer, sometimes it's sharper, sometimes worse. And which model "gets" your taste is deeply personal. Astro-LLM turns both into a daily reading:
| Organ | Astrology name | What it really measures |
|---|---|---|
| Capability probe | 运势 fortune | Is the model sharp today? — 18 deterministic, auto-graded tasks → an IQ, latency, cost, refusal rate, trend. |
| Value matcher | 缘分 affinity | Does it judge like you? — a bank of subjective dilemmas; we measure agreement (footrule + verdict match). |
| MCP server | — | How an agent runs the test on itself. |
| Harmonize loop | 调和 harmony | Can we nudge a model toward you? — inject your taste, re-test on held-out dilemmas. |
The "luck" is the skin; the numbers underneath are real. See the honesty note at the bottom of the dashboard.
Quickstart (local)
Requirements: Python 3.11+, uv, Node 20+.
cp .env.example .env # paste your API keys (all optional — see below)
make install # backend venv (uv) + frontend deps
make seed # probe live models, write committed seed JSON (optional)
make dev-backend # API on http://localhost:8000 (terminal 1)
make dev-frontend # UI on http://localhost:5173 (terminal 2)
Open http://localhost:5173.
No keys? It still works. The repo ships committed seed data, so the dashboard,
verdict grid and value-match all render offline. Keys unlock live re-probes
(↻ 实时巡检), the live custom-dilemma panel, and the harmonize loop.
Providers
ANTHROPIC_API_KEY, OPENAI_API_KEY, DEEPSEEK_API_KEY are wired and verified.
GEMINI_API_KEY / QWEN_API_KEY are implemented; without them those models show
clearly-labelled simulated data. Adding a key flips them to live on the next make seed.
Deploy (one command)
make up # docker compose: builds the frontend, serves SPA + API on :8000
# or:
docker build -t astro-llm . && docker run -p 8000:8000 --env-file .env astro-llm
In production FastAPI serves the built SPA and the API from the same origin, so there's nothing else to configure. The image bakes in the seed data, so it renders even with zero keys.
Architecture
backend/ FastAPI + httpx + pydantic + SQLite (uv-managed)
app/
providers/ one adapter per provider (OpenAI/Anthropic/DeepSeek/Gemini/Qwen)
benchmarks/ dilemma bank, capability tasks, judge + capability runners,
matching (footrule + agreement), scoring (IQ + suggestion)
astrology/ deterministic zodiac / numerology / fortune / compatibility
loop/ harmonize (train/test guardrail)
storage/ SQLite DAL + seed generator
service.py assembly: runs + astrology -> AlmanacCards + headline
api/routes.py REST API | mcp_server.py MCP tools | scheduler.py
frontend/ React + Vite + TypeScript, handwritten CSS, GSAP, hand-drawn SVG charts
Full data contracts: ARCHITECTURE.md.
API
GET /api/dashboard · GET /api/models · GET /api/dilemmas ·
POST /api/match · POST /api/harmonize · POST /api/judge · GET /api/health
MCP
make mcp # python -m app.mcp_server (stdio)
Tools: list_models, get_almanac, judge_dilemma, match_me,
score_model_against_user. Point any MCP client (e.g. Claude Desktop) at it and an
agent can score itself against the benchmark.
Hourly almanac
Set ENABLE_SCHEDULER=true to probe available models on an interval (PROBE_INTERVAL_MINUTES),
persisting real runs to SQLite so the trend becomes measured data over time.
Tests
make test # 34 tests: astrology, matching, scoring, graders, judge parsing,
# harmonize, API (offline via TestClient + monkeypatched seed)
Design
Handwritten CSS only — no Tailwind, no component library, no chart library. Charts are hand-drawn SVG. Type: Fraunces (display) + Space Grotesk (UI) + Space Mono (numbers). GSAP drives entrance reveals, number count-ups, and chart draw-on.
Honesty note
The capability score is a real stopwatch + autograder. The value-match measures how a model was tuned to present itself, not a hidden soul. The harmonize loop is scored on held-out dilemmas the model never saw during tuning — the guardrail that keeps "alignment" from collapsing into a flattery machine. The astrology is for fun; we say so.
⚠ Rotate any API keys that were shared in plaintext before making this repo public.
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。
mcp-server-qdrant
这个仓库展示了如何为向量搜索引擎 Qdrant 创建一个 MCP (Managed Control Plane) 服务器的示例。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。