
Fileshareforagents
online.fileshareforagentsPublished by fileshareforagents.onlinev0.2.0Updated Nov 3, 2026
Storage for AI agents: free public items, or private items paid with credits or USDC (x402).
Overview
Local MCP server that lets an assistant store, share and retrieve files and text through fileshareforagents.online, free for public items or paid per call.
- What you can do
- Store content publicly for up to 7 days, or privately for 1 to 365 days, as text, JSON, base64 bytes or a local file
- Retrieve stored items inline or saved to a file, and check expiry, reads left, size and type
- Extend retention, buy extra reads, and delete items permanently
- Create signed time-limited share links, revoke them, and set or remove a password on the public address
- Check pricing, wallet balance and account credits, buy credits with USDC, and send feedback
- When to use it
- Useful when an assistant needs to hand a file or snippet to a human or another agent, or park content somewhere reachable for a few days, without setting up its own storage. Also fits agents that need a simple paid drop box with credit or USDC billing.
- Requirements
- Runs locally over stdio, typically via npx with Node.js. An account API key in FILESHARE_API_KEY, or a wallet private key in WALLET_KEY holding USDC, is needed for paid tools; free tools work without either. FILESHARE_NETWORK selects testnet (default, Base Sepolia) or mainnet (Base). Network access to the service is required.
Installation
In SourceWeft
- Open Fileshareforagents in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
fileshareforagents-mcp
MCP server for fileshareforagents.online: storage and file sharing for AI agents. Public items (up to 7 days) are free. Private items, longer retention, extensions and read packs are paid calls, one cent each, and there are two ways to pay:
- Prepaid credits, no wallet. Sign in at https://fileshareforagents.online/login, buy
credits (10 are included on signup), create an API key in the dashboard and set it as
FILESHARE_API_KEY. Each paid call spends one credit. - USDC over x402. Set
WALLET_KEYto a wallet holding USDC on Base; the server signs a $0.01 payment per call. The key never leaves the process and is never sent to the service. With both configured, credits are used first and the wallet steps in when they run out.
The server runs locally next to your agent (stdio).
Install
Claude Desktop, Claude Code, Cursor, Windsurf and most MCP clients take a config like this:
Claude Code, one line:
Paying with a wallet instead: replace FILESHARE_API_KEY with WALLET_KEY=0x... (a private
key of a wallet holding USDC on the chosen network).
Start on testnet (the default): free test USDC on Base Sepolia from
faucet.circle.com, nothing real at stake. Switch to real money
with FILESHARE_NETWORK=mainnet and a wallet holding USDC on Base. The wallet needs no ETH;
the payment facilitator pays gas.
Without WALLET_KEY the free tools work and the paid ones explain what to set.
Tools
Allowed content: JSON, text, Markdown, CSV, HTML, SVG, PDF, PNG, JPEG, WebP, GIF, up to 25 MB.
Two ways to hand content to a human
share_linkwithexpires_inseconds. Send the URL. Nothing else needed, but anyone holding the URL can read until it expires.set_password, then send the returnedpublic_urland the password over different channels. The address asks for the password on every open.
Each open counts one read; buy_reads first if many people will open it.
Environment
Notes
- Content is deleted at expiry and cannot be recovered. This is a drop box, not a vault.
- Keep the
secretfromstore; it is shown once. Whoever has it controls the item. - Terms of service: https://fileshareforagents.online/terms. Machine-readable docs: https://fileshareforagents.online/llms.txt.
- Failed settlements are never charged; the server retries once and otherwise returns the
service's error with a
request_idyou can quote infeedback.
MIT licensed.
Source: mcp/README.md at commit d6b0516
Tools
0Version history
2- v0.2.0LatestSep 29, 2026
- v0.1.2Sep 18, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts