Skip to main content
Glama
anandapurva55

multi-source-mcp-benchmark

by anandapurva55
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to multi-source-mcp-benchmark

No user-submitted related servers found.

    Related Servers

    • TrustHarness

      ofirtro
      A
      license
      B
      quality
      C
      maintenance
      Enables deterministic security testing of AI agents that use tools by serving synthetic MCP environments with poisoned data, fake secrets, and privileged actions. Records agent tool calls and evaluates security invariants (e.g., canary leaks, forbidden access, approval binding) without an LLM judge or real systems.
      8
      MIT

    • Sandbox MCP Server

      nagaozen
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to create isolated Docker runtimes, execute commands, manage workspace files, drive a headed browser, and retrieve artifacts through eight semantic MCP tools, with progressive capability discovery and explicit sandbox lifecycle.
      Apache 2.0
    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

    A3.7/5.0

    Scored across 14 tools

    Disambiguation4/5

    Most tools target distinct operations (read vs write vs move vs search vs metadata). However, read_file is explicitly deprecated in favor of read_text_file, creating a confusing overlap, and list_directory vs list_directory_with_sizes differ only by an optional detail.

    Naming Consistency4/5

    The set is largely consistent verb_noun (read_text_file, write_file, move_file, search_files, get_file_info). Minor deviation with directory_tree, which is noun-only, and the legacy read_file naming.

    Tool Count5/5

    14 tools is well-scoped for a filesystem server, with each tool earning its place across read, write, navigate, and metadata operations.

    Completeness3/5

    Core read/write/edit/move/search/metadata are covered, but there is no delete or remove operation, a notable gap for full filesystem lifecycle coverage. No copy operation either, though move partially covers that.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources