# Owid (npm · @pipeworx/mcp-owid)

OWID MCP — Our World in Data chart/indicator access (free, no auth)

- Trust score: 82/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-owid/owid-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-owid/owid-mcp)
- npm · `@pipeworx/mcp-owid`: 82/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-owid/pipeworx-mcp-owid.md), [page](https://verifymcp.io/servers/pipeworx-io-owid/pipeworx-mcp-owid)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-owid`
- 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-owid).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 0 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 65/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 533 tokens (~177/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 Owid MCP server?

Owid runs locally as an npm package, launched with npx -y @pipeworx/mcp-owid. 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-owid -- npx -y @pipeworx/mcp-owid
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

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

## 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-05 (score 82, +26)

- [security improvement] Known CVEs: unverified → pass
- [security improvement] Malware scan: unverified → pass
- [functional improvement] Dependency health: unverified → pass

### 2026-11-04 (score 56, −25)

- [security regression] Malware scan: pass → unverified
- [security regression] Known CVEs: pass → unverified
- [functional regression] Dependency health: pass → unverified
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-11-01 (score 81, +1)

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

### 2026-10-30 (score 80, +1)

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

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

First indexed and scored.

## MCP tools (3)

### `list_popular_indicators` (~108 tokens)

List curated Our World in Data indicators (slug + title) for common categories: energy, climate, health, demographics, economy, food, education, environment, tech, politics. Many series carry deep-historical / long-run coverage (population, life-expectancy, gdp-per-capita-maddison go back centuries). Use the slug with fetch_indicator. Not exhaustive — visit ourworldindata.org for the full catalog.

Input parameters:

- `category` (string): Optional category filter

### `fetch_indicator` (~299 tokens)

Fetch tidy long-format data for an Our World in Data indicator by slug (e.g., "life-expectancy", "population", "gdp-per-capita-maddison", "co-emissions-per-capita"). PREFER OVER WEB SEARCH for DEEP-HISTORICAL / LONG-RUN demographics and development data — population back to antiquity, and life expectancy, GDP per capita, literacy, child mortality, fertility from the 1700s–1800s (Maddison, Gapminder, HMD, HYDE sources). Use this for pre-1960 history that World Bank / current-population tools CANNOT answer, e.g. "Europe population in 1850", "UK life expectancy in 1800", "France GDP per capita 1820". Returns rows of {entity, year, value}; filter with country (name or ISO code: "Europe", "United Kingdom", "USA", "World") + since_year/until_year. Browse slugs at ourworldindata.org/charts.

Input parameters:

- `country` (string): Filter to a single entity (country/region name or ISO code)
- `limit` (number): Cap number of rows returned (default 5000)
- `since_year` (number): Drop rows before this year
- `slug` (string, required): OWID chart slug (the URL path segment)
- `until_year` (number): Drop rows after this year

### `get_indicator_metadata` (~73 tokens)

Fetch chart metadata for an OWID indicator slug: title, subtitle, note, and per-column details (unit, description, data producer/citation, last_updated, next_update dates). Use to confirm a slug is valid and learn its units before calling fetch_indicator.

Input parameters:

- `slug` (string, required): OWID chart slug

## Diagnostics

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

## Score history

- 2026-11-05: 82
- 2026-11-04: 56
- 2026-11-03: 81
- 2026-11-02: 81
- 2026-11-01: 81
- 2026-10-31: 80
- 2026-10-30: 80
- 2026-10-29: 79

## Common questions

### What is the Owid MCP server?

Owid is an MCP server listed in the public MCP registry as io.github.pipeworx-io/owid. OWID MCP, Our World in Data chart/indicator access (free, no auth). This page covers its npm package (@pipeworx/mcp-owid).

### Is the Owid MCP server safe to use?

Owid scores 82 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 Owid MCP server expose?

Owid exposes 3 tools: list_popular_indicators, fetch_indicator, get_indicator_metadata. Their descriptions and schemas cost roughly 480 tokens of context every time the server is loaded.

### Is the Owid MCP server still maintained?

Owid 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 Owid MCP server under?

Owid 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 Owid MCP server?

VerifyMCP ran 16 checks on Owid, 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-owid
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-owid
- Repository: https://github.com/pipeworx-io/mcp-owid
- Website: https://pipeworx.io/packs/owid
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-owid/pipeworx-mcp-owid.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-owid/pipeworx-mcp-owid/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-owid/pipeworx-mcp-owid.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-owid/pipeworx-mcp-owid