Artifact Delivery Desk
Server Details
Register an artifact delivery route
- Status
- Unhealthy
- Last Tested
- Transport
- Streamable HTTP
- URL
TDQS
Scored across 1 tool
With only one tool, there is no possibility for confusion between tools.
The single tool uses a clear verb_noun pattern (record_export_route), which is consistent with common MCP naming conventions.
A single tool for an 'Artifact Delivery Desk' server is far too few to handle the typical lifecycle of deliveries, such as listing, updating, or deleting routes.
The server only supports recording export routes, missing essential operations like reading, updating, or deleting routes, resulting in severe incompleteness for its domain.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
1 tool update
- First observed
record_export_route
Related MCP Connectors
Plan the delivery route for an artifact
Register a delivery confirmation pattern
Related MCP Servers
- AlicenseAqualityAmaintenanceA local MCP-controlled artifact shelf for agents to publish generated content with stable preview URLs. Provides a shared SQLite registry and HTTP gallery for human browsing.361MIT
- FlicenseNot gradedqualityDmaintenanceEnables multi-agent systems to store large tool outputs and share only artifact IDs between agents, with access control, TTL, and audit logging.-
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to publish, retrieve, update, and delete hosted HTML, Markdown, Mermaid, and SVG artifacts and to create, list, or revoke shareable links through authenticated, scope-enforced tools. It exposes artifact hosting over Streamable HTTP so any MCP client can manage content on a self-hosted instance using a Bearer agent API key.MIT
- AlicenseNot gradedqualityAmaintenanceA local, agent-to-agent artifact exchange for LLM workflows. Enables MCP-capable tools like Claude, Codex, and Gemini to publish, list, read, update, and continue from artifacts without copying content through chat.167MIT