MCP.Market

Repowise (Hosted) MCP server

online · 100% uptime
by repowise.dev·dev.repowise/repowise-hosted·v1.0.0·8.1k stars

Ask how your codebase works. Hosted codebase intelligence for repos indexed on repowise.dev.

A97/100grade A
What users say
No reviews yet
Be the first
Safety scan
A97/100

full report

Adoption
Established

8.1k stars

Reviews

Write one

Nobody has reviewed Repowise (Hosted) yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Repowise (Hosted) tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Public scan report

scanner v0.1.10 · 2026-11-10 · same rubric, same numbers if you re-run it

no findings
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 267ms (auth required)20/20
  • –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
  • Auth qualityOAuth resource metadata advertised on 40115/15
  • Maintenancelast push 0 days ago15/15
  • Maintainer identityendpoint served from the registry-verified namespace domain8/10
Overall 97/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Repowise (Hosted) compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
97/100
higher than 98% of 48,114 servers
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
1,006 ms
faster than 9% of 30,044 servers
GitHub stars
8,099
more than 95% of 28,851 servers

Release history: 2 versions in the registry since 2026-06-07, latest 2026-11-05, typically one every 151 days.

Install Repowise (Hosted) in Claude Code, Cursor or VS Code

claude mcp add --transport http repowise-hosted https://api.repowise.dev/mcp
Add to Cursor

What the publisher says

From the Repowise (Hosted) repository's README, as published. We do not edit it. Read it on GitHub

<!-- mcp-name: dev.repowise/repowise -->

English | 简体中文

Stop paying your agent to re-read your codebase.

Repowise indexes your code, git history, tests and decisions once, on your machine. Your coding agent asks the index instead of grepping and opening files, so it does about half the work. You get the same answers in a dashboard: what calls this, what breaks, what to fix first, and why.

Half the tool callsyour agent opens 3 files where it opened 7 · 31.6% less output Up to 99% less noisefrom test runs, installs and git output · every error line kept 88% of the right filesfound in one call · next best tool: 61%

Graph, risk, health, tests and dead code make zero LLM calls · no API key to index · 28 languages · Claude Code, Codex, Cursor and any MCP host · free and open source

Quickstart · For your agent · What it does · Hosted · Benchmarks · Teams · Docs

Set it up in one line

Open Claude Code, Codex, Cursor or any MCP-capable agent in your repository and paste:

Read https://docs.repowise.dev/setup.md and set up Repowise in this repository.

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Grade history

  • 2026-11-10restoreB → Ascore 97

Repowise (Hosted): common questions

Is Repowise (Hosted) MCP server safe?
Yes, by our scan: it is graded A (97/100). Read the Repowise (Hosted) safety report
How do I install Repowise (Hosted)?
It runs remotely at api.repowise.dev. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Repowise (Hosted) need an API key?
No key to paste: it signs you in with OAuth when your client connects.
Is Repowise (Hosted) maintained?
The last commit was 6 days ago (2026-11-09). The latest release is v1.0.0.
Is Repowise (Hosted) up?
100% of our last 27 checks got an answer. We check remote servers about four times a day.
How does Repowise (Hosted) compare with other MCP servers?
safety score 97/100 (higher than 98% of 48,114 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 1,006 ms (faster than 9% of 30,044 servers). Full comparison.