mcp-pulse

Aggregate MCP ecosystem data from GitHub and npm into a weekly momentum score and briefing.

Updated Jun 2, 2026

Search Tags:#npm #github #mcp #momentum #ecosystem #model-context-protocol #server-tracking

Ready to run

npx skills add https://github.com/Atrium-Hermes/atrium-lighthouse --skill mcp-pulse

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: mcp-pulse
Source: https://github.com/Atrium-Hermes/atrium-lighthouse/tree/main/skills/mcp-pulse
Command: npx skills add https://github.com/Atrium-Hermes/atrium-lighthouse --skill mcp-pulse

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured weekly digest and momentum assessment for the Model Context Protocol (MCP) ecosystem, helping teams monitor server adoption, tooling signals, and protocol evolution.

Core Features & Use Cases

Ecosystem momentum tracking: aggregate server deployments, repo activity, and download signals to gauge progress toward MCP-as-default tool-call rails.
Signal synthesis: synthesize notable developments (new servers, ecosystem stats, and notable integrations) into a concise momentum score and narrative.
Operational monitoring: maintain a seed memory around MCP context and generate weekly updates and notifications for stakeholders.

Quick Start

Provide a concise weekly MCP momentum briefing based on the latest ecosystem signals and craft a short thesis sentence about whether MCP is advancing, holding, stalling, or reversing.

Frequently Asked Questions about mcp-pulse

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I track Model Context Protocol ecosystem momentum and server adoption?▼

Track Model Context Protocol ecosystem momentum by aggregating GitHub repository activity, npm download signals, and server deployments into a weekly momentum score. The Skill synthesizes these signals to measure adoption velocity and generate a concise narrative briefing.

What is the best way to monitor weekly MCP server tooling signals and ecosystem news?▼

Monitor weekly MCP server tooling signals by fetching current context from memory, npm downloads, and GitHub repository activity. This generates a structured briefing with a momentum score and a one-line thesis on whether the ecosystem is advancing, holding, stalling, or reversing.

How does MCP momentum scoring work for tracking protocol adoption velocity?▼

MCP momentum scoring works by aggregating server adoption signals, repository activity, and npm download data into a measured adoption velocity. It applies weekly tracking across MCP servers and notable ecosystem news to produce a structured momentum assessment.

Can I use this to generate a weekly briefing on MCP-as-default tool-call rails progress?▼

Yes, you can generate a weekly briefing on MCP-as-default tool-call rails progress by synthesizing server deployments, ecosystem stats, and tooling signals. The output includes a concise momentum score, narrative, and a short thesis sentence about ecosystem direction.

Do I need prior context loaded to measure MCP adoption velocity accurately?▼

You need seed memory loaded around MCP context to measure adoption velocity accurately. The Skill loads this context and fetches MCP-relevant data from GitHub and npm to produce the structured weekly briefing and momentum assessment.

What are the limitations of tracking MCP momentum using npm downloads and GitHub activity?▼

Tracking MCP momentum using npm downloads and GitHub activity captures quantitative adoption signals but may miss qualitative protocol integrations or private server deployments. The momentum score synthesizes visible repository and download signals into a concise narrative without accessing closed ecosystem data.