io.github.putput-io-dev/putput-mcp
REMOTE · PUTPUT.IO · 2 COMPONENTS · SCANNED AUG 3
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 →
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 Usability71
- 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 Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · putput.io
claude mcp add --transport http putput-io-dev-putput-mcp 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": {
"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.
- 2 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Jul 26 +4
- 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
- 29 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 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 65
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 3 Aug 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 | 18 Jun 2026 | 16 Sept 2026 | ECDSA 256 | ECDSA-SHA256 | a7b3c7ffea8c405c0e46fcad049f236e |
| 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 |
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 |
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.
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.