Monitoring MCP server

Monitoring is the official remote MCP server from repuso.com. It answers at https://api.repuso.com/public/v1/mcp over streamable HTTP and asks you to sign in with your repuso.com account before it lists its tools, so your client opens a login the first time it connects. Our probes reached it 10 of 10 times since 5 September 2026; the last check, on 18 October 2026, got the sign-in challenge, so it is up.

Monitor review profiles on 50+ platforms, fetch and tag reviews, track ratings, manage webhooks.

Description as the publisher wrote it.

What Monitoring needs before it works

A sign-in. The server refused to list its tools to an anonymous client and answered with an authentication challenge, which is how an MCP server protected by OAuth behaves. Add it with one of the setups below; the first connection opens a login for your repuso.com account, and the tools appear once you have approved it.

Add Monitoring to your AI client

Every block below points at https://api.repuso.com/public/v1/mcp. Pick your client and copy.

claude mcp add --transport http monitoring https://api.repuso.com/public/v1/mcp

{
  "mcpServers": {
    "monitoring": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://api.repuso.com/public/v1/mcp"]
    }
  }
}

{
  "mcpServers": {
    "monitoring": {
      "url": "https://api.repuso.com/public/v1/mcp"
    }
  }
}

{
  "servers": {
    "monitoring": {
      "type": "http",
      "url": "https://api.repuso.com/public/v1/mcp"
    }
  }
}

{
  "context_servers": {
    "monitoring": {
      "url": "https://api.repuso.com/public/v1/mcp"
    }
  }
}

{
  "mcpServers": {
    "monitoring": {
      "serverUrl": "https://api.repuso.com/public/v1/mcp"
    }
  }
}

{
  "mcpServers": {
    "monitoring": {
      "url": "https://api.repuso.com/public/v1/mcp"
    }
  }
}

name: monitoring
version: 0.0.1
schema: v1
mcpServers:
  - name: monitoring
    type: streamable-http
    url: https://api.repuso.com/public/v1/mcp

{
  "mcpServers": {
    "monitoring": {
      "httpUrl": "https://api.repuso.com/public/v1/mcp"
    }
  }
}

{
  "mcpServers": {
    "monitoring": {
      "type": "http",
      "url": "https://api.repuso.com/public/v1/mcp"
    }
  }
}

{
  "mcpServers": {
    "monitoring": {
      "url": "https://api.repuso.com/public/v1/mcp"
    }
  }
}

goose://extension?url=https%3A%2F%2Fapi.repuso.com%2Fpublic%2Fv1%2Fmcp&type=streamable_http&id=monitoring&name=monitoring

Is Monitoring up right now?

It answered our last check on 18 October 2026 in 340 ms. Over 10 checks since 5 September 2026 it answered 10. Status here comes from Neuronto's own probes, not from the publisher.

MCP servers similar to Monitoring

Questions about Monitoring

Is there an official Monitoring MCP server?

Yes. It is published by repuso.com and served from api.repuso.com, the vendor's own domain: https://api.repuso.com/public/v1/mcp.

How do I sign in to Monitoring?

Add the server with a setup above. The first time your client connects it opens the sign-in page for repuso.com; approve it and the tools load.

Is Monitoring down?

It answered our last check on 18 October 2026 in 340 ms. Over 10 checks since 5 September 2026 it answered 10.

How do I add Monitoring to Cursor?

Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://api.repuso.com/public/v1/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.

Does Monitoring need an API key?

It needs a sign-in rather than a key you paste: the server answered with an authentication challenge, so your client runs the login when it first connects.

Where this comes from

Publisher: com.repuso. Endpoint host: api.repuso.com. ARD identifier: urn:air:com.repuso:mcp:monitoring. First indexed 31 August 2026. The tools are exactly what the server returned; nothing on this page is inferred from its name. Ranking in Neuronto search is never for sale.