Skip to main content
Glama
ANAMIZED

SuperAgenticMCP

by ANAMIZED
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to SuperAgenticMCP

No user-submitted related servers found.

    Related Servers

    • Peta Core

      dunialabs
      F
      license
      Not graded
      quality
      A
      maintenance
      A production-ready MCP gateway and control plane that provides credential vault, policy engine, audit logging, and managed runtime for routing tool calls between AI agents and downstream MCP servers.
      59
      -

    • SecTrust

      nanshandongli
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP hosts to run auditable multi-agent work through a SQLite task registry, DAG orchestration, three collaboration modes (pipeline, iterative refinement, and proposal voting), human-in-the-loop approvals, an enforced sandbox, compliance scanning, and long-term memory. Exposes these capabilities as 36 tools so every consequential step stays gated behind a human checkpoint.
      AGPL 3.0

    • agentloop

      luckeyfaraday
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that enables AI agents to run a deterministic orchestration loop with decomposition, subagent execution, and review feedback across multiple LLM backends.
      60
      MIT
    Deploy Server
    Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

    TDQS

    A4.6/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a distinct role: status reports router health, list_rack shows catalog contents, rack_add and rack_remove mutate the rack, and route_task plans routing. There is no meaningful overlap or ambiguity between tools.

    Naming Consistency4/5

    Most tools follow a clear verb_noun snake_case pattern such as list_rack, rack_add, and rack_remove. The lone status tool breaks the verb_noun pattern, but it is still a simple, readable name and does not cause confusion.

    Tool Count5/5

    Five tools is well-scoped for a router/rack management server. Each tool covers a necessary operation without redundancy or unnecessary bloat.

    Completeness4/5

    The surface covers the core lifecycle: health check, catalog listing, add/upsert, remove, and routing plan generation. Minor gaps exist such as no single-server detail endpoint and route_task being a deterministic stub, but the main workflows are supported.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources