A
licenseNot graded
qualityD
maintenanceMCP server for AWS S3 and compatible object stores, enabling LLM clients to browse buckets and fetch objects.
MIT No Attribution
strands-hub-mcp
by labeveryday
Related Servers
Alternatives to strands-hub-mcp
No user-submitted related servers found.
Related Servers
AgentMark MCP Serverofficial
AlicenseNot gradedqualityAmaintenanceMCP server for AgentMark. Exposes the full AgentMark API to AI editors: list traces and spans, manage datasets, write scores, run experiments, manage apps, deployments, environments, and annotation queues.352AGPL 3.0
sceptre-mcp-serverofficial
AlicenseNot gradedqualityDmaintenanceMCP server that exposes Sceptre CloudFormation management operations as tools for AI agents.Apache 2.0- FlicenseNot gradedqualityCmaintenanceProvides a production-oriented MCP server exposing tools, resources, and prompts over Streamable HTTP with JWT authentication and per-tool RBAC, enabling Amazon Bedrock Claude clients to securely invoke MCP capabilities.-
- AlicenseAqualityAmaintenanceMCP server that exposes a pool of Claude SDK agents as tools, enabling deterministic agent creation, retrieval, and resumption from a capability corpus.101MIT
- FlicenseCqualityBmaintenanceMCP server that exposes the Lyzr Enterprise API as tools, resources, and prompts, allowing users to bring their own Lyzr API key to access a wide range of agent and RAG capabilities.100-
TDQS
B3.3/5.0
Scored across 17 tools
Disambiguation4/5
Most tools map to distinct resources and actions, with clear domain prefixes (registry, prompts, metrics, sessions). However, sessions_get_session_json and sessions_get_raw both fetch session data and could be confused, as could registry_get_agent vs sessions_get_agent_json despite their different contexts.
Naming Consistency4/5
Naming follows a consistent <domain>_<verb>_<object> pattern for nearly all tools, such as registry_list_agents and sessions_get_message_json. The main deviation is hub_status, which lacks a verb unlike the rest, and sessions_get_raw uses an adjective instead of a specific object.
Tool Count4/5
17 tools is slightly above the typical well-scoped range, but the count is justified by the five distinct domains and the deep session hierarchy. Each tool serves a specific retrieval task, making the count reasonable rather than bloated.
Completeness4/5
The read-focused surface is fairly complete for inspection: sessions are traversable from ID down to message content, prompts have version listing/creation, and metrics are accessible. Minor gaps include no delete/create in the registry and no write operations for sessions, but these may be intentionally outside the server's scope.
Maintenance
ActivityInactive
ResponsivenessNo issues