Machinepulse
REMOTE · MACHINEPULSE.TECH
Market data tools for the MCP ecosystem: server stats, events, search, leaderboards, package trends.
Available components
Last scanned (22 hours ago)
Scores higher than 58% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Search and Retrieval
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. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability75
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management22
- Stability check failed: schema churn in the 14 days we've observed: 4 tool removals, 0 breaking changes, 0 auth/transport breaks, 4 additions. See how to fix → Fail
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 16 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 18 to 22.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 12 to 15.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 5 to 8.
- 27 Oct 26 0
- Tool “search_mcp_servers” rewrote its description, which is the text the model reads security
- 22 Oct 26 +7
- Stability: unverified → fail ▼ security
- Tool “data_quality” was removed ▼ security
- Tool “leaderboard” was removed ▼ security
- Tool “market_overview” was removed ▼ security
- Tool “pulse” was removed ▼ security
- 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 security
- Schema quality: pass → fail ▼ functional
- 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” functional
- 21 Oct 26 62
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Probed https://machinepulse.tech/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=machinepulse.tech | CN=YE2,O=Let's Encrypt,C=US | 3 Oct 2026 | 1 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 572d643f50797c8df8af122363089d9d7b2 |
| SANs: machinepulse.tech | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of machinepulse.tech. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| tech. | present | 2185 | 13 | Verified |
| machinepulse.tech. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://machinepulse.tech/mcp | Verified | 200 | |
| http (plaintext) | http://machinepulse.tech/mcp | HTTPS enforced | 308 | https://machinepulse.tech/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_agents_summary Get Agents Summary ~64
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.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
get_data_quality Get Data Quality ~70
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.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
get_ecosystem_events Get Ecosystem Events ~145
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.
| Name | Type | Req | Description |
|---|---|---|---|
| canonical_key | – | – | – |
| event_type | – | – | – |
| limit | integer | – | – |
| offset | integer | – | – |
| since | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_entity_profile Get Entity Profile ~138
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.
| Name | Type | Req | Description |
|---|---|---|---|
| canonical_key | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_finance_summary Get Finance Summary ~76
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.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
get_github_trending Get Github Trending ~109
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.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
| limit | integer | – | – |
| offset | integer | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_leaderboard Get Leaderboard ~172
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`.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| metric_id | string | – | – |
| offset | integer | – | – |
| window | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_llm_summary Get Llm Summary ~65
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.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
get_market_overview Get Market Overview ~111
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`.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
get_mcp_ecosystem_summary Get Mcp Ecosystem Summary ~76
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.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
get_npm_trends Get Npm Trends ~122
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`.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
| package | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_package_comparison Get Package Comparison ~128
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`.
| Name | Type | Req | Description |
|---|---|---|---|
| packages | array | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_protocols_timeline Get Protocols Timeline ~96
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| offset | integer | – | – |
| protocol | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_pulse Get Pulse ~108
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.
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_pypi_trends Get Pypi Trends ~126
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`.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
| package | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
search_mcp_servers Search Mcp Servers ~183
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.
| Name | Type | Req | Description |
|---|---|---|---|
| archived | – | – | – |
| category | – | – | – |
| has_repo | – | – | – |
| limit | integer | – | – |
| min_stars | – | – | – |
| offset | integer | – | – |
| pushed_before | – | – | – |
| query | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
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.
remote · machinepulse.tech
claude mcp add --transport http tech-machinepulse-machinepulse 'https://machinepulse.tech/mcp'
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.