Skip to main content
Glama

glama-status-mcp

ARCHIVED 2026-10-06 — merged into scraper-mcp. This repo was the precursor Glama tracker; its UX lives on as scraper_advice (per-repo fix lists), scraper_fleet (staleness / worst_tools / deltas), and the Phase 4 digest in scraper-mcp (ports 10998/10999). Its scraper targets Glama's pre-2026-07 layout and returns no data on live pages — do not restart this server. Ports 11072/11073 stay reserved until dashboard links migrate (see WEBAPP_PORTS.md). Uncommitted tree dirt predates the archive and is intentionally untouched.

Daily-refreshed Glama score tracker for the sandraschi fleet. Scrapes per-tool TDQS grades from glama.ai, stores in SQLite, surfaces via MCP tools and a web dashboard. Tracks deltas between snapshots, generates daily reports, and flags stale repos needing rescan.

Quickstart

just install
just web          # HTTP backend on :11072
just web-frontend # Vite dev on :11073
just web-dev      # Full stack
just refresh      # Manual scrape + snapshot

Related MCP server: Zenith MCP Server

MCP Tools

Tool

Purpose

glama_status

Portmanteau: list, get, worst_tools, refresh, history, staleness, report, deltas

glama_scores_summary

Compact grade distribution and per-repo stats

glama_daily_report

Full markdown report with deltas, worst tools, stale repos

Web Dashboard

Route

Description

/

Sortable fleet score table

/api/repos

All repos with per-tool breakdowns

/api/repos/{name}

Single repo tool breakdown

/api/report

Full daily report JSON

/api/deltas

Score changes since last snapshot

/api/refresh (POST)

Trigger rescrape + snapshot

/api/worst-tools

Lowest-scoring tools fleet-wide

How it works

  1. Scraper fetches glama.ai/mcp/servers/{author}/{repo}/score pages

  2. Parser extracts per-tool grades, 6 TDQS dimension scores, coherence, and maintenance data

  3. SQLite stores current scores + snapshot history for delta tracking

  4. Daily refresh via Scheduled Task or just refresh creates a new snapshot

  5. Delta engine compares latest two snapshots to show changes

Scored repos (10 of 35 registered on Glama)

Repo

Grade

Score

Tools

blender-mcp

C

2.70

67

windows-operations-mcp

B

3.00

17

virtualization-mcp

B

3.06

9

worldlabs-mcp

B

3.38

20

robotics-mcp

A

3.58

8

bumi-mcp

A

3.64

2

xkcd-mcp

A

3.67

6

cursor-mcp

A

3.80

6

steam-mcp

A

3.81

14

email-mcp

A

3.82

10

25 more registered on Glama but not yet analyzed (page exists, no tools).

Scoring (Glama TDQS)

Dimension

Weight

Description

Purpose Clarity

25%

First sentence states what the tool does

Usage Guidelines

20%

When to / not to call, preconditions

Behavioral Transparency

20%

Returns, side effects, error conditions

Parameter Semantics

15%

Every param: type, values, what it affects

Conciseness & Structure

10%

Not a wall of text, not a one-liner

Contextual Completeness

10%

Enough context to use without reading source

Server-level = 60% mean + 40% minimum - one bad tool pulls the whole score down.

Ports

  • Backend (FastAPI + MCP HTTP): 11072

  • Frontend (Vite dev): 11073

Available Tools

7 tools
glama_agentic_analyzeB

Analyze Glama scores with LLM sampling and generate fixable todos.

Uses the connected LLM (via MCP ctx.sample) to intelligently analyze a repo's tool docstring scores and produce actionable fix tasks.

Inputs: repo_name. Returns: object

glama_daily_reportA

Generate daily fleet health report.

Includes grade distribution, recent changes, worst tools, stale repos. When to use: once daily for comprehensive fleet Glama score overview. When NOT to use: for single repo details use glama_status(get). Preconditions: at least one refresh must have been run.

Inputs: format. Returns: object

glama_generate_reportsA

Generate markdown analysis reports for repos.

Creates per-repo fix-todo reports in the reports/ directory, suitable for ingestion by IDE LLMs. If repo_name is empty, generates reports for all scored repos.

Inputs: repo_name. Returns: object

glama_scores_summaryB

Return compact fleet-wide score summary.

Grades per repo and count per grade bucket. Returns: success, grade_distribution, repos, count, message.

Inputs: no named parameters. Returns: object

glama_statusA

Fleet-wide Glama score tracker -- query per-tool TDQS grades.

Identifies worst-scoring tools, trigger rescans. When to use: check fleet repo Glama scores, find tools needing docstring fixes, or trigger a refresh. When NOT to use: for code diagnostics use the repo's own tools; for Glama submission/review use glama.ai directly. Preconditions: repo must have been submitted to Glama and scored.

Operations:

  • list: All repos, worst-first.

  • get: Per-tool breakdown for one repo (repo_name required).

  • worst_tools: Lowest-scoring tools fleet-wide.

  • refresh: Rescrape all fleet repos + snapshot.

  • history: Recent refresh log entries.

  • staleness: Repos >7d since last scrape.

  • report: Full daily status report.

  • deltas: Score changes between last two snapshots.

  • add_repo: Add a repo to track (name, optional author/slug).

  • remove_repo: Stop tracking a repo.

  • reload_config: Reload fleet-repos.json config file.

Inputs: operation (required), limit, repo_name. Returns: object

show_glama_repo_cardA

Show per-repo Glama score breakdown as a rich Prefab card.

Displays overall grade, TDQS scores, coherence dimensions, maintenance grade, and per-tool scores for a single repo.

Inputs: repo_name (required).

show_glama_status_cardA

Show fleet Glama score overview as a rich Prefab card.

Displays grade distribution, per-repo scores (worst first), worst tools across the fleet, and stale repos in a structured dashboard card suitable for in-chat viewing.

Return Format

ToolResult with PrefabApp card and plain-text fallback.

Examples

await show_glama_status_card()

Inputs: no named parameters.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.9/5.0

    Scored across 7 tools

    Disambiguation3/5

    Some overlap exists between dedicated report tools (glama_daily_report, glama_scores_summary) and the glama_status tool which has its own 'report' and 'list' operations. Descriptions try to clarify, but an agent might struggle to choose the correct tool for a given task.

    Naming Consistency5/5

    All tools follow a consistent 'glama_<descriptive_name>' pattern in snake_case, with clear verb_noun or descriptive names. There is no mixing of conventions or confusing styles.

    Tool Count5/5

    With 7 tools, the set is well-scoped for monitoring and analyzing Glama scores. Each tool has a distinct purpose, and the count feels neither too few nor too many.

    Completeness4/5

    The set covers analysis, reporting, summary, detailed queries, and rich cards. Missing a direct submission tool is acceptable as it's outside the server's scope. Minor gaps like lacking a bulk update feature are not critical.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      B
      quality
      D
      maintenance
      Agentic data quality MCP server — runs structured validation rules against warehouses (DuckDB, BigQuery, Athena, Databricks, Postgres), diagnoses failures with LLM root cause analysis, and proposes SQL remediations. Full audit trail of every AI decision.
      6
      15 PyPI
      5
      Apache 2.0
    • F
      license
      Not graded
      quality
      D
      maintenance
      A custom MCP server exposing database, ticketing, and external-API tools to both Claude Desktop and a self-built autonomous agent powered by Groq's free-tier LLaMA 3.3.
      -