Developer · Remote MCP server

Repose

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

Visit Repose's website

What the MCP Registry states

The entry as published to the official MCP Registry (read 2026-10-04), latest version.

Registry name
io.github.vncntknl/repose
Version
0.1.0
Status
Active
Category
developer
Transport
Streamable HTTP
Published
2026-09-19
Updated
2026-09-19
Publisher
vncntknl (GitHub)
Namespace
Namespace verified by the MCP Registry via GitHub (github.com/vncntknl) · how
Website
repose.sh
Source
Registry API entry

Remote endpoints

TransportURLHeaders declared
Streamable HTTPhttps://repose.sh/api/mcpAuthorization (required, secret)

Live check

This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.

Reachable
Yes (HTTP 401)
Handshake
Not completed: sign-in required
Sign-in required
Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
Checked on
2026-10-05

How the live check works

How to connect Repose

Repose is a remote MCP server: there is nothing to install. Its endpoint is https://repose.sh/api/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.

The registry entry declares an HTTP header for the connection: Authorization (required, secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.

Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect

More developer servers

All 5,152 →
ServerRunsEndpoint or package
RepoPilotLocal, deterministic review of Git changes: weakened tests and CI gates, risky flows, blast radius.Local · stdionpm: repopilot
RepoRelayBounded local MCP access to one approved repository for AI read/search and structured handoffs.Local · HTTPnpm: reporelay-mcp
RepoRippleDeterministic repository change-impact analysis for engineers and coding agents.Local · stdioPyPI: reporipple
ReposcoutDiscover, enrich, and rank GitHub repos for an objective with weighted, evidence-based scoring.Local · stdionpm: @rakeshroushan/reposcout
RepotectorThe repo guardian AI agents handshake with before they touch your code.Local · stdionpm: repotector
RepovineCheckout-local repository context graph over MCP; `npx repovine setup` wires skills, agents, hooks.Local · stdionpm: repovine
RepowiseCodebase intelligence for AI coding agents - graph, git history, docs, decisions, code health.Local · stdioPyPI: repowise
Repowise (Hosted)Hosted codebase intelligence for repos indexed on repowise.dev - no local indexing needed.Remote · HTTPapi.repowise.dev