# flowR (npm · @eagleoutice/flowr-mcp)

Static dataflow analysis, program slicing, linting, and dependency extraction for R code.

- Trust score: 75/100 (medium)
- Change this week: −5
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- npm · `@eagleoutice/flowr-mcp`: 75/100 (this document), [markdown](https://verifymcp.io/servers/flowr-analysis-flowr/eagleoutice-flowr-mcp.md), [page](https://verifymcp.io/servers/flowr-analysis-flowr/eagleoutice-flowr-mcp)

## Channel facts

- Registry: `npm`
- Package: `@eagleoutice/flowr-mcp`
- Version: `0.1.3`
- 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**: 73/100
  - No malware found by supply-chain analysis.
  - Known CVEs could not be checked: we could not reach the advisory database to check. This is a gap on our side.
  - No install/post-install scripts declared.
  - 34 of 82 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to flowr-analysis/flowr).
  - Clear OSI-approved license (ISC).
  - Actively maintained (last published 13 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 50/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 455 tokens (~455/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 53/100
  - Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 89/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 67% 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 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 1 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 flowR MCP server?

flowR runs locally as an npm package, launched with npx -y @eagleoutice/flowr-mcp. 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 flowr-analysis-flowr -- npx -y @eagleoutice/flowr-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "flowr-analysis-flowr": {
      "command": "npx",
      "args": [
        "-y",
        "@eagleoutice/flowr-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "flowr-analysis-flowr": {
      "command": "npx",
      "args": [
        "-y",
        "@eagleoutice/flowr-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add flowr-analysis-flowr -- npx -y @eagleoutice/flowr-mcp
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add flowr-analysis-flowr --command npx --arg -y --arg @eagleoutice/flowr-mcp
```

### Hermes

```yaml
mcp_servers:
  flowr-analysis-flowr:
    command: "npx"
    args: ["-y", "@eagleoutice/flowr-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "flowr-analysis-flowr": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@eagleoutice/flowr-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add flowr-analysis-flowr -t stdio -c npx -a -y @eagleoutice/flowr-mcp
```

### Other

```json
{
  "mcpServers": {
    "flowr-analysis-flowr": {
      "command": "npx",
      "args": [
        "-y",
        "@eagleoutice/flowr-mcp"
      ]
    }
  }
}
```

## 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 75, −8)

- [security regression] Known CVEs: pass → unverified

### 2026-11-04 (score 83, +1)

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

### 2026-11-02 (score 82, +1)

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

### 2026-10-31 (score 81, +1)

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

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

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

### 2026-10-27 (score 79, +1)

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

### 2026-10-25 (score 78, +1)

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

### 2026-10-23 (score 77, +28)

- [security improvement] Injection markers: unverified → pass
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Stability: unverified → 0.10
- [functional improvement] MCP protocol: unverified → pass

## MCP tools (1)

### `query` (~455 tokens)

Statically analyze R code and search R package signatures with flowR queries (https://github.com/flowr-analysis/flowr/wiki/Query-API). Common ones: {"type":"static-slice","criteria":["12@x"]} for the code affecting x in line 12, {"type":"linter"} for lint findings, {"type":"dependencies"} for loaded libraries, read and written files, {"type":"guess-dep-versions"} for the package versions the code works with, {"type":"call-context","callName":"^read_"} for calls, and, needing no code, {"type":"signature","package":"dplyr","function":"across"} to search signatures and versions (globs allowed), {"type":"function-info","name":"filter"} for the packages exporting a function. A query with wrong arguments is answered with its schema. Types: call-context (Call-Context Query), config (Config Query), control-flow (Control-Flow Query), call-graph (Call-Graph Query), dataflow (Dataflow Query), does-call (Does-Call Query), dataflow-lens (Dataflow Lens Query), absint (Abstract Interpretation Query), files (Files Query), id-map (Id-Map Query), normalized-ast (Normalized AST Query), dataflow-cluster (Dataflow Cluster Query), static-slice (Static Slice Query), provenance (Provenance Query), input-sources (Input Sources Query), dependencies (Dependencies Query), location-map (Location Map Query), search (Search Query), happens-before (Happens-Before Query), inspect-exception (Inspect Exceptions of Functions Query), inspect-higher-order (Inspect Higher-Order Functions Query), inspect-recursion (Inspect Recursive Functions Query), inspect-fn-props (Inspect Argument Roles Query), resolve-value (Resolve Value Query), project (Project Query), signature (Signature Query), origin (Origin Query), linter (Linter Query), dice (Dice Query), guess-dep-versions (Guess Dependency Versions Query), function-info (Function Info Query)

Input parameters:

- `code` (string): R code to analyze.
- `files` (array): R files or project folders to analyze.
- `queries` (array, required)

## Diagnostics

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

## Score history

- 2026-11-05: 75
- 2026-11-04: 83
- 2026-11-03: 82
- 2026-11-02: 82
- 2026-11-01: 81
- 2026-10-31: 81
- 2026-10-30: 80
- 2026-10-29: 80
- 2026-10-28: 79
- 2026-10-27: 79
- 2026-10-26: 78
- 2026-10-25: 78
- 2026-10-24: 77
- 2026-10-23: 77
- 2026-10-22: 49
- 2026-10-21: 65
- 2026-10-20: 50

## Common questions

### What is the flowR MCP server?

flowR is an MCP server listed in the public MCP registry as io.github.flowr-analysis/flowr. Static dataflow analysis, program slicing, linting, and dependency extraction for R code. This page covers its npm package (@eagleoutice/flowr-mcp).

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

flowR scores 75 out of 100 on VerifyMCP. 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 flowR MCP server expose?

flowR exposes 1 tool: query. Their descriptions and schemas cost roughly 455 tokens of context every time the server is loaded.

### Is the flowR MCP server still maintained?

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

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

## Links

- npm package: https://www.npmjs.com/package/@eagleoutice/flowr-mcp
- Socket report: https://socket.dev/npm/package/@eagleoutice/flowr-mcp
- Repository: https://github.com/flowr-analysis/flowr
- Changelog RSS feed: https://verifymcp.io/servers/flowr-analysis-flowr/eagleoutice-flowr-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/flowr-analysis-flowr/eagleoutice-flowr-mcp.json
- HTML version of this page: https://verifymcp.io/servers/flowr-analysis-flowr/eagleoutice-flowr-mcp