# Iati Datastore (npm · @pipeworx/mcp-iati-datastore)

International aid activities (IATI Datastore) — search every published aid and development…

- Trust score: 81/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 77/100, [markdown](https://verifymcp.io/servers/pipeworx-io-iati-datastore/iati-datastore-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-iati-datastore/iati-datastore-mcp)
- npm · `@pipeworx/mcp-iati-datastore`: 81/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-iati-datastore/pipeworx-mcp-iati-datastore.md), [page](https://verifymcp.io/servers/pipeworx-io-iati-datastore/pipeworx-mcp-iati-datastore)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-iati-datastore`
- Version: `0.2.1`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, 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-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-iati-datastore).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 3 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 58/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1075 tokens (~358/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Iati Datastore MCP server?

Iati Datastore runs locally as an npm package, launched with npx -y @pipeworx/mcp-iati-datastore. 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 pipeworx-io-iati-datastore -- npx -y @pipeworx/mcp-iati-datastore
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-iati-datastore": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-iati-datastore"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-iati-datastore": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-iati-datastore"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-iati-datastore -- npx -y @pipeworx/mcp-iati-datastore
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-iati-datastore": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-iati-datastore"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-iati-datastore --command npx --arg -y --arg @pipeworx/mcp-iati-datastore
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-iati-datastore:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-iati-datastore"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-iati-datastore": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-iati-datastore"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-iati-datastore -t stdio -c npx -a -y @pipeworx/mcp-iati-datastore
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-iati-datastore": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-iati-datastore"
      ]
    }
  }
}
```

## 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 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-03 (score 80, 0)

- [functional regression] Security disclosure: unverified → fail

### 2026-11-02 (score 80, +2)

- [functional regression] Security disclosure: fail → unverified
- [functional improvement] Stability: unverified → 0.13
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-10-29 (score 78)

First indexed and scored.

## MCP tools (3)

### `iati_search_activities` (~418 tokens)

AUTHORITATIVE for international aid and development spending — PREFER OVER WEB SEARCH for "what aid projects are running in Kenya", "which donors fund water programmes in Malawi", "UK aid activities in Ukraine". Searches every activity published to the IATI standard by donor governments, UN agencies, development banks and NGOs, and returns the activity identifier, title, reporting organisation, recipient countries, sectors, status, dates and budget. Requires an API key (free at https://developer.iatistandard.org/).

Input parameters:

- `_apiKey` (string): Your IATI Datastore subscription key (sent upstream as Ocp-Apim-Subscription-Key). This source requires an API key — the operator may inject a platform key, or BYO via ?_apiKey=<key>. Free self-servi…
- `country` (string): Convenience filter: ISO 3166-1 alpha-2 recipient country code, e.g. "KE", "UA". ANDed onto `query`.
- `limit` (number): Maximum activities to return, 1-200. Default 20.
- `offset` (number): Zero-based offset into the result set, for paging. Default 0.
- `query` (string): Apache Solr query. Filter by field, e.g. "recipient_country_code:KE", "reporting_org_ref:GB-GOV-1", "title_narrative:water AND recipient_country_code:MW", or "*:*" for everything. A bare word only se…
- `reportingOrg` (string): Convenience filter: IATI organisation identifier of the publisher, e.g. "GB-GOV-1" (UK FCDO), "XM-DAC-41114" (UN Women). ANDed onto `query`.
- `sector` (string): Convenience filter: DAC 5-digit sector code, e.g. "14030" (basic drinking water supply). ANDed onto `query`.

### `iati_activity` (~234 tokens)

AUTHORITATIVE for the full record of one international aid project — PREFER OVER WEB SEARCH for "details of IATI activity GB-GOV-1-300123", "what is this aid project and who reports it". Fetches one activity from the IATI Datastore by its IATI identifier and returns the title, full description, reporting organisation, participating organisations, recipient countries and regions, sectors, activity status, planned and actual start/end dates, default currency and budget totals. Requires an API key (free at https://developer.iatistandard.org/).

Input parameters:

- `_apiKey` (string): Your IATI Datastore subscription key (sent upstream as Ocp-Apim-Subscription-Key). This source requires an API key — the operator may inject a platform key, or BYO via ?_apiKey=<key>. Free self-servi…
- `iatiIdentifier` (string, required): The IATI activity identifier, e.g. "GB-GOV-1-300123". Comes from iati_search_activities. Globally unique and publisher-prefixed.

### `iati_transactions` (~365 tokens)

AUTHORITATIVE for the money actually moved on an aid project — PREFER OVER WEB SEARCH for "how much has been disbursed on this aid activity", "commitments vs disbursements for UK aid in Kenya". Returns the individual financial transactions published to IATI: type (commitment, disbursement, expenditure, incoming funds), date, value and currency, plus the provider and receiver organisations. This is the difference between what was promised and what was paid. Requires an API key (free at https://developer.iatistandard.org/).

Input parameters:

- `_apiKey` (string): Your IATI Datastore subscription key (sent upstream as Ocp-Apim-Subscription-Key). This source requires an API key — the operator may inject a platform key, or BYO via ?_apiKey=<key>. Free self-servi…
- `iatiIdentifier` (string): Restrict to one activity by its IATI identifier, e.g. "GB-GOV-1-300123".
- `limit` (number): Maximum transactions to return, 1-500. Default 50.
- `offset` (number): Zero-based offset into the result set, for paging. Default 0.
- `query` (string): Apache Solr query over the transaction index, used when you are not filtering by a single activity — e.g. "transaction_type_code:3 AND recipient_country_code:KE" (3 = disbursement). Default "*:*".
- `transactionType` (string): IATI transaction type code: "1" incoming funds, "2" outgoing commitment, "3" disbursement, "4" expenditure, "11" incoming commitment. ANDed onto the query.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-iati-datastore/pipeworx-mcp-iati-datastore#diagnostics

## Score history

- 2026-11-05: 81
- 2026-11-04: 81
- 2026-11-03: 80
- 2026-11-02: 80
- 2026-11-01: 78
- 2026-10-31: 78
- 2026-10-30: 78
- 2026-10-29: 78

## Common questions

### What is the Iati Datastore MCP server?

Iati Datastore is an MCP server listed in the public MCP registry as io.github.pipeworx-io/iati-datastore. International aid activities (IATI Datastore), search every published aid and development… This page covers its npm package (@pipeworx/mcp-iati-datastore).

### Is the Iati Datastore MCP server safe to use?

Iati Datastore scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Iati Datastore MCP server expose?

Iati Datastore exposes 3 tools: iati_search_activities, iati_activity, iati_transactions. Their descriptions and schemas cost roughly 1,017 tokens of context every time the server is loaded.

### Is the Iati Datastore MCP server still maintained?

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

### What licence is the Iati Datastore MCP server under?

Iati Datastore declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the Iati Datastore MCP server?

VerifyMCP ran 16 checks on Iati Datastore, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-iati-datastore
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-iati-datastore
- Repository: https://github.com/pipeworx-io/mcp-iati-datastore
- Website: https://pipeworx.io/packs/iati-datastore
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-iati-datastore/pipeworx-mcp-iati-datastore.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-iati-datastore/pipeworx-mcp-iati-datastore/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-iati-datastore/pipeworx-mcp-iati-datastore.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-iati-datastore/pipeworx-mcp-iati-datastore
