# Machinepulse (remote · machinepulse.tech)

Market data tools for the MCP ecosystem: server stats, events, search, leaderboards, package trends.

- Trust score: 72/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-04

## Components

- remote · `machinepulse.tech`: 72/100 (this document), [markdown](https://verifymcp.io/servers/tech-machinepulse-machinepulse/machinepulse.md), [page](https://verifymcp.io/servers/tech-machinepulse-machinepulse/machinepulse)

## Channel facts

- Endpoint: `https://machinepulse.tech/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `4.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-04.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 75/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1789 tokens (~111/item across 16 items; 16 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 22/100
  - Stability check failed: schema churn in the 14 days we've observed: 4 tool removals, 0 breaking changes, 0 auth/transport breaks, 4 additions.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 16 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Machinepulse MCP server?

Machinepulse is a hosted endpoint at https://machinepulse.tech/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http tech-machinepulse-machinepulse 'https://machinepulse.tech/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "tech-machinepulse-machinepulse": {
      "url": "https://machinepulse.tech/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "tech-machinepulse-machinepulse": {
      "type": "http",
      "url": "https://machinepulse.tech/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.tech-machinepulse-machinepulse]
url = "https://machinepulse.tech/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "tech-machinepulse-machinepulse": {
      "type": "remote",
      "url": "https://machinepulse.tech/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add tech-machinepulse-machinepulse --url 'https://machinepulse.tech/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  tech-machinepulse-machinepulse:
    url: "https://machinepulse.tech/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "tech-machinepulse-machinepulse": {
      "Transport": "http",
      "Url": "https://machinepulse.tech/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add tech-machinepulse-machinepulse -t streamable-http -u 'https://machinepulse.tech/mcp'
```

### Other

```json
{
  "mcpServers": {
    "tech-machinepulse-machinepulse": {
      "type": "http",
      "url": "https://machinepulse.tech/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 18 to 22.

### 2026-11-02 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 12 to 15.

### 2026-10-31 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 5 to 8.

### 2026-10-27 (score 69, 0)

- [security] Tool “search_mcp_servers” rewrote its description, which is the text the model reads

### 2026-10-22 (score 69, +7)

- [security regression] Stability: unverified → fail
- [security regression] Tool “data_quality” was removed
- [security regression] Tool “leaderboard” was removed
- [security regression] Tool “market_overview” was removed
- [security regression] Tool “pulse” was removed
- [security improvement] Authorization: unverified → partial
- [security] Tool “get_finance_summary” rewrote its description, which is the text the model reads
- [security] Tool “get_agents_summary” rewrote its description, which is the text the model reads
- [security] Tool “get_ecosystem_events” rewrote its description, which is the text the model reads
- [security] Tool “get_entity_profile” rewrote its description, which is the text the model reads
- [security] Tool “get_github_trending” rewrote its description, which is the text the model reads
- [security] Tool “get_llm_summary” rewrote its description, which is the text the model reads
- [security] Tool “get_mcp_ecosystem_summary” rewrote its description, which is the text the model reads
- [security] Tool “get_npm_trends” rewrote its description, which is the text the model reads
- [security] Tool “get_package_comparison” rewrote its description, which is the text the model reads
- [security] Tool “get_protocols_timeline” rewrote its description, which is the text the model reads
- [security] Tool “get_pypi_trends” rewrote its description, which is the text the model reads
- [security] Tool “search_mcp_servers” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: pass → fail
- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: 4.0.10 → 4.1.0
- [functional] New tool “get_data_quality”
- [functional] New tool “get_leaderboard”
- [functional] New tool “get_market_overview”
- [functional] New tool “get_pulse”

### 2026-10-21 (score 62)

First indexed and scored.

## MCP tools (16)

### `get_mcp_ecosystem_summary` (~76 tokens)

Get Mcp Ecosystem Summary

Summarize the MCP server ecosystem — unique servers, 7-day arrivals vs the previous 7 days, per-registry counts and new arrivals per category. Read-only aggregation of daily-collected observatory data; no side effects. Use when the user asks how big or how fast-growing the MCP ecosystem is.

### `get_npm_trends` (~122 tokens)

Get Npm Trends

Fetch daily download counts for an npm package — up to 100 days, with total, latest day and average over days that have data; days without collection are null with a note. Read-only aggregation of daily-collected observatory data; no side effects. Days inside the npm reporting delay are partial (shown, excluded from latest and average), never fake zeros. Use when the user asks how an npm package is growing; for side-by-side comparison use `get_package_comparison`.

Input parameters:

- `days` (integer)
- `package` (string, required)

### `get_pypi_trends` (~126 tokens)

Get Pypi Trends

Fetch daily download counts for a PyPI package — up to 100 days, with total, latest day and average over days that have data; days without collection are null with a note. Read-only aggregation of daily-collected observatory data; no side effects. Days inside the PyPI reporting delay are partial (shown, excluded from latest and average), never fake zeros. Use when the user asks how a PyPI package is growing; for side-by-side comparison use `get_package_comparison`.

Input parameters:

- `days` (integer)
- `package` (string, required)

### `get_github_trending` (~109 tokens)

Get Github Trending

List repositories seen on GitHub Trending — last N days (1-100), newest first, with rank and stars gained today; limit/offset page through the list. Read-only aggregation of daily-collected observatory data; no side effects. For a project ranking by measured change use `get_leaderboard` instead. Use when the user asks what is trending on GitHub.

Input parameters:

- `days` (integer)
- `limit` (integer)
- `offset` (integer)

### `get_ecosystem_events` (~145 tokens)

Get Ecosystem Events

List tracked ecosystem events — without filters, counts per event type over the last 7 days plus the latest event of each type and a plain-word legend; set event_type or canonical_key for the full feed (limit/offset page through it), set since=YYYY-MM-DD to widen the window. Read-only aggregation of daily-collected observatory data; no side effects. For counts rather than the feed use the `get_*_summary` tools. Use when the user asks what changed recently in the ecosystem.

Input parameters:

- `canonical_key`
- `event_type`
- `limit` (integer)
- `offset` (integer)
- `since`

### `get_entity_profile` (~138 tokens)

Get Entity Profile

Fetch the entity card for any tracked type (MCP server, agent, HF model, package) by canonical_key or natural name — all linked facts, categories, HF model license tiers, how to connect, recent events; field captions in fields_note. Name lookup matches exact aliases and canonical keys, not free-form text. Read-only aggregation of daily-collected observatory data; no side effects. Package download days may be missing (npm/PyPI reporting delay); missing days are null with notes, never fake zeros. Use when the user asks about a specific server, agent, model or package.

Input parameters:

- `canonical_key` (string, required)

### `search_mcp_servers` (~183 tokens)

Search Mcp Servers

Search MCP servers by canonical_key (former keys included, they stay as aliases), name or description — substring match, not fuzzy search, ordered by stars when available; optional filters archived, has_repo, category, min_stars, pushed_before run in one request; limit/offset page through the matches. Read-only aggregation of daily-collected observatory data; no side effects. Name/keyword lookup over MCP servers only; for the card of a known entity use `get_entity_profile`. Use when the user gives a name, a task word (PDF, payment) or a filter and wants keys and facts.

Input parameters:

- `archived`
- `category`
- `has_repo`
- `limit` (integer)
- `min_stars`
- `offset` (integer)
- `pushed_before`
- `query` (string, required)

### `get_package_comparison` (~128 tokens)

Get Package Comparison

Compare npm/PyPI download activity for up to 20 packages — last 30 days: total, latest day and average (a longer list is cut and says so). Read-only aggregation of daily-collected observatory data; no side effects. Package download days may be missing (npm/PyPI reporting delay); missing days are null with notes, never fake zeros. Use when the user wants to compare package popularity side by side; for a single package's history use `get_npm_trends` or `get_pypi_trends`.

Input parameters:

- `packages` (array, required)

### `get_pulse` (~108 tokens)

Get Pulse

Snapshot every observatory metric for one day — window values with formula, formula_plain, basis, and per-metric history depth (`metric_history_from`); insufficient history is a fact, never a fake zero. Read-only; daily collection, package download windows may lag. Use when the user asks for the current state of the AI agent ecosystem; for a narrative overview use `get_market_overview`, for one domain use the `get_*_summary` tools.

Input parameters:

- `as_of`

### `get_leaderboard` (~172 tokens)

Get Leaderboard

Rank tracked entities (servers, agents, models) by a project-level metric — project_momentum (score: middle of star/download/HF-derivative growth ranks) or trend_days (days on GitHub Trending) over the 7d window; limit/offset page through the full ranked list. Numbers and catalog facts only, no quality scores. Read-only aggregation of daily-collected observatory data; no side effects. Package download days may be missing (npm/PyPI reporting delay); missing days are null with notes, never fake zeros. Use when the user asks what is rising; for the daily GitHub Trending list use `get_github_trending`.

Input parameters:

- `limit` (integer)
- `metric_id` (string)
- `offset` (integer)
- `window`

### `get_market_overview` (~111 tokens)

Get Market Overview

Fetch the observatory front page in one call — MCP servers, A2A agents, HF models, x402 money, top-5 growth with one catalog line each, new arrivals per category and data coverage, a few headline numbers each. Read-only aggregation of daily-collected observatory data; no side effects; money figures carry their stated data lag. Use when the user wants the state of the whole market in a single request; for per-metric values with formulas use `get_pulse`.

### `get_data_quality` (~70 tokens)

Get Data Quality

Report collector health — coverage, per-source freshness and missed snapshot runs with reasons, separating recent misses from the whole recorded history; internal-only sources are excluded. Read-only aggregation of daily-collected observatory data; no side effects. Use when the user asks whether the observatory data is fresh or complete.

### `get_agents_summary` (~64 tokens)

Get Agents Summary

Summarize the A2A agent registry — snapshot total and verified counts plus new and left agents over the last 7 days. Read-only aggregation of daily-collected observatory data; no side effects. Use when the user asks how the AI agent registry is growing.

### `get_llm_summary` (~65 tokens)

Get Llm Summary

Summarize the Hugging Face model watchlist — model count, new arrivals, derivative net flow and the license tier mix. Read-only aggregation of daily-collected observatory data; no side effects. Use when the user asks about open LLMs and their licenses.

### `get_finance_summary` (~76 tokens)

Get Finance Summary

Summarize x402 agent-payment volume (DefiLlama) — latest stored day and the 7-day window split by chains with non-zero volume, with the data lag stated. Read-only aggregation of daily-collected observatory data; no side effects. Use when the user asks about agent payments or x402 volume.

### `get_protocols_timeline` (~96 tokens)

Get Protocols Timeline

List the protocol chronicle (MCP, A2A, AP2, x402) — releases and milestones, newest first, optionally filtered by protocol; limit/offset page through the entries. Read-only aggregation of daily-collected observatory data; no side effects. Use when the user asks when a protocol shipped something.

Input parameters:

- `limit` (integer)
- `offset` (integer)
- `protocol`

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/tech-machinepulse-machinepulse/machinepulse#diagnostics

## Score history

- 2026-11-04: 72
- 2026-11-03: 71
- 2026-11-02: 71
- 2026-11-01: 70
- 2026-10-31: 70
- 2026-10-30: 69
- 2026-10-29: 69
- 2026-10-28: 69
- 2026-10-27: 69
- 2026-10-26: 69
- 2026-10-25: 69
- 2026-10-24: 69
- 2026-10-23: 69
- 2026-10-22: 69
- 2026-10-21: 62

## Common questions

### What is the Machinepulse MCP server?

Machinepulse is an MCP server listed in the public MCP registry as tech.machinepulse/machinepulse. Market data tools for the MCP ecosystem: server stats, events, search, leaderboards, package trends. This page covers its hosted endpoint (https://machinepulse.tech/mcp).

### Is the Machinepulse MCP server safe to use?

Machinepulse scores 72 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Machinepulse MCP server expose?

Machinepulse exposes 16 tools: get_mcp_ecosystem_summary, get_npm_trends, get_pypi_trends, get_github_trending, get_ecosystem_events, and 11 more. Their descriptions and schemas cost roughly 1,789 tokens of context every time the server is loaded.

### Does the Machinepulse MCP server require authentication?

No. We connected to Machinepulse without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Machinepulse MCP server still maintained?

Machinepulse is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://machinepulse.tech/mcp
- Changelog RSS feed: https://verifymcp.io/servers/tech-machinepulse-machinepulse/machinepulse.xml
- Changelog JSON feed: https://verifymcp.io/servers/tech-machinepulse-machinepulse/machinepulse.json
- HTML version of this page: https://verifymcp.io/servers/tech-machinepulse-machinepulse/machinepulse