Cloud Services
dockage.ai
An MCP server for storing, fetching, listing, and managing files on Walrus decentralized storage, including batch storage and live on-chain receipts.
ENDPOINT 1
https://dockage.ai/mcp
MCP server metadata
- Name
- dockage
- Version
- 0.3.0
Known tools 6
quoteGet a firm, signed price quote for storing files on Walrus via dockage.ai — no payment, no commitment, no key needed.
Potential side effectslistList everything a Sui address has stored via dockage.ai, reconstructed LIVE from the chain (no server records — on-chain receipts are the database).
Inferred read-onlystoreStore a single file, paid in USDC over x402 — assumes you have an agentic wallet holding USDC on Sui.
Inferred read-onlystore_batchStore 2-500 files as ONE Walrus quilt: a single on-chain object with per-file patch IDs — far cheaper than separate stores.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.dockage]
url = "https://dockage.ai/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"dockage": {
"type": "http",
"url": "https://dockage.ai/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: dockage
Remote MCP URL: https://dockage.ai/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"dockage": {
"url": "https://dockage.ai/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"dockage": {
"type": "http",
"url": "https://dockage.ai/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "dockage",
"transport": "streamable-http",
"url": "https://dockage.ai/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.