io.github.putput-io-dev/putput-mcp
REMOTE · PUTPUT.IO · 2 COMPONENTS · SCANNED SEP 22
File uploads for AI agents. Upload, list, and manage files. No signup required.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 185 tokens (~46/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_file" 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
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
How do I install the io.github.putput-io-dev/putput-mcp server?
io.github.putput-io-dev/putput-mcp is a hosted endpoint at https://putput.io/api/v1/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · putput.io
claude mcp add --transport http putput-io-dev-putput-mcp 'https://putput.io/api/v1/mcp'
{
"mcpServers": {
"putput-io-dev-putput-mcp": {
"url": "https://putput.io/api/v1/mcp"
}
}
} {
"servers": {
"putput-io-dev-putput-mcp": {
"type": "http",
"url": "https://putput.io/api/v1/mcp"
}
}
} [mcp_servers.putput-io-dev-putput-mcp] url = "https://putput.io/api/v1/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"putput-io-dev-putput-mcp": {
"type": "remote",
"url": "https://putput.io/api/v1/mcp",
"enabled": true
}
}
} openclaw mcp add putput-io-dev-putput-mcp --url 'https://putput.io/api/v1/mcp' --transport streamable-http
mcp_servers:
putput-io-dev-putput-mcp:
url: "https://putput.io/api/v1/mcp" {
"McpServers": {
"putput-io-dev-putput-mcp": {
"Transport": "http",
"Url": "https://putput.io/api/v1/mcp"
}
}
} assistant mcp add putput-io-dev-putput-mcp -t streamable-http -u 'https://putput.io/api/v1/mcp'
{
"mcpServers": {
"putput-io-dev-putput-mcp": {
"type": "http",
"url": "https://putput.io/api/v1/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 26 Aug 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
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 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
- 31 Jul 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
- 30 Jul 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 Jul 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
- 26 Jul 26 0
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 22 Sept 2026 · Probed https://putput.io/api/v1/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=putput.io | CN=WE1,O=Google Trust Services,C=US | 16 Aug 2026 | 14 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 6b167a68045143ed0ef1ce1be8398bf5 |
| SANs: putput.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of putput.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| putput.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://putput.io/api/v1/mcp | Verified | 200 | |
| http (plaintext) | http://putput.io/api/v1/mcp | HTTPS enforced | 301 | https://putput.io/api/v1/mcp |
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 →
delete_file ~26
Delete an uploaded file by ID
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | File ID to delete |
No output schema declared.
No examples provided.
get_file_info ~28
Get details about a specific file
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | File ID to look up |
No output schema declared.
No examples provided.
list_files ~53
List uploaded files with optional filtering
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Pagination cursor |
| limit | number | – | Max results (default: 50, max: 200) |
| prefix | string | – | Filter by prefix |
No output schema declared.
No examples provided.
upload_file ~78
Upload a file from a URL to PutPut storage
| Name | Type | Req | Description |
|---|---|---|---|
| filename | string | – | Optional filename override |
| metadata | object | – | Optional key-value metadata |
| prefix | string | – | Optional path prefix for organization |
| url | string | yes | URL of the file to upload |
| visibility | string | – | File visibility (default: public) |
No output schema declared.
No examples provided.
What is the io.github.putput-io-dev/putput-mcp server?
io.github.putput-io-dev/putput-mcp is listed in the public MCP registry as io.github.putput-io-dev/putput-mcp. File uploads for AI agents. Upload, list, and manage files. No signup required. This page covers its hosted endpoint (https://putput.io/api/v1/mcp).
Is the io.github.putput-io-dev/putput-mcp server safe to use?
io.github.putput-io-dev/putput-mcp scores 83 out of 100 on VerifyMCP. 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.putput-io-dev/putput-mcp server expose?
io.github.putput-io-dev/putput-mcp exposes 4 tools: upload_file, list_files, delete_file, get_file_info. Their descriptions and schemas cost roughly 185 tokens of context every time the server is loaded.
Does the io.github.putput-io-dev/putput-mcp server require authentication?
Yes. io.github.putput-io-dev/putput-mcp asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the io.github.putput-io-dev/putput-mcp server still maintained?
io.github.putput-io-dev/putput-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.