Skip to main content
Glama

Server Details

Edge content delivery for autonomous agents — signed manifests, A2A authentication

Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.

If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.

Status
Unhealthy
Uptime
0.0% over 36 days
Last Tested
Transport
Streamable HTTP
URL
Repository
srotzin/hive-mcp-cdn
GitHub Stars
0
Server Listing
hive-mcp-cdn

TDQS

A4/5.0

Scored across 3 tools

Disambiguation5/5

Each tool targets a distinct cache operation: get, put, and purge. There is no overlap in functionality, making it clear which tool to use for retrieval, storage, or deletion.

Naming Consistency5/5

All tool names follow the consistent pattern 'cdn_cache_verb' (e.g., cdn_cache_get, cdn_cache_put, cdn_cache_purge). This is a predictable and uniform naming convention.

Tool Count5/5

Three tools is well-scoped for a CDN cache server, covering the essential operations without unnecessary bloat. The count is appropriate for the domain.

Completeness4/5

The tool surface covers the basic cache lifecycle: read (get), write (put), and delete (purge). While a list/scan operation might be useful in some contexts, it is not essential for a simple cache and the tools provide a complete minimal set.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 3 tool updates
    • First observedcdn_cache_get
    • First observedcdn_cache_put
    • First observedcdn_purge

Related MCP Connectors

Related MCP Servers

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.