Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.colapsis/transfa

NPM · TRANSFA-MCP · SCANNED SEP 30

Upload any file, get a signed link. SHA-256 verified, TTL-enforced, no account required.

Available components

0 this week 84 Trust /100
Trust breakdown (7 categories)

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 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
  • 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 137 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability82
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 351 tokens (~87/item across 4 items; 4 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; "delete_upload" 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 4 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
Install

How do I install the io.github.colapsis/transfa MCP server?

io.github.colapsis/transfa runs locally as an npm package, launched with npx -y transfa-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 · transfa-mcp

# add to Claude Code
claude mcp add colapsis-transfa -- npx -y transfa-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "colapsis-transfa": {
      "command": "npx",
      "args": [
        "-y",
        "transfa-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "colapsis-transfa": {
      "command": "npx",
      "args": [
        "-y",
        "transfa-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add colapsis-transfa -- npx -y transfa-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "colapsis-transfa": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "transfa-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add colapsis-transfa --command npx --arg -y --arg transfa-mcp
# ~/.hermes/config.yaml
mcp_servers:
  colapsis-transfa:
    command: "npx"
    args: ["-y", "transfa-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "colapsis-transfa": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "transfa-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add colapsis-transfa -t stdio -c npx -a -y transfa-mcp
// mcp.json
{
  "mcpServers": {
    "colapsis-transfa": {
      "command": "npx",
      "args": [
        "-y",
        "transfa-mcp"
      ]
    }
  }
}
Changelog

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.

  • 30 Sept 26 0
    • Stability: 0.97 → pass security
  • 29 Sept 26 +1

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

  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Sept 26 +1
    • Security disclosure: unverified → pass ▲ functional
  • 26 Sept 26 0
    • Security disclosure: pass → unverified ▼ functional
  • 25 Sept 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 24 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 23 Sept 26 0
    • Stability: 0.97 → pass security
Diagnostics

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 30 Sept 2026 · Analysed npm/transfa-mcp@1.0.1

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 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 4 exposed · ~351 tokens

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 →

Tool Tokens
delete_upload ~34

Delete an upload immediately. Requires ownership (API key must match the uploader).

NameTypeReqDescription
idstringyesUpload ID to delete

No output schema declared.

No examples provided.

file_info ~71

Get metadata about an upload without downloading it. Returns filename, size, SHA-256, expiry, download count, active status, and whether the file is in a grace period.

NameTypeReqDescription
idstringyesUpload ID (the short code in the URL, e.g. "a7f9k2")

No output schema declared.

No examples provided.

list_uploads ~46

List your recent uploads. Requires TRANSFA_API_KEY or a key saved by `tf auth`.

NameTypeReqDescription
limitnumber–Number of results (1–100, default 10)

No output schema declared.

No examples provided.

upload ~200

Upload a file from the local filesystem and get a signed link. Returns an agent_link (direct download URL for scripts/agents) and a human_link (browser-friendly share page). SHA-256 is always computed and returned for integrity checks. Works without an API key (guest mode, 10 MB limit). Set TRANSFA_API_KEY for larger files and longer TTLs.

NameTypeReqDescription
expiresstring–TTL: "1h", "24h", "7d", "30d". Default: 7d
gracestring–Grace period after expiry, e.g. "12h" — keeps file downloadable this long after TTL ends
max_downloadsnumber–Max download count
namestring–Override filename shown to recipient
onceboolean–Delete after first download
passwordstring–Password-protect the link
pathstringyesPath to the file to upload

No output schema declared.

No examples provided.

Common questions

What is the io.github.colapsis/transfa MCP server?

io.github.colapsis/transfa is an MCP server listed in the public MCP registry as io.github.colapsis/transfa. Upload any file, get a signed link. SHA-256 verified, TTL-enforced, no account required. This page covers its npm package (transfa-mcp).

Is the io.github.colapsis/transfa MCP server safe to use?

io.github.colapsis/transfa scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 30 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.colapsis/transfa MCP server expose?

io.github.colapsis/transfa exposes 4 tools: upload, file_info, list_uploads, delete_upload. Their descriptions and schemas cost roughly 351 tokens of context every time the server is loaded.

Is the io.github.colapsis/transfa MCP server still maintained?

io.github.colapsis/transfa is still listed as active in the MCP registry. We last reached this channel on 30 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.colapsis/transfa MCP server under?

io.github.colapsis/transfa declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.