Repose

io.github.vncntknlPublished by GitHub account vncntknlv0.1.0Updated Oct 24, 2026

Uptime monitoring that doesn't cry wolf: manage monitors, read incidents, record deploys.

VerifiedStreamable HTTPWeb executableSecurity & Monitoring

Overview

AI-generated overview

Repose is a remote uptime-monitoring MCP server that lets an assistant manage monitors, read incidents and record deploys.

What you can do
Manage uptime monitors, including creating and updating them with a read-write token. Read incidents and acknowledge them. Record deploys against the monitoring setup. Read-only access is available with a read token.
When to use it
Useful when you want an assistant to check on site uptime and incidents, or to log deploys and acknowledge alerts as part of a release or on-call workflow.
Requirements
Remote endpoint at repose.sh over streamable HTTP with OAuth. An Authorization header carrying a Repose API token (Bearer rsk_…) created under Settings → API tokens. A read-write token requires the Team plan or higher.
Before you install
The Authorization header holds a secret API token; keep it private. A read-write token lets the assistant create and update monitors, acknowledge incidents and record deploys, which changes monitoring state. Use a read-only token when only inspection is needed.

Installation

In SourceWeft

  1. Open Repose 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/io.github.vncntknl%2Frepose/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": {
    "repose": {
      "type": "http",
      "url": "https://repose.sh/api/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. v0.1.0LatestSep 19, 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.