Skip to main content
Glama
labeveryday

strands-hub-mcp

by labeveryday
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to strands-hub-mcp

No user-submitted related servers found.

    Related Servers

    • s3-mcp

      EpykLab
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for AWS S3 and compatible object stores, enabling LLM clients to browse buckets and fetch objects.
      MIT No Attribution
    • AgentMark MCP Server by agentmark-ai

      AgentMark MCP Serverofficial

      agentmark-ai
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP 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.
      352
      AGPL 3.0

    • Skyhook

      upendradevsingh
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides an MCP server for Amazon S3 and S3-compatible storage, enabling authenticated uploads, versioned object management, and latest-version retrieval through MCP clients like Claude and Cursor.
      4 npm
      MIT
    Deploy Server
    Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

    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

    Resources