FileSeen
NPM · FILESEEN-MCP · 2 COMPONENTS
Send files as tracked links from any AI agent and see who opened them, page by page.
Available components
Last scanned (2 hours ago)
Scores higher than 36% of npm servers
Category Documents and Files
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. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 12 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability66
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management43
- Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +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.
- 2 Nov 26 +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.
- 31 Oct 26 +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.
- 29 Oct 26 +3
- Stability: unverified → 0.20 ▲ functional
- 24 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 23 Oct 26 48
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/fileseen-mcp@1.2.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_if_seen ~94
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The id returned by create_tracked_link. |
No output schema declared.
No examples provided.
compare_links Compare links side by side ~172
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?'.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
create_tracked_link ~149
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.
| Name | Type | Req | Description |
|---|---|---|---|
| file_path | string | yes | 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. |
No output schema declared.
No examples provided.
get_link_analytics In-depth analytics for one link ~204
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | 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… |
No output schema declared.
No examples provided.
list_my_links List my FileSeen links ~217
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
recent_activity Recent activity on my links ~171
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
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.
npm · fileseen-mcp
claude mcp add com-fileseen-fileseen -- npx -y fileseen-mcp
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.