AxoWatch

com.axowatchPublished by axowatch.comOfficial publisherv1.0.0Updated Oct 24, 2026

Uptime, page speed, app errors and user-flow runs for your sites, plus fix tasks for coding agents.

VerifiedStreamable HTTPWeb executableDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

AxoWatch is a remote MCP server that gives an assistant uptime, page speed, app error and user-flow data for your sites, plus fix tasks for coding agents.

What you can do
Retrieve uptime status for monitored sites and apps, so an assistant can report whether they are up or down and summarize availability issues. Pull page speed measurements to review performance and spot slow pages. Review app errors and user-flow run results to understand failures in real user journeys. Create fix tasks for coding agents based on the issues found.
When to use it
Useful when you monitor websites or apps with AxoWatch and want an assistant to check availability, performance, errors and user-flow results, or to turn detected problems into fix tasks for coding agents.
Requirements
A remote MCP server reached at the AxoWatch endpoint over streamable HTTP. Authentication is required via OAuth, so an AxoWatch account and an OAuth sign-in flow are needed. No environment variables or headers are declared.
Before you install
Access is granted through OAuth to your AxoWatch account, so review the scopes requested during sign-in. The server can create fix tasks for coding agents, which is a write action that may change data in your account. Monitoring data about your sites and apps is sent to AxoWatch.

Installation

In SourceWeft

  1. Open AxoWatch in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. 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.axowatch%2Faxowatch/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.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "axowatch": {
      "type": "http",
      "url": "https://axowatch.com/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestOct 10, 2026

Score

67% 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
  • 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.