mcp server
io.github.colapsis/transfa
Upload any file, get a signed link. SHA-256 verified, TTL-enforced, no account required.
Description as published by the maintainer. Source
- version 1.0.1
- active
active — Most recent push to the repository was 2026-05-15.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| GitHub stars | 18 | Number of GitHub accounts that bookmarked this repository since it was created. It is a bookmark count, not installs, not active users and not quality. | cumulative, all time | GitHub | |
| Last commit | 2026-05-15 | Date of the most recent push to any branch. This is the strongest cheap indicator of whether the project is still maintained. | point in time | GitHub | |
| Open issues | 0 | Open issues plus open pull requests, as GitHub counts them together. A high number can mean an active project or an abandoned one. | as of fetch | GitHub | |
| Latest published version | 1.0.1 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-05-15 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| License | MIT | Licence GitHub detected in the repository. Detection can be wrong; the LICENSE file is authoritative. | as of fetch | GitHub | |
| First listed in the MCP Registry | 2026-05-15 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| repository status | active | The repository exists on GitHub and is not archived. This says nothing about how recently it was worked on. | as of fetch | GitHub |
Where to get it
Related, by what their authors tagged them
-
verify-proof
— last commit 2026-07-19, shares cli, sha256
Verify blockchain-anchored timestamp proofs offline. No network calls, account, or API key.
-
OBTO
— last commit 2026-08-05, shares self-hostable
Your AI builds, deploys, and runs full-stack apps on a hosted workspace created at first sign-in.
-
com.pentest-tools/mcp-server
— last commit 2026-08-03, shares cicd
MCP server for Pentest-Tools.com: run scans, manage findings and reports via your preffered LLM.
-
co.yungle/yungle
— last commit 2026-07-30, shares cli, file-transfer
Ask about your Yungle file deliveries — what was sent, who downloaded, what expires. Read-only.
-
dev.yafl/mcp
— last commit 2026-08-01, shares cli, file-transfer
Agent-first E2EE file transfer over MCP: move files between machines in one tool call, gone in 24h.
-
io.github.Daghis/teamcity
— last commit 2026-07-01, shares devops, nodejs
MCP server exposing JetBrains TeamCity CI/CD workflows to AI coding assistants
-
Servonaut
— last commit 2026-08-05, shares cli, devops
Manage AWS, Hetzner, OVH and SSH servers: status, logs, CloudWatch, IP bans, safe command exec.
-
LiteScope
— last commit 2026-07-14, shares cli, devops
Operations toolchain for SQLite, Cloudflare D1 & Turso: inspect, diff, migrate, monitor & repair.
-
io.github.danmartuszewski/hop
— last commit 2026-06-22, shares cli, devops
SSH connection manager with MCP server for AI-assisted operations across servers.
-
KSail
— last commit 2026-08-07, shares cli, devops
SDK for creating, managing, and operating Kubernetes clusters and workloads with ease.
These share tags the maintainers applied themselves, such as cli, sha256, self-hostable, cicd. Common tags like "mcp" or "ai" are ignored for this: agreeing with six hundred other projects is not a similarity.
This is not a recommendation and not a test result. It is a map of what the authors said their work is about.
How the author describes it
Topics the maintainer set on GitHub: cicd, cli, devops, file-sharing, file-transfer, mcp, nodejs, rest-api, self-hostable, sha256.
Bring your own setup
We take apart real AI setups every week and show what broke, what cost too much, and what the trace actually said. If you run agents on real work, that is where the useful conversation is.
Join ZBS AI Practice Lab