Developer · Remote MCP server

Repowise (Hosted)

Hosted codebase intelligence for repos indexed on repowise.dev - no local indexing needed.

Visit Repowise (Hosted)'s website

What the MCP Registry states

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

Registry name
dev.repowise/repowise-hosted
Version
0.17.1
Status
Active
Category
developer
Transport
Streamable HTTP
Published
2026-06-07
Updated
2026-06-07
Publisher
dev.repowise · 2 servers with pages here
Namespace
Namespace verified by the MCP Registry via the domain repowise.dev · how
Website
www.repowise.dev
Source
Registry API entry

Remote endpoints

TransportURLHeaders declared
Streamable HTTPhttps://api.repowise.dev/mcp/{owner}/{repo}Authorization (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.

Checked
Not requested: URL template placeholder
Checked on
2026-10-05

How the live check works

How to connect Repowise (Hosted)

Repowise (Hosted) is a remote MCP server: there is nothing to install. Its endpoint is https://api.repowise.dev/mcp/{owner}/{repo}, 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 URL contains placeholders to fill in before connecting: {owner} and {repo}.

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, not tested here. 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 from dev.repowise

All 2 →
ServerRunsEndpoint or package
RepowiseCodebase intelligence for AI coding agents - graph, git history, docs, decisions, code health.Local · stdioPyPI: repowise

More developer servers

All 5,152 →
ServerRunsEndpoint or package
ReposeUptime monitoring that doesn't cry wolf: manage monitors, read incidents, record deploys.Remote · HTTPLive check: sign-in requiredrepose.sh
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
REPSLogLog and read REPS time logs, properties, and categories via MCP. Requires REPSLog Premium.Remote · HTTPLive check: sign-in requiredapi.reps-log.com
ReqistryDiscover, compare, and monitor 1,400+ APIs directly from your AI coding agent.Remote · HTTPLive check: ✓ handshakemcp.reqistry.dev
Research Repo DoctorDeterministic Artifact Evaluation preflight and run-path grader for research repositories.Local · stdioPyPI: rrdoctor
Resharper Cli MCPReSharper CLI inspection/cleanup via MCP. Unofficial: not affiliated with or endorsed by JetBrains.Local · stdioNuGet: Zphil.ReSharperCli