
Checkly Mcp
io.github.mrfentmenv1.0.0Updated Oct 1, 2026
Assertion checks for status, headers and content - no API key.
Overview
AI-generated overview
A local MCP server that lets an assistant run assertion checks on HTTP status codes, headers, and response content without an API key.
- What it does
- This server exposes assertion-style checks for HTTP responses, covering status codes, headers, and content. It runs as a local process over stdio, so the assistant can invoke these checks directly during a session. The registry description states that no API key is required.
- When to use it
- Useful when you want an assistant to verify that an endpoint returns the expected status, headers, or body content as part of a development or testing workflow. It fits lightweight, local verification rather than full browser or load testing.
- Requirements
- Runs as a local process on the user's machine, installed from the npm package checkly-mcp over stdio. Node.js is required for an npm package. No environment variables, headers, or authentication are declared.
Before you install
The registry description says no API key is needed, and no credentials are declared. The server performs HTTP requests to whatever targets it is given, so be mindful of which endpoints an assistant is pointed at. Desktop only; no web executable.
Installation
In SourceWeft
- Open Checkly Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
This repository has no README.
Tools
0Tool metadata has not been indexed yet.
Version history
1- v1.0.0LatestOct 1, 2026

