Skip to main content
Glama

Related Servers

Alternatives to forge-test-mcp

  • A
    license
    A
    quality
    B
    maintenance
    Lints and autofixes Solidity smart contracts with Solhint, from any MCP client. Exposes lint_solidity, lint_file, lint_project, fix_solidity, fix_file, explain_rule and get_config, running Solhint through its JavaScript API against the project's own config and installed version.
    7
    995 npm
    1
    MIT

Related Servers

  • A
    license
    A
    quality
    B
    maintenance
    Enables AI agents to run, debug, and inspect Playwright end-to-end tests, returning structured pass/fail stats, failure diagnostics with actionable fix hints, live DOM inspection, selector validation, visual diffs, and flakiness verdicts instead of raw test output.
    11
    MIT
  • A
    license
    A
    quality
    B
    maintenance
    Enables AI agents to run a project's pytest, unittest, jest, or vitest suites and get back compact structured results with trimmed tracebacks, collection errors kept apart from real failures, and the slowest tests. Agents can then re-run just the failures, expand one failure with local variables, repeatedly execute a single test to judge flakiness, and inspect Python coverage gaps, all under a hard timeout that kills the whole process tree.
    7
    MIT
  • A
    license
    A
    quality
    C
    maintenance
    Enables AI coding agents to discover installed host compilers, execute builds in isolated child environments with timeout enforcement, and convert noisy ANSI-laden compiler logs from Python, Rust, C/C++, Node, and Go toolchains into clean structured JSON diagnostics. It also reports toolchain readiness so agents can avoid blind invocations of missing compilers.
    4
    MIT
  • A
    license
    A
    quality
    D
    maintenance
    Provides structured, sandboxed test and lint feedback for coding agents, returning compact typed verdicts with failure fingerprints instead of raw runner output. It enables impact-selected test execution in isolated containers, distinguishing pre-existing failures from regressions.
    4
    Apache 2.0
  • A
    license
    A
    quality
    C
    maintenance
    Gives AI assistants structured access to a test automation stack so they can run suites, inspect failure details and captured output, look up test data, and file Jira bugs (or drafts) only for confirmed defects. It works with any framework that emits JUnit XML, letting assistants triage flaky, environment, and test-data issues alongside real product defects.
    6
    MIT

TDQS

A4.1/5.0

Scored across 3 tools

Disambiguation5/5

run_tests, explain_failure, and build have clearly distinct purposes: one runs the suite, one drills into a single failure at high verbosity, one compiles. An agent can easily route each request.

Naming Consistency4/5

run_tests and explain_failure follow verb_noun, while build is a bare verb. Minor deviation but still readable and predictable.

Tool Count4/5

Three tools is slightly thin but each earns its place covering the core workflow of build, run, and diagnose. Well-scoped for a focused Foundry testing server.

Completeness4/5

The build-run-explain lifecycle is fully covered, including structured compiler output and fuzz/invariant counterexamples. Minor gaps like listing tests or coverage exist but core workflows are complete.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues