# FileSeen (npm · fileseen-mcp)

Send files as tracked links from any AI agent and see who opened them, page by page.

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

## Components

- remote · `mcp.fileseen.com`: 36/100, [markdown](https://verifymcp.io/servers/com-fileseen-fileseen/mcp.md), [page](https://verifymcp.io/servers/com-fileseen-fileseen/mcp)
- npm · `fileseen-mcp`: 69/100 (this document), [markdown](https://verifymcp.io/servers/com-fileseen-fileseen/fileseen-mcp.md), [page](https://verifymcp.io/servers/com-fileseen-fileseen/fileseen-mcp)

## Channel facts

- Registry: `npm`
- Package: `fileseen-mcp`
- Version: `1.2.0`
- 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**: 98/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.
  - 30 of 92 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 19/100
  - Repository check failed: no source repository is declared.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 12 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 66/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1400 tokens (~233/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 43/100
  - Stability observed for 13 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 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 FileSeen MCP server?

FileSeen runs locally as an npm package, launched with npx -y fileseen-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 com-fileseen-fileseen -- npx -y fileseen-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "com-fileseen-fileseen": {
      "command": "npx",
      "args": [
        "-y",
        "fileseen-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-fileseen-fileseen": {
      "command": "npx",
      "args": [
        "-y",
        "fileseen-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add com-fileseen-fileseen -- npx -y fileseen-mcp
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add com-fileseen-fileseen --command npx --arg -y --arg fileseen-mcp
```

### Hermes

```yaml
mcp_servers:
  com-fileseen-fileseen:
    command: "npx"
    args: ["-y", "fileseen-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "com-fileseen-fileseen": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "fileseen-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-fileseen-fileseen -t stdio -c npx -a -y fileseen-mcp
```

### Other

```json
{
  "mcpServers": {
    "com-fileseen-fileseen": {
      "command": "npx",
      "args": [
        "-y",
        "fileseen-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-04 (score 69, +1)

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

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

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

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

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

### 2026-10-29 (score 66, +3)

- [functional improvement] Stability: unverified → 0.20

### 2026-10-24 (score 63, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-10-23 (score 48)

First indexed and scored.

## MCP tools (6)

### `create_tracked_link` (~149 tokens)

Turn a local file (PDF, Word, PowerPoint, Excel, images and more) into a FileSeen link to paste into an email or message from any provider (Gmail, Outlook, Apple Mail, Slack, WhatsApp). Use it whenever the user is about to send or attach a document and would want to know if it was seen. Returns the link, a ready line for the email, and an id for check_if_seen.

Input parameters:

- `file_path` (string, required): Absolute path to the file to share.
- `name` (string): Optional link name, e.g. acme-proposal.
- `notify` (boolean): Email the user when it is opened. Default true.

### `check_if_seen` (~94 tokens)

Check whether a FileSeen link was opened: opened yes or no, how many times, first and last open, and reading time per page where the user's plan includes it. If an email image was added, it also gives 'Email opened (approximate)': a hint only, never proof the email was read. Checking never counts as an open.

Input parameters:

- `id` (string, required): The id returned by create_tracked_link.

### `list_my_links` (~217 tokens)

List my FileSeen links

The user's FileSeen links, newest first, with opens, unique viewers, reading time and completion, both all time and within the `since` window. Use it for 'how are my links doing', 'which documents were opened today' (since=today, opened=true) or 'which were never opened' (since=all, opened=false). Totals come first. Reading this never counts as an open.

Input parameters:

- `limit` (integer): Rows to return (default 25). Totals always cover every match.
- `opened` (boolean): true: only links opened within the window; false: only links NOT opened within it.
- `query` (string): Only links whose file name, link id or label contains this text.
- `since` (string): Time window: 24h, 7d, 30d, 4w, today, yesterday, all, or an ISO date/datetime such as 2026-10-01 (UTC unless an offset is given). Default 30d.

### `recent_activity` (~171 tokens)

Recent activity on my links

Recent visits across all the user's links, newest first: when, which document, who (name or email when the reader gave it, otherwise 'Viewer N'), country, device, reading time and the pages read. Opens by the same visitor within 30 minutes count as one visit. Use it for 'what happened this week' or 'who opened anything today'. Reading this never counts as an open.

Input parameters:

- `limit` (integer): Visits to return (default 25). Totals cover every visit in the window.
- `since` (string): Time window: 24h, 7d, 30d, 4w, today, yesterday, all, or an ISO date/datetime such as 2026-10-01 (UTC unless an offset is given). Default 7d.

### `get_link_analytics` (~204 tokens)

In-depth analytics for one link

Everything the private stats page shows for one link: totals (opens, unique viewers, reading time, completion), each page's time, reach and drop-off with page names, each viewer and visit, a daily timeline, downloads, countries, sources, files in a data room, and the settings that change how to read the numbers (email gate, view-only, expiry). Use it for 'who opened the pitch deck and which pages did they read?'. Reading this never counts as an open.

Input parameters:

- `id` (string, required): Link id (from create_tracked_link or list_my_links) or its token.
- `since` (string): Time window: 24h, 7d, 30d, 4w, today, yesterday, all, or an ISO date/datetime such as 2026-10-01 (UTC unless an offset is given). Default all (all time). Window numbers, pages, viewers and timeline f…

### `compare_links` (~172 tokens)

Compare links side by side

Side-by-side numbers for several links, ranked by attention (reading time, then opens): opens, unique viewers, reading time, average per session and completion within the window. Give ids, or a query that matches file names (e.g. 'proposal'). Use it for 'which of my proposals got the most attention this month?'.

Input parameters:

- `ids` (array): Link ids or tokens to compare (max 20).
- `query` (string): Compare every link whose file name, id or label contains this text.
- `since` (string): Time window: 24h, 7d, 30d, 4w, today, yesterday, all, or an ISO date/datetime such as 2026-10-01 (UTC unless an offset is given). Default 30d.

## Diagnostics

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

## Score history

- 2026-11-05: 69
- 2026-11-04: 69
- 2026-11-03: 68
- 2026-11-02: 68
- 2026-11-01: 67
- 2026-10-31: 67
- 2026-10-30: 66
- 2026-10-29: 66
- 2026-10-28: 63
- 2026-10-27: 63
- 2026-10-26: 63
- 2026-10-25: 63
- 2026-10-24: 63
- 2026-10-23: 48

## Common questions

### What is the FileSeen MCP server?

FileSeen is an MCP server listed in the public MCP registry as com.fileseen/fileseen. Send files as tracked links from any AI agent and see who opened them, page by page. This page covers its npm package (fileseen-mcp).

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

FileSeen scores 69 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. 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 FileSeen MCP server expose?

FileSeen exposes 6 tools: create_tracked_link, check_if_seen, list_my_links, recent_activity, get_link_analytics, compare_links. Their descriptions and schemas cost roughly 1,007 tokens of context every time the server is loaded.

### Is the FileSeen MCP server still maintained?

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

FileSeen declares the MIT 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/fileseen-mcp
- Socket report: https://socket.dev/npm/package/fileseen-mcp
- Website: https://fileseen.com/mcp/
- Changelog RSS feed: https://verifymcp.io/servers/com-fileseen-fileseen/fileseen-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-fileseen-fileseen/fileseen-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-fileseen-fileseen/fileseen-mcp