Model Context Protocol server for Rollbar
Nothing to run from here
Machinepulse is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
96/100
tool-list score
16
tools declared
remote
at its publisher
—
calls last 7d
What it does
Market data tools for the MCP ecosystem: server stats, events, search, leaderboards, package trends.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http machinepulse-mcp https://machinepulse.tech/mcp
# 2 — ask your agent for something these tools do
# get_mcp_ecosystem_summary, get_npm_trends, get_pypi_trends and 13 more
Machinepulse costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
MAAll 1 server
machinepulse1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http machinepulse-mcp https://machinepulse.tech/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
16 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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.
No parameter schema on file.
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 i
| Parameter | Type | Required | Notes |
|---|---|---|---|
| package | string | yes | — |
| days | integer | no | — |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| package | string | yes | — |
| days | integer | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| days | integer | no | — |
| limit | integer | no | — |
| offset | integer | no | — |
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_*_s
| Parameter | Type | Required | Notes |
|---|---|---|---|
| event_type | no | — | |
| since | no | — | |
| canonical_key | no | — | |
| limit | integer | no | — |
| offset | integer | no | — |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| canonical_key | string | yes | — |
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 o
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | — |
| limit | integer | no | — |
| offset | integer | no | — |
| archived | no | — | |
| has_repo | no | — | |
| category | no | — | |
| min_stars | no | — | |
| pushed_before | no | — |
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;
| Parameter | Type | Required | Notes |
|---|---|---|---|
| packages | array | yes | — |
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 do
| Parameter | Type | Required | Notes |
|---|---|---|---|
| as_of | no | — |
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 down
| Parameter | Type | Required | Notes |
|---|---|---|---|
| metric_id | string | no | — |
| window | no | — | |
| limit | integer | no | — |
| offset | integer | no | — |
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 reque
No parameter schema on file.
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.
No parameter schema on file.
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.
No parameter schema on file.
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.
No parameter schema on file.
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.
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| protocol | no | — | |
| limit | integer | no | — |
| offset | integer | no | — |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Machinepulse or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 96 / 100
Release 4.1.0 · scanned 28 Oct 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score96
Findings0 threat · 0 capability
Capabilityminimal
Coveragemanifest
Verificationnot in this report
Surface digestbae2cd56ab1586e650483d3e0a908572a99cc4a64a5abbece6c153bbd5a7d514
Score vectorthreat 100 → client 96
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| get_mcp_ecosystem_summary | no tags | |
| get_npm_trends | untrusted-input | untrusted-input: keyword "fetch" |
| get_pypi_trends | untrusted-input | untrusted-input: keyword "fetch" |
| get_github_trending | no tags | |
| get_ecosystem_events | no tags | |
| get_entity_profile | untrusted-input | untrusted-input: keyword "fetch" |
| search_mcp_servers | no tags | |
| get_package_comparison | untrusted-input | untrusted-input: keyword "download" |
| get_pulse | untrusted-input | untrusted-input: keyword "download" |
| get_leaderboard | untrusted-input | untrusted-input: keyword "download" |
| get_market_overview | untrusted-input | untrusted-input: keyword "fetch" |
| get_data_quality | no tags | |
| get_agents_summary | no tags | |
| get_llm_summary | no tags | |
| get_finance_summary | no tags | |
| get_protocols_timeline | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digestbae2cd56ab1586e6
Scanned2026-10-28
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 4.1.0.
4.1.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Machinepulse can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.