Machinepulse is an MCP server published by tech.machinepulse, hosted at machinepulse.tech. When last checked on 2026-11-21 it was working: it answers and lists its tools. It declares 16 tools, including get_mcp_ecosystem_summary, get_npm_trends, get_pypi_trends, get_github_trending, get_ecosystem_events.
Market data tools for the MCP ecosystem: server stats, events, search, leaderboards, package trends.
Nothing else in the archive shares these values.
Squares are this server's values; dots are other servers sharing them. A shared address or publisher is a lead, not proof of a common operator.
Inferred from the host name and headers: what a server runs on, not who runs it.
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 parameters.
{
"name": "get_mcp_ecosystem_summary",
"title": "Get Mcp Ecosystem Summary",
"description": "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.",
"inputSchema": {
"type": "object",
"properties": {},
"additionalProperties": false
},
"outputSchema": {
"type": "object",
"additionalProperties": true
},
"annotations": {
"readOnlyHint": true,
"idempotentHint": true,
"destructiveHint": false
}
}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`.
| Parameter | Type | Description |
|---|---|---|
| days | integer | |
| package * | string |
{
"name": "get_npm_trends",
"title": "Get Npm Trends",
"description": "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`.",
"inputSchema": {
"type": "object",
"required": [
"package"
],
"properties": {
"days": {
"type": "integer",
"default": 30
},
"package": {
"type": "string"
}
},
"additionalProperties": false
},
"outputSchema": {
"type": "object",
"additionalProperties": true
},
"annotations": {
"readOnlyHint": true,
"idempotentHint": true,
"destructiveHint": false
}
}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`.
| Parameter | Type | Description |
|---|---|---|
| days | integer | |
| package * | string |
{
"name": "get_pypi_trends",
"title": "Get Pypi Trends",
"description": "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`.",
"inputSchema": {
"type": "object",
"required": [
"package"
],
"properties": {
"days": {
"type": "integer",
"default": 30
},
"package": {
"type": "string"
}
},
"additionalProperties": false
},
"outputSchema": {
"type": "object",
"additionalProperties": true
},
"annotations": {
"readOnlyHint": true,
"idempotentHint": true,
"destructiveHint": false
}
}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 | Description |
|---|---|---|
| days | integer | |
| limit | integer | |
| offset | integer |
{
"name": "get_github_trending",
"title": "Get Github Trending",
"description": "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.",
"inputSchema": {
"type": "object",
"properties": {
"days": {
"type": "integer",
"default": 7
},
"limit": {
"type": "integer",
"default": 100
},
"offset": {
"type": "integer",
"default": 0
}
},
"additionalProperties": false
},
"outputSchema": {
"type": "object",
"additionalProperties": true
},
"annotations": {
"readOnlyHint": true,
"idempotentHint": true,
"destructiveHint": false
}
}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.
| Parameter | Type | Description |
|---|---|---|
| limit | integer | |
| since | any | |
| offset | integer | |
| event_type | any | |
| canonical_key | any |
{
"name": "get_ecosystem_events",
"title": "Get Ecosystem Events",
"description": "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.",
"inputSchema": {
"type": "object",
"properties": {
"limit": {
"type": "integer",
"default": 100
},
"since": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"default": null
},
"offset": {
"type": "integer",
"default": 0
},
"event_type": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"default": null
},
"canonical_key": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"default": null
}
},
"additionalProperties": false
},
"outputSchema": {
"type": "object",
"additionalProperties": true
},
"annotations": {
"readOnlyHint": true,
"idempotentHint": true,
"destructiveHint": false
}
}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.
| Parameter | Type | Description |
|---|---|---|
| canonical_key * | string |
{
"name": "get_entity_profile",
"title": "Get Entity Profile",
"description": "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.",
"inputSchema": {
"type": "object",
"required": [
"canonical_key"
],
"properties": {
"canonical_key": {
"type": "string"
}
},
"additionalProperties": false
},
"outputSchema": {
"type": "object",
"additionalProperties": true
},
"annotations": {
"readOnlyHint": true,
"idempotentHint": true,
"destructiveHint": false
}
}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.
| Parameter | Type | Description |
|---|---|---|
| limit | integer | |
| query * | string | |
| offset | integer | |
| archived | any | |
| category | any | |
| has_repo | any | |
| min_stars | any | |
| pushed_before | any |
{
"name": "search_mcp_servers",
"title": "Search Mcp Servers",
"description": "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.",
"inputSchema": {
"type": "object",
"required": [
"query"
],
"properties": {
"limit": {
"type": "integer",
"default": 100
},
"query": {
"type": "string"
},
"offset": {
"type": "integer",
"default": 0
},
"archived": {
"anyOf": [
{
"type": "boolean"
},
{
"type": "null"
}
],
"default": null
},
"category": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"default": null
},
"has_repo": {
"anyOf": [
{
"type": "boolean"
},
{
"type": "null"
}
],
"default": null
},
"min_stars": {
"anyOf": [
{
"type": "integer"
},
{
"type": "null"
}
],
"default": null
},
"pushed_before": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"default": null
}
},
"additionalProperties": false
},
"outputSchema": {
"type": "object",
"additionalProperties": true
},
"annotations": {
"readOnlyHint": true,
"idempotentHint": true,
"destructiveHint": false
}
}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`.
| Parameter | Type | Description |
|---|---|---|
| packages * | array |
{
"name": "get_package_comparison",
"title": "Get Package Comparison",
"description": "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`.",
"inputSchema": {
"type": "object",
"required": [
"packages"
],
"properties": {
"packages": {
"type": "array",
"items": {
"type": "string"
}
}
},
"additionalProperties": false
},
"outputSchema": {
"type": "object",
"additionalProperties": true
},
"annotations": {
"readOnlyHint": true,
"idempotentHint": true,
"destructiveHint": false
}
}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.
| Parameter | Type | Description |
|---|---|---|
| as_of | any |
{
"name": "get_pulse",
"title": "Get Pulse",
"description": "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.",
"inputSchema": {
"type": "object",
"properties": {
"as_of": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"default": null
}
},
"additionalProperties": false
},
"outputSchema": {
"type": "object",
"additionalProperties": true
},
"annotations": {
"readOnlyHint": true,
"idempotentHint": true,
"destructiveHint": false
}
}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`.
| Parameter | Type | Description |
|---|---|---|
| limit | integer | |
| offset | integer | |
| window | any | |
| metric_id | string |
{
"name": "get_leaderboard",
"title": "Get Leaderboard",
"description": "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`.",
"inputSchema": {
"type": "object",
"properties": {
"limit": {
"type": "integer",
"default": 20
},
"offset": {
"type": "integer",
"default": 0
},
"window": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"default": null
},
"metric_id": {
"type": "string",
"default": "project_momentum"
}
},
"additionalProperties": false
},
"outputSchema": {
"type": "object",
"additionalProperties": true
},
"annotations": {
"readOnlyHint": true,
"idempotentHint": true,
"destructiveHint": false
}
}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`.
No parameters.
{
"name": "get_market_overview",
"title": "Get Market Overview",
"description": "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`.",
"inputSchema": {
"type": "object",
"properties": {},
"additionalProperties": false
},
"outputSchema": {
"type": "object",
"additionalProperties": true
},
"annotations": {
"readOnlyHint": true,
"idempotentHint": true,
"destructiveHint": false
}
}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 parameters.
{
"name": "get_data_quality",
"title": "Get Data Quality",
"description": "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.",
"inputSchema": {
"type": "object",
"properties": {},
"additionalProperties": false
},
"outputSchema": {
"type": "object",
"additionalProperties": true
},
"annotations": {
"readOnlyHint": true,
"idempotentHint": true,
"destructiveHint": false
}
}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 parameters.
{
"name": "get_agents_summary",
"title": "Get Agents Summary",
"description": "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.",
"inputSchema": {
"type": "object",
"properties": {},
"additionalProperties": false
},
"outputSchema": {
"type": "object",
"additionalProperties": true
},
"annotations": {
"readOnlyHint": true,
"idempotentHint": true,
"destructiveHint": false
}
}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 parameters.
{
"name": "get_llm_summary",
"title": "Get Llm Summary",
"description": "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.",
"inputSchema": {
"type": "object",
"properties": {},
"additionalProperties": false
},
"outputSchema": {
"type": "object",
"additionalProperties": true
},
"annotations": {
"readOnlyHint": true,
"idempotentHint": true,
"destructiveHint": false
}
}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 parameters.
{
"name": "get_finance_summary",
"title": "Get Finance Summary",
"description": "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.",
"inputSchema": {
"type": "object",
"properties": {},
"additionalProperties": false
},
"outputSchema": {
"type": "object",
"additionalProperties": true
},
"annotations": {
"readOnlyHint": true,
"idempotentHint": true,
"destructiveHint": false
}
}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 | Description |
|---|---|---|
| limit | integer | |
| offset | integer | |
| protocol | any |
{
"name": "get_protocols_timeline",
"title": "Get Protocols Timeline",
"description": "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.",
"inputSchema": {
"type": "object",
"properties": {
"limit": {
"type": "integer",
"default": 20
},
"offset": {
"type": "integer",
"default": 0
},
"protocol": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"default": null
}
},
"additionalProperties": false
},
"outputSchema": {
"type": "object",
"additionalProperties": true
},
"annotations": {
"readOnlyHint": true,
"idempotentHint": true,
"destructiveHint": false
}
}Names, descriptions and schemas were written by the server and are shown as data.
Pattern matches on what the server declares. They show what it says it can do, not what it does.
None yet. Changes appear after a server's second daily check.