Skip to main content
Glama
meovan07

mcp-evidence-api

by meovan07
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to mcp-evidence-api

No user-submitted related servers found.

    Related Servers

    • api-mcp

      Hassan-Jamal
      A
      license
      A
      quality
      C
      maintenance
      An MCP server that automatically discovers API endpoints from any codebase, generates and runs tests, and produces per-role QA audit reports in PDF and XLSX.
      10
      753 npm
      MIT

    • datalox-gated-runtime

      Oshawott324
      A
      license
      Not graded
      quality
      A
      maintenance
      This MCP server provides a stateful, resettable, verifiable API runtime that gates every tool call, enabling agents to run long workflows against provider-shaped environments without live provider write access. It records decisions, side effects, and outcome evidence for replayable, verifiable benchmark runs.
      Apache 2.0

    • postmcp

      Bencibr
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for API request automation and testing, with multi-project workspaces, environment profiles, OAuth2 support, WebSocket testing, assertions, and history auditing.
      6 npm
      5
      MIT

    • Postmancer

      hijaz
      A
      license
      Not graded
      quality
      D
      maintenance
      A standalone MCP server for API testing and management, allowing AI assistants to interact with RESTful APIs through natural language.
      10 npm
      28
      MIT

    • CyberMCP

      ricauts
      A
      license
      C
      quality
      D
      maintenance
      A Model Context Protocol server designed for testing backend APIs for security vulnerabilities like authentication bypass, injection attacks, and data leakage.
      14
      16
      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.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a distinct role: start session, make request, finish session. There is no overlap in functionality.

    Naming Consistency4/5

    Tools use snake_case with imperative verbs. 'request' is less descriptive but still follows the verb pattern; the other two follow verb_noun. Overall consistent.

    Tool Count5/5

    Three tools perfectly cover the session lifecycle: start, execute, finish. No redundancy or missing steps.

    Completeness5/5

    The toolset provides a complete workflow for recording HTTP evidence: session creation, request logging, and session finalization. No obvious gaps.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources