Skip to main content
Glama
botAGI

agmind-mcp

by botAGI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to agmind-mcp

No user-submitted related servers found.

    Related Servers

    • Local AI MCP by TMHSDigital

      Local AI MCPofficial

      TMHSDigital
      A
      license
      A
      quality
      A
      maintenance
      Unified MCP server for managing local model runtimes (Ollama, LM Studio, etc.), enabling provider-agnostic discovery, lifecycle management, hardware-fit checks, and delegated inference.
      16
      18 npm
      Creative Commons Attribution Non Commercial No Derivatives 4.0 International

    • @clawket/mcp

      clawket
      A
      license
      A
      quality
      B
      maintenance
      An MCP server that enables LLMs to pull-based search through Clawket's RAG repository for exploratory and conditional queries. It provides read-only access to search artifacts, tasks, and decisions via HTTP API.
      5
      10 npm
      MIT

    • provgraf-mcp

      Inarus
      A
      license
      A
      quality
      C
      maintenance
      Read-only MCP server exposing a W3C PROV knowledge graph of verified facts with provenance, enabling AI agents to list, search, and check facts while enforcing that writes remain CLI-only.
      5
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.5/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool serves a clearly distinct purpose: get_claim retrieves a single record by ID, list_measured provides an overview of measured combinations, and search_claims performs keyword queries. There is no overlap in functionality or potential for misselection.

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern (get_claim, list_measured, search_claims), which is predictable and easy to remember. No mixed conventions or ambiguous verbs.

    Tool Count5/5

    With 3 tools, the set is compact yet sufficient for the server's purpose of querying a claim registry. Each tool earns its place, covering retrieval, overview, and search without unnecessary bloat.

    Completeness5/5

    For a read-only registry, the surface is complete: users can search, list overall combinations, and fetch full details by ID. There are no missing lifecycle operations (create/update/delete) that would apply to this domain, so no dead ends remain.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources