io.github.jrlprost/filoo-mcp
NPM · @FILOOAPP/MCP-SERVER · SCANNED SEP 22
Create short links, fetch click analytics, and generate QR codes via the filoo.app API.
Available components
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
- 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- 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 124 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability82
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 825 tokens (~91/item across 9 items; 9 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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 Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "filoo_delete_link" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 9 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
How do I install the io.github.jrlprost/filoo-mcp server?
io.github.jrlprost/filoo-mcp runs locally as an npm package, launched with npx -y @filooapp/mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @filooapp/mcp-server
claude mcp add jrlprost-filoo-mcp -- npx -y @filooapp/mcp-server
{
"mcpServers": {
"jrlprost-filoo-mcp": {
"command": "npx",
"args": [
"-y",
"@filooapp/mcp-server"
]
}
}
} {
"servers": {
"jrlprost-filoo-mcp": {
"command": "npx",
"args": [
"-y",
"@filooapp/mcp-server"
]
}
}
} codex mcp add jrlprost-filoo-mcp -- npx -y @filooapp/mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"jrlprost-filoo-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"@filooapp/mcp-server"
],
"enabled": true
}
}
} openclaw mcp add jrlprost-filoo-mcp --command npx --arg -y --arg @filooapp/mcp-server
mcp_servers:
jrlprost-filoo-mcp:
command: "npx"
args: ["-y", "@filooapp/mcp-server"] {
"McpServers": {
"jrlprost-filoo-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@filooapp/mcp-server"
]
}
}
} assistant mcp add jrlprost-filoo-mcp -t stdio -c npx -a -y @filooapp/mcp-server
{
"mcpServers": {
"jrlprost-filoo-mcp": {
"command": "npx",
"args": [
"-y",
"@filooapp/mcp-server"
]
}
}
} 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.
- 22 Sept 26 +1
- Stability: 0.97 → pass security
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −3
- Stability: pass → 0.80 functional
- 15 Sept 26 +1
- Stability: 0.97 → pass security
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 −3
- Stability: pass → 0.83 functional
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 22 Sept 2026 · Analysed npm/@filooapp/mcp-server@0.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 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| 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 →
filoo_create_link ~171
Create a new short link on filoo. Returns the short_url (filoo.app/{username}/{slug}) and the link code. Use this whenever an agent needs to shorten a URL, hand a clean URL to a user, generate a QR-friendly link, or attach click tracking to an outbound URL. Counts against the daily creation quota and active link cap — call filoo_usage first if unsure.
| Name | Type | Req | Description |
|---|---|---|---|
| destination | string | yes | The long URL to shorten (http or https). |
| label | string | – | Optional private label shown only in the dashboard. |
| slug | string | – | Optional custom slug like 'spring-sale'. Alphanumeric + hyphens, 1–64 chars. Auto-generated if omitted. |
| username | string | – | Username to publish under. Defaults to the user's primary username. |
No output schema declared.
No examples provided.
filoo_delete_link ~76
Permanently delete a filoo short link. The short_url stops resolving (returns 404). Click history is preserved on the filoo side for analytics. This action cannot be undone — confirm with the user before calling unless they explicitly asked to delete.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | Link code in the form 'username:slug'. |
No output schema declared.
No examples provided.
filoo_get_link ~81
Get full details for one filoo short link by code. The code format is 'username:slug' (the colon is URL-encoded automatically). Returns destination, label, active flag, created_at, and short_url.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | Link code in the form 'username:slug', e.g. 'agency:campaign-1'. |
No output schema declared.
No examples provided.
filoo_link_stats ~80
Get click/scan analytics for one filoo short link: total clicks, unique visitors, bot count, top countries, and top traffic sources (including QR-code sources). Use to answer questions like 'how is my campaign link doing?' or to compare performance across links.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | Link code in the form 'username:slug'. |
No output schema declared.
No examples provided.
filoo_list_links ~100
List the authenticated user's short links, newest first, cursor-paginated. Returns items[] with code, short_url, destination, created_at, plus a cursor to fetch the next page. Use to inventory existing links before creating a new one (avoid duplicates) or to find a link by destination.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Pagination cursor from a previous call. |
| limit | integer | – | Page size, max 100. Default 20. |
No output schema declared.
No examples provided.
filoo_list_usernames ~62
List every username the authenticated user owns on filoo, along with which one is primary. Short links live under a username (filoo.app/{username}/{slug}), so this is the canonical way for an agent to discover what namespaces it can publish into.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
filoo_me ~73
Get the authenticated filoo user's account: tier (free/solo/pro/agents/lifetime), owned usernames, boost credits, and tier limits (active links cap, links-per-day quota, API rate limit). Call this first when an agent needs to know what username to publish under or how much headroom is left.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
filoo_update_link ~130
Update a filoo short link in place: change its destination (the previous destination is kept in the audit history so the short URL is safe to repoint), edit its label, or disable/re-enable it with active. The short_url itself never changes. Useful for keeping a stable short URL while migrating the target.
| Name | Type | Req | Description |
|---|---|---|---|
| active | boolean | – | Set false to disable the link, true to re-enable. |
| code | string | yes | Link code in the form 'username:slug'. |
| destination | string | – | New long URL to redirect to. |
| label | string | – | New private label. |
No output schema declared.
No examples provided.
filoo_usage ~52
Get today's filoo usage versus quotas: links created today, daily creation cap, API calls today, active link count, active link cap, remaining boost credits. Use before bulk-creating links to avoid hitting limits.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the io.github.jrlprost/filoo-mcp server?
io.github.jrlprost/filoo-mcp is listed in the public MCP registry as io.github.jrlprost/filoo-mcp. Create short links, fetch click analytics, and generate QR codes via the filoo.app API. This page covers its npm package (@filooapp/mcp-server).
Is the io.github.jrlprost/filoo-mcp server safe to use?
io.github.jrlprost/filoo-mcp scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 September 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 io.github.jrlprost/filoo-mcp server expose?
io.github.jrlprost/filoo-mcp exposes 9 tools: filoo_me, filoo_usage, filoo_list_usernames, filoo_create_link, filoo_list_links, and 4 more. Their descriptions and schemas cost roughly 825 tokens of context every time the server is loaded.
Is the io.github.jrlprost/filoo-mcp server still maintained?
io.github.jrlprost/filoo-mcp is still listed as active in the MCP registry. We last reached this channel on 22 September 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 io.github.jrlprost/filoo-mcp server under?
io.github.jrlprost/filoo-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.