Search arXiv papers, download full text, semantic search, citation graphs, and alerts via MCP.
Nothing to run from here
DataPulse MY 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.
19
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Read-only discovery for 440 Malaysian public datasets with freshness, licence, and provenance.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http datapulse-my-mcp https://mcp.data-pulse.my/mcp
# 2 — ask your agent for something these tools do
# search_datasets, get_dataset, get_data_passport and 16 more
DataPulse MY costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
R3All 2 servers
r3dz4r2 servers
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 datapulse-my-mcp https://mcp.data-pulse.my/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
19 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.
Use for discovery only: find DataPulse's 440 Malaysian public datasets by topic, source, or licence—for example, 'Malaysian public data inflation', licence and attribution, or a government dataset source. Returns ranked matches with id, title, source, licence, published status, and score. This is not trust verification: a status is published pipeline context, not proof that a dataset is current or
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Topic or task phrasing used to rank discovery candidates, e.g. 'Malaysian public data inflation'; use a returned id with get_dataset. |
| licence | no | Optional exact licence name or supported alias applied before ranking, e.g. 'CC BY 4.0'; omit it to search every licence. | |
| source | no | Optional publisher/source substring filter applied before ranking, e.g. 'OpenDOSM'; omit it to search every source. | |
| limit | integer | no | Maximum highest-ranked discovery matches to return, e.g. 10; omitted defaults to 10 and does not change ranking. |
Return full detail for one dataset id, including its latest health status and last-verified timestamp, content_freshness_date, and freshness_signal_source (last_modified, content_parse, or none). Use to fetch the provenance/citation metadata for a dataset found via search_datasets and distinguish unknown-freshness from proven stale data. Use it for one dataset's current published detail; do not us
| Parameter | Type | Required | Notes |
|---|---|---|---|
| dataset_id | string | yes | Stable dataset slug returned by search_datasets, e.g. 'dosm_cpi_state'; this tool requires the slug, not a display name. |
Return one bounded, machine-readable Dataset Passport v1 for a canonical dataset ID. It reads the published Passport artifact only; it does not fetch an upstream source or create evidence. The Passport describes observed metadata and evidence availability, not semantic truth, completeness, certification, legal permission, safety, or AI admission. Use it for the bounded Passport artifact; do not us
| Parameter | Type | Required | Notes |
|---|---|---|---|
| dataset_id | string | yes | Stable dataset slug returned by search_datasets, e.g. 'fuelprice'; this tool requires the slug, not a display name. |
Return datasets whose status is aging, stale, or degraded, plus datasets missing from the latest health snapshot. Use when an agent needs to know which data has a freshness or schema-validity risk. Use it to enumerate freshness or schema-risk candidates; do not use it for anomalies, trends, reliability, or drift—use find_anomalies, find_deteriorating, find_unreliable, or find_schema_drift instead.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| max_age_hours | integer | no | Maximum published-snapshot age before otherwise healthy rows are included, e.g. 72; omit it to use 24 hours. |
Return datasets flagged by the latest published anomaly detection (anomalies), ranked by how far the observed update interval exceeds its threshold. Optionally require a minimum publish-reliability grade; includes pipeline-computed anomaly and reliability evidence so agents do not recompute it. Use it for unusual update intervals; do not use it for worsening freshness, recovery, reliability grades
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | Maximum highest-ranked anomalies to return, e.g. 50; omit it to use 50 without changing the ranking. |
| mode | no | Optional exact published detection mode filter, e.g. 'rolling_14d' or 'cadence_fallback'; omit it to include every mode. | |
| min_reliability | no | Optional inclusive published reliability floor, e.g. 'C' keeps A, B, and C; omit it to retain rows regardless of grade. |
Return datasets whose published freshness trend is deteriorating, ranked by staleness slope. Optionally require a minimum historical anomaly rate; includes pipeline-computed trend and reliability evidence so agents do not recompute it. Use it for worsening freshness trends; do not use it for anomalies, recovery, reliability grades, or structural drift—use find_anomalies, find_recovering, find_unre
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | Maximum highest-ranked deteriorating datasets to return, e.g. 50; omit it to use 50 without changing ranking. |
| min_anomaly_rate | no | Optional inclusive anomaly-rate filter on published history, e.g. 25.0; omit it to retain every deteriorating row. |
Return datasets whose published freshness trend is recovering, with the fastest staleness reductions first. Includes pipeline-computed trend and publish-reliability evidence. Use it for improving freshness trends; do not use it for deterioration, anomalies, reliability grades, or structural drift—use find_deteriorating, find_anomalies, find_unreliable, or find_schema_drift instead. It reads precom
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | Maximum fastest-recovering datasets to return, e.g. 50; omit it to use 50 without changing ranking. |
Return datasets whose evaluated publish-reliability grade is at or below a threshold (the unreliable ones), with the worst grades and lowest on-time percentages first. Reliability measures timeliness of successful freshness observations, not uptime; sample days are included so agents can judge evidence depth. Use it for timeliness reliability grades; do not use it for individual anomalies, trends,
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | Maximum worst-ranked unreliable datasets to return, e.g. 50; omit it to use 50 without changing ranking. |
| at_or_below_grade | string | no | Inclusive published reliability threshold; e.g. 'C' returns grades C, D, and F; omit it to use C. |
Return datasets with published structural or record-count drift evidence, ranked with structural changes first. Optionally require a minimum number of structural transitions; includes pipeline-computed evidence so agents do not infer drift from freshness alone. Use it for structural or record-count changes; do not use it for freshness risk, anomalies, trends, or reliability—use find_stale, find_an
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | Maximum structural-first ranked drift results to return, e.g. 50; omit it to use 50 without changing ranking. |
| min_change_count | integer | no | Inclusive filter on the larger published shape or column transition count, e.g. 1; omit it to include every drift row. |
Return the published cross-source reconciliation group for a dataset name or id, including per-member counts, dates, statuses, tolerances, and contextual deltas. A discrepancy requires human review and does not prove either source is wrong. Use it to compare a dataset with its published cross-source group; do not use it for provenance or evidence receipts—use get_provenance or get_evidence instead
| Parameter | Type | Required | Notes |
|---|---|---|---|
| dataset_name | string | yes | Stable dataset slug or exact display name to resolve, e.g. 'interestrates' or 'Monthly Interest Rates'; use search_datasets to discover valid values. |
Use when asked 'can I cite this source?', for licence and attribution, or for citation-ready provenance. Returns source, steward, licence/attribution context, canonical URL, and compact published evidence context: probe time, transport, access dependency, freshness signal, schema drift / record-count drift context, anomaly flag, and status. Bind a citation to dataset identity, source/evidence URL,
| Parameter | Type | Required | Notes |
|---|---|---|---|
| dataset_ids | array | yes | Dataset slugs returned by search_datasets for a batched citation lookup, e.g. ['fuelprice', 'pricecatcher']; preserve order and use get_dataset for display-name resolution. |
Use for a deep evidence audit or to inspect a provenance and evidence receipt. Returns the complete published evidence receipt for one dataset: probe time, transport, access dependency, freshness, schema drift / record-count drift, tolerance, status, anomaly fields, and receipt/evidence references. It reads published pipeline evidence, not a live source fetch: you may report what the pipeline obse
| Parameter | Type | Required | Notes |
|---|---|---|---|
| dataset_id | string | yes | Stable dataset slug returned by search_datasets for its complete receipt, e.g. 'fuelprice'; this tool requires the slug, not a display name. |
This is the preferred single-call pre-trust check for 'is this dataset current?', stale, unknown-freshness, degraded, or browser-dependent questions, and whenever an agent must verify before relying on data. Returns dataset metadata, published evidence and fail-closed signed receipt verification with artifact references. It verifies published artifacts, not a live source check: you may infer wheth
| Parameter | Type | Required | Notes |
|---|---|---|---|
| dataset_id | string | yes | Stable dataset slug returned by search_datasets for the published receipt check, e.g. 'fuelprice'; this tool requires the slug, not a display name. |
| include_proof_steps | boolean | no | Set true to include bounded verifier diagnostics for an audit, e.g. false; omit it to suppress diagnostics without changing verification. |
Return a freshness-at-a-glance summary of the published catalogue: fresh, aging, stale, and reference counts plus the latest health check time. Use it for catalogue-level freshness context; do not use it to enumerate affected datasets—use find_stale instead. It reads the latest published snapshot, so missing counts or check time mean the artifact omitted them; DataPulse is read-only, requires no A
No parameter schema on file.
Use when a fresh, rate-limited live-vs-published comparison is needed for a direct-access dataset, for example after asking whether a government dataset is reachable now. Performs a rate-limited live GET and returns comparable transport receipts plus a match, mismatch, unreachable, or not_verifiable verdict. This live check is an observation, not semantic truth: it does not recompute content dates
| Parameter | Type | Required | Notes |
|---|---|---|---|
| dataset_id | string | yes | Stable direct-access dataset slug returned by search_datasets for a live transport observation, e.g. 'fuelprice'; browser-dependent sources return not_verifiable. |
Return published attestation facts, the unsigned methodology-versioned trust score, numeric components, and component_availability reasons, plus existing health/trend/drift/reconciliation evidence for one canonical dataset id, e.g. 'fuelprice'. This tool does not re-probe or verify the signature; call verify_attestation separately. Use it to assemble the published trust view; do not use it for rec
| Parameter | Type | Required | Notes |
|---|---|---|---|
| dataset_id | string | yes | Stable dataset slug returned by search_datasets to aggregate, e.g. 'fuelprice'; display names are not resolved here. |
Use to verify a signed published probe attestation after an evidence audit. Returns L1 signature, key, time, and chain-link checks; optional L2 replay of daily heads to a Git-tag anchor; and L3 scope, which requires verify_evidence for live transport. A valid signature proves attestation integrity and scope, not upstream semantic truth or currentness. For a deep audit use search_datasets → get_evi
| Parameter | Type | Required | Notes |
|---|---|---|---|
| reference | string | yes | Dataset slug returned by search_datasets or an exact published digest reference, e.g. 'fuelprice'; the slug resolves through the attestation index. |
| replay_chain | boolean | no | Set true to perform the slower L2 daily-head replay to a Git tag, e.g. true; omit it to run L1 only. |
Return all datasets with the given licence, summarised. Use to enumerate what's available under a specific licence for compliance/reuse scoping. Use it to enumerate one licence; do not use it to discover by topic or inspect a dataset's citation context—use search_datasets or get_provenance instead. It reads published manifest data, so an empty list means no published dataset has the resolved licen
| Parameter | Type | Required | Notes |
|---|---|---|---|
| licence | string | yes | Exact published licence name or supported alias, e.g. 'Creative Commons Attribution 4.0'; use search_datasets to discover licence values. |
Aggregate anonymous tool usage for an inclusive ISO date range, e.g. 2026-08-01 to 2026-08-07. Returns total_calls, by_outcome, by_tool, by_dataset, trust_verdict_calls (the count of trust_verdict records regardless of outcome or result shape), and trust_distribution (counts of returned trust verdicts by published score band: 90-100, 75-89, 50-74, 25-49, 0-24) for the inclusive range.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| since | string | yes | Inclusive first day of the persisted-record window, e.g. '2026-08-01'; it must not be after until. |
| until | string | yes | Inclusive last day of the persisted-record window, e.g. '2026-08-07'; it must not be before since. |
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 DataPulse MY 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: —
—Grade not published
No rule-by-rule report on file for this release
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.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
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 3.55.24.
3.55.24
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 DataPulse MY 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.