Skip to content

Reproducibility Issues with MCPMark Benchmark #239

@H-Sompalle

Description

@H-Sompalle

Reproducibility Issues with MCPMark Benchmark

Specific Issues Encountered

  1. Notion Server: Zero reproducibility achieved
  2. GitHub Server: Fails to run properly
  3. Playwright Server: Docker image size causes practical deployment issues
  4. Repository Navigation Tasks: Difficult to reproduce consistently

Error traces suggest the benchmark primarily tests file structure navigation rather than MCP functionality

Based on error patterns, the benchmark appears to reduce to: "Can an LLM navigate file structures?" rather than testing the broader capabilities that MCP servers are designed to provide.
While sandboxing as a benchmark concept is excellent in theory, the current implementation challenges raise questions about whether it's measuring the right capabilities.

Has anyone successfully:

  • Reproduced MCPMark results with >80% success rates?
  • Created a working setup they can share?
  • Identified specific environment/configuration requirements not covered in the docs?

This issue is opened in good faith to help the community understand and properly use MCPMark. Shared reproduction steps, configurations, or insights would benefit everyone trying to benchmark their MCP implementations.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions