Httpstatus
com.httpstatusPublished by httpstatus.comOfficial publisherv0.1.0Updated Oct 25, 2026
AI-callable tools for API mocking, testing, monitoring, security, and automation.
Overview
A remote MCP server from Httpstatus that gives AI assistants callable tools for API mocking, testing, monitoring, security and automation.
- What you can do
- Provides AI-callable tools covering API mocking and testing, so an assistant can work with simulated or test API endpoints through the service. Also covers monitoring and security tooling, plus automation tasks, according to the provider's description. The manifest lists no individual tools, so the exact operations and their inputs are not documented here.
- When to use it
- Worth considering when you want an assistant to help with API mocking, testing, monitoring or automation tasks through a hosted service rather than local tooling. Check the provider's own documentation first, since the specific tools are not described in this listing.
- Requirements
- A remote endpoint at mcp.httpstatus.com over streamable HTTP; no local package or runtime is needed. Authentication is required and uses OAuth, so you need an account with the provider and must complete an OAuth sign-in. No environment variables or headers are declared.
Installation
In SourceWeft
- Open Httpstatus in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/com.httpstatus%2Fmcp-server/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"httpstatus": {
"type": "http",
"url": "https://mcp.httpstatus.com/mcp"
}
}
}Tools
0Version history
1- v0.1.0LatestSep 16, 2026
Score
56% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
Publish an icon in the registry entry.
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.
