# Ine Pt [Health: Active]

**Category:** 🧮 Data Science Tools  
**Repository:** https://github.com/pipeworx-io/mcp-ine-pt  
**GitHub Stars:** 0  
**npm Downloads (last month):** 414  
**Views:** 2  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/ine-pt

## Description
Statistics Portugal (INE) JSON indicator MCP.

## Tools
Capabilities this server exposes over MCP:

- **indicator_meta** — Metadata for an INE (Statistics Portugal) indicator: title, periodicity, unit, time range, and the full list of dimensions with their valid dimension-value codes. Call this BEFORE get_indicator so you know which Dim1/Dim2/... codes are valid. Requires the indicator code (varcd) — INE has no keyword/search endpoint, so look the code up on https://www.ine.pt first.
- **get_indicator** — Fetch data values for an INE (Statistics Portugal) indicator. Pass the indicator code (varcd) and optionally a `dims` object mapping dimension slots ("Dim1","Dim2",...) to dimension-value codes to select a slice (codes come from indicator_meta). Omit a Dim slot to return all of its values. Requires varcd — INE has no keyword/search endpoint, so look the code up on https://www.ine.pt first.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

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

## Documentation

## What the Ine Pt MCP server does

The Ine Pt MCP server connects an MCP client to indicator data from Statistics Portugal (INE). It provides two pack-specific tools: `indicator_meta` describes an indicator, while `get_indicator` retrieves its values. The data interface is organized around INE indicator codes rather than text searches, so an indicator code must be identified on the INE website before using either tool.

`indicator_meta` returns the indicator title, periodicity, unit, available time range, and its dimensions. For each dimension, the response includes valid dimension-value codes. This makes it the discovery step for constructing a valid data request.

`get_indicator` accepts the same indicator code and can optionally receive a `dims` object. Keys such as `Dim1` and `Dim2` identify dimension slots, and their values select dimension-value codes returned by `indicator_meta`. Leaving out a dimension slot returns all values for that dimension.

## How it works

A typical request starts by calling `indicator_meta` with `varcd`. The client can then use the returned dimension structure to choose valid filters before calling `get_indicator`. This two-step flow is useful for indicators with multiple dimensions because the valid codes are indicator-specific.

The hosted MCP endpoint is `https://gateway.pipeworx.io/ine-pt/mcp`. The same gateway also exposes a full endpoint at `https://gateway.pipeworx.io/mcp`; the pack endpoint lists the INE tools alongside shared Pipeworx meta-tools, while the standalone package exposes only the INE pack tools. The gateway's `ask_pipeworx` tool can route plain-language questions to catalog tools, including this pack.

## Setup and configuration

For an MCP client that supports remote endpoints, add the pack URL as an MCP server. The README specifically shows Claude Desktop, Cursor, and Windsurf configurations using the hosted endpoint. The gateway also offers direct HTTP access: send a JSON POST request to `/v1/tools/indicator_meta` or another tool path, with the required arguments in the request body.

A local installation is available through the `@pipeworx/mcp-ine-pt` npm package. Configure the client to run `npx -y @pipeworx/mcp-ine-pt`; the process communicates over stdin and stdout and does not require a Pipeworx account. The hosted gateway and the local package use the same pack tools, but only the gateway connection includes shared meta-tools.

## Tools and capabilities

- `indicator_meta`: retrieves indicator metadata and valid dimension-value codes.
- `get_indicator`: retrieves indicator values for all dimensions or a selected slice.
- Optional dimension filtering uses a `dims` mapping such as `Dim1` and `Dim2`.
- Hosted use supports MCP connections and direct HTTP tool calls.
- Local use supports stdio MCP without a gateway round trip.

## Limitations and notes

The Ine Pt MCP server does not search INE indicators by keyword. Callers need to find the `varcd` on `ine.pt` first. Dimension filters must use codes supplied by `indicator_meta`; arbitrary labels or unknown codes may not select the intended data.

The hosted pack endpoint lists shared Pipeworx meta-tools in addition to the two INE tools, so its reported tool count is larger than the pack's own list. A local stdio process lists only the INE tools. The gateway documentation says that initial calls do not require an account, but the material does not specify rate limits or data update schedules.

_Full upstream README: https://allmcps.com/mcp/ine-pt/readme_