Fastio vs Google Cloud Storage

Fastio 32

fast.io, docs.fast.io, api.fast.io and mcp.fast.io weren't re-read on 4 November, because the terms of 2 October 2026 bar any robot from any portion of the Services, website included, outside the API and MCP access of Section 12. Per the 9 October check, no status page or incident history was found on fast.io, the docs or the Trust Centre (0 + 5 for no readable history). Rate limits are exposed in x-ve-limit-avail, x-ve-limit-max and x-ve-limit-expires headers, with no published numbers (5). 429 handling is documented with Retry-After, backoff, a retryable 503 and if_version_id compare-and-swap on uploads. Idempotency keys exist only on bug reports, not on file, share or workspace writes, so this is safe-retry guidance without idempotency keys on the product's writes (12, corrected on 4 November from 13, which isn't a value the line allows). No SLA, and Section 12 of the terms, re-read on 4 November, still gives no guarantee of API availability (0). The API and MCP server are sold as generally available (10). An earlier reading of the API's own status endpoint is struck, since it came from a request to the product.

Google Cloud Storage 80

Google Cloud's status dashboard with a per-product incident feed (20). In the 90 days from 8 August, Cloud Storage appears in a high-severity incident on 20 August across 27 products (about 3 hours 40 minutes of timeouts and errors), a medium incident on 8 to 9 October with elevated upload and write errors, and a medium regional incident in europe-west2 on 20 October. One major outage (10). The request-rate guide gives numbers, no ramp-up needed below 1,000 writes or 5,000 reads a second per bucket, with gradual ramping above (15). The retry strategy page lists retryable responses, idempotent operations and preconditions that make writes safe to retry, and the client libraries back off exponentially (15). SLA with monthly uptime of 99.95 per cent for multi-region Standard and 99.9 per cent regional (10). Generally available, and the MCP server since 20 April 2026 (10). 20 + 10 + 15 + 15 + 10 + 10 = 80.

Fastio 64

Closed service under clear terms dated 2 October 2026, re-read on 4 November and unchanged in date. The CLI is Apache-2.0 (18). Per the 9 October check, not re-read on 4 November, a privacy policy, a published DPA and a deletion policy with matching periods of 15, 30, 60 and 90 days, and a no-training statement. The DPA binds only once signed (26). Deprecations are flagged in the docs (Basic sign-in, QuickShare, 410 Gone for retired paths) without dates, and the terms disclaim backward compatibility (6). Sub-processor list with purposes and locations, and 15 days' notice of additions (20).

Google Cloud Storage 85

Closed service under the Google Cloud terms; client libraries are Apache-2.0 (18). Google's privacy policy, the Cloud Data Processing Addendum and a sub-processor list last modified 19 October 2026 apply, per the Secret Manager listing's 1 November check (22). Dated notices in release notes and a deprecated read_text MCP tool that names its replacement; Google Cloud's deprecation policy wasn't re-read today (15). Sub-processors are listed with locations, and each bucket is created in a chosen location (18). 18 + 22 + 15 + 18 = 73.

Fastio 70

CLI v0.2.98 on 29 October 2026 adds comment threads, suggestions and export (30). v0.2.99 on 2 November only updates dependencies, so it can't set recency. 18 CLI tags between 1 September and 2 November 2026, all inside the 90 days from 6 August, most of them changing code (20). No changelog in the CLI repository, and fast.io wasn't re-read. Support runs through a contact page, Discord and a bug-report endpoint, and the CLI repository had no open issues and one star, per the 9 October check (7). The official CLI is current, there are no SDKs, and a search of the MCP registry for fastio and fast.io returned nothing, per the 9 October check (5). CI runs check, format, clippy, the test suite and a release build, and Cargo.lock is committed and was updated on 2 November (8).

Google Cloud Storage 88

Release notes on 4 November 2026 (30). Entries on 30 October, 13 October, 30 September, 10 September and 3 September (20). A closed service with dated release notes and paid support; issue trackers for the client libraries are public (15). Official client libraries in many languages (15). Libraries ship with end-to-end checksums by default since 30 September (8). 30 + 20 + 15 + 15 + 8 = 88.

Fastio 65

Per the 9 October check, not re-read on 4 November (terms ban on robots). No OpenAPI file. OPTIONS introspection returns parameter types and constraints on about 40 per cent of endpoints, and MCP tools answer action="describe". The hosted tool definitions were not read, because mcp.fast.io's robots.txt disallows /mcp (10). llms.txt on fast.io and api.fast.io, a Markdown twin for each reference section, agents.md and skill.md (10). Descriptions say when to use each tool and name the traps (17). Constraint tables and enums are documented, but MCP inputs route through one action parameter (9). Request and response examples and per-endpoint error tables (13). The API is version 1.0 under /current/, guides carry version numbers and dates, and no changelog was found, in the docs then or in the CLI repository on 4 November (6).

Google Cloud Storage 81

The JSON API is described by a public Google API Discovery document, storage v1 revision 20261103 (25). docs.cloud.google.com/llms.txt and /storage/llms.txt return 404 (0). The reference explains each method and the docs say when to use XML, JSON or gRPC and that gsutil is legacy (14). Typed resources with enums for storage classes and predefined ACLs (14). Samples in every client library and an error reference with HTTP codes and reasons (13). API version v1 and dated release notes, the latest on 4 November 2026 (15). 25 + 0 + 14 + 14 + 13 + 15 = 81.

Fastio 73

Per the 9 October check, not re-read on 4 November (terms ban on robots). 35 hosted tools in named mode, 39 with import and signing (5). Added back 10 for the 8-tool code mode, read-only sessions that list no write tools and the CLI's --tools filter (15). Offset and cursor pagination, page_size of 100 to 500, filters and output=terse or markdown (20). Errors carry an HTTP status, a code, per-parameter messages and a recovery hint (18). The docs say every hosted tool sets readOnlyHint, destructiveHint and idempotentHint, and uploads accept if_version_id. No general idempotency key (14). No SDK in any language, only the CLI, and workspace creation needs four required fields with literal permission strings (6). The CLI's own stdio server, read from its source at v0.2.99 on 4 November, lists 26 action-routed tools (import only when cloud import is on) and sets no annotations.

Google Cloud Storage 85

Graded as an API with a nine-tool MCP server. The fields parameter selects partial responses, and Range reads fetch part of an object (22). maxResults and pageToken paging, prefix and delimiter filters and match globs (20). JSON errors with code, message and reason, and a documented retry table (16). Generation and metageneration preconditions make retries safe; the MCP reference gives no read-only or destructive annotations (14). Client libraries in many languages with retries on by default, but every call needs Google auth and a project (13). 22 + 20 + 16 + 14 + 13 = 85.

Fastio 77

OAuth 2.0 with PKCE (S256), dynamic client registration and consent to scopes, or revocable API keys scoped by entity and access mode with optional expiry, per the 9 October check (30). Read-only scopes, read and write tools kept apart, and confirm='true' on irreversible actions (18). Stored files are untrusted content. The docs flag intent text as untrusted and say AI works within the caller's permissions, with no wider guidance (6). An activity log on every plan, kept 30 to 365 days, with an actor on each record. CSV export and SIEM streaming are Enterprise only (13). security@fast.io and the CLI's SECURITY.md, which promises acknowledgement within 48 hours and a fix within 7 days for critical issues, plus Google CASA Assurance Level 1 per the 9 October Trust Centre reading. No SOC 2 report, no bug bounty and no security.txt (10, corrected from 7, since SECURITY.md has stated the 48-hour acknowledgement since 1 September 2026).

Google Cloud Storage 85

IAM roles on project, bucket and managed folder, V4 signed URLs, and an IAM permission per MCP method (mcp.tools.call plus the storage permission, such as storage.objects.delete for delete_object) (30). Read-only roles such as Storage Object Viewer, grantable down to a managed folder, soft delete with a pausable hard-deletion window and retention locks, but no confirmation step on delete_bucket or delete_object (17). read_object returns stored content to the model with no untrusted-content guidance on the MCP page (5). Cloud Audit Logs with Admin Activity and Data Access entries (15). google.com security.txt is valid to 2030-04-01 with a VRP policy link, per the Secret Manager listing's 1 November check, and Google Cloud publishes security bulletins; Cloud Storage's place in the SOC 2 scope wasn't read today (18). 30 + 17 + 5 + 15 + 18 = 85.