convez.ai
MCP ServerDevOps & InfraestruturaIntermediário
rogerchappel

MCP ChangeFeed

rogerchappel/mcpchangefeed

Rastreador de mudanças e diretório estático para servidores MCP

Ver no GitHub
InicialPluginScore · de 0 a 100

MCP ChangeFeed rastreia mudanças em servidores Model Context Protocol, normaliza metadados e publica um diretório estático com CLI integrada. Detecta atualizações significativas como novos servidores, repositórios renomeados, comandos de instalação alterados e avisos de documentação obsoleta.

Instalação

$npx convez-ai rogerchappel/mcpchangefeed

1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.

Métricas

Estrelas
2
Forks
1
Acompanhando
0
Saúde
71%
Último commit
há 1 semana
Versão
—
Issues abertas
4
Contribuidores
2

Casos de uso

  • Monitorar atualizações e mudanças em servidores MCP públicos
  • Buscar e comparar servidores MCP via CLI ou site estático
  • Gerar leaderboard de ferramentas mais mantidas e ativas
  • Detectar descontinuação ou renomeação de pacotes MCP

Veredito

Ferramenta bem pensada para o ecossistema MCP: resolve fragmentação de descoberta focando em mudanças, não em listagens estáticas. CLI + site estático + GitHub Actions automation tornam viável para mantencão contínua com baixa dependência de APIs externas.

README

A tradução para o português deste README ainda está na fila.

mcpchangefeed

Public changefeed, CLI, and static site for MCP servers and agent tools.

mcpchangefeed tracks public Model Context Protocol servers from registry-style data, normalizes metadata, detects meaningful changes, scores freshness/usefulness signals, and publishes both a CLI and a crawlable static site.

Why

MCP discovery is fragmented, but directory space is already crowded. The useful angle is knowing what changed:

  • new servers
  • removed servers
  • renamed packages and repositories
  • changed install commands
  • changed categories and tags
  • stale or missing documentation warnings
  • freshness views for maintained and fast-moving tools

CLI

The CLI makes the repo useful even before SEO compounds: developers can query the same normalized dataset locally, compare snapshots in CI, and script checks around MCP server freshness.

pnpm install
pnpm run build:cli
node dist-cli/cli.js top --input fixtures/servers.json
node dist-cli/cli.js search filesystem --input fixtures/servers.json
node dist-cli/cli.js diff --before fixtures/servers-before.json --after fixtures/servers.json

Planned package usage:

npx mcpchangefeed top
mcpfeed search github
mcpfeed diff --before old.json --after new.json

Data Sources

Initial source priority:

  1. Official MCP registry snapshots.
  2. Known reference/community server lists.
  3. npm and PyPI packages with MCP naming and metadata.
  4. Light GitHub enrichment from known repository URLs, cached and rate-limited.

The GitHub API should be enrichment, not the main dependency.

GitHub Action Commit Engine

The scheduled workflow refreshes public data and commits only meaningful changes:

  • latest normalized snapshot
  • dated history snapshot
  • changed leaderboard output
  • changed static pages
  • daily changelog entry

No timestamp-only commits.

The workflow is intentionally GitHub-token-light. It starts with the official MCP registry endpoint and can add npm/PyPI enrichment without depending on high-volume GitHub API calls.

Static Site

Build the public SEO surface:

pnpm run build:site

Output goes to site/ and can be published by GitHub Pages or Cloudflare Pages.

The first generated site includes:

  • homepage leaderboard
  • per-server pages
  • category landing pages
  • sitemap and robots files
  • JSON export for client-side/search consumers

Verification

pnpm test
Ver o original no GitHub

Bom para

Relacionados