Loading ToolBench

Reading the current corpus…

DigitalOcean Spaces MCP server · B · ToolBench

← Browse

DigitalOcean Spaces

spaces.mcp.digitalocean.com/mcp

Being assessedSTREAMABLE_HTTP11 tools

70/100

Definition Quality72

Protocol Readiness88

Security75

Supportability35

Spec posture

Being assessed against 2026-07-28·last reported 2025-11-25

Live V2 assessment pending · evidence: Streamable HTTP

Being assessed

Summary

Well-curated 11-tool set focused on DigitalOcean Spaces operations (CDN and key management). Tools use typed, named parameters with clear schemas. Descriptions are adequate but sometimes terse. Security warning in spaces-key-create demonstrates awareness of sensitive operations. Minor inconsistencies in required parameter handling and pagination defaults. No evidence of auto-generation patterns.

Tools (11)

region-listsource verified80/100

List all available regions with features and droplet size availability. Supports pagination.

spaces-cdn-createsource verified77/100

Create a new CDN

spaces-cdn-deletesource verified75/100

Delete a CDN

spaces-cdn-flush-cachesource verified83/100

Flush the cache of a CDN

spaces-cdn-getsource verified75/100

Get CDN information by ID

spaces-cdn-listsource verified75/100

List CDNs with pagination

spaces-key-createsource verified89/100

Create a new Spaces key. SECURITY WARNING: The returned secret key should NEVER be added to files or committed to source control. Always store the secret key in environment variables (e.g., DO_SPACES_SECRET_KEY) and access it securely at runtime. The secret key should be treated as highly sensitive credential information and should not be displayed in logs or output when possible.

spaces-key-deletesource verified

Issues (4)

MEDIUM

Minimal descriptions for CRUD operations. Tools like spaces-cdn-delete, spaces-key-delete, spaces-cdn-get lack context on when/why to use them. Should explain preconditions, side effects, and use cases.

spaces-cdn-deletespaces-cdn-getspaces-key-deletespaces-key-get

HIGH

Inconsistent pagination parameter requirements. spaces-key-list marks Page and PerPage as required (not optional), while spaces-cdn-list and region-list have defaults and don't mark them required. This creates confusion for agent callers.

spaces-key-listspaces-cdn-listregion-list

MEDIUM

spaces-cdn-flush-cache accepts variable file list (up to 50 per request) but description doesn't explain retry/batching strategy for larger datasets. Agent may be unsure how to handle 100+ files.

spaces-cdn-flush-cache

LOW

Security warning in spaces-key-create is excellent, but only this tool has it. Similar guidance should apply to spaces-key-delete and spaces-key-update operations that modify sensitive credentials.

spaces-key-deletespaces-key-update

Recommendations

Expand descriptions for CDN and key CRUD operations to include: typical use case, preconditions (e.g., 'CDN must be in active state'), success indicators, and common errors. Target 60+ characters minimum.
Standardize pagination: make Page and PerPage optional with defaults across all list operations. Update spaces-key-list schema to match pattern of spaces-cdn-list (set required: [] with defaults).
Add guidance to spaces-cdn-flush-cache: document that agents should batch requests >50 files and explain expected cache invalidation timing (e.g., 'propagates within 60 seconds').
Extend security warnings to spaces-key-delete and spaces-key-update, emphasizing that key rotation and deletion have downstream effects on applications using those credentials.
Add example return value hints in descriptions (e.g., spaces-cdn-get: 'Returns CDN ID, origin, TTL, and current cache statistics'). This helps agents understand what data is available after invocation.

Score history

Overall score trend

First recorded score · v1 rubric

70/100

Scored	Grade	Overall	Spec posture	Rubric
2026-04-14	B	70	2025-11-25	v1