$ loading_
Make backend API calls and package evidence proving an endpoint works.
Copy the install command and let the AI configure it · recommended for beginners
No copy-paste install info for "mcp-evidence-api" yet — see the docs or source repo.
Call this backend endpoint and package the request and response as reviewable evidence to prove it currently works: GET /health
An evidence record containing request details, call result, and response content showing the endpoint works.
Make a request to the user info endpoint and return request+response evidence so frontend and backend teams can confirm the response structure: GET /users/123
A paired request-and-response result that helps verify the endpoint response structure and status.
Request the order query endpoint and package this call as evidence to serve as proof that the endpoint works: POST /orders/query
A stored API call evidence item showing the request and its corresponding response.
Developers can call an API after implementing or changing it and keep request-response evidence to show the endpoint currently works. This also helps when checking whether the endpoint behavior matches expectations.
During frontend-backend integration, teams can generate paired request and response records as objective proof of what an API returned. This reduces ambiguity from verbal descriptions.
When you need to show that an endpoint worked successfully, this tool can create evidence records. It is useful for turning real API calls into reviewable artifacts.
It is an MCP server that makes backend API requests and packages the request and response as evidence. Its core purpose is to prove that an endpoint works.
Based on the description, it produces evidence in the form of request-and-response pairs. In other words, it turns an API call and its response into a record that shows the endpoint works.
The provided material does not include installation steps, runtime requirements, or key requirements. See the source repository for specifics.
Validate AI-generated code with browser tests, evidence capture, and smart diagnostics.
Drive Chromium with Playwright to capture verification screenshots, videos, and traces.
Assess invoices before payment with risk decisions, confidence scores, and verification.
Assess evidence behind org design and leadership claims, and suggest safer wording.
A test MCP server for validating client implementations across protocol features.
Securely proxy MCP services as OpenAPI endpoints for easier integration and deployment.