io.github.zhouhengchang/code-refactor
Code Refactor
Is the Code Refactor MCP server down? No. It is up and needs auth (HTTP 403), probed 2026-11-15.
Refactor legacy code into modern, idiomatic code without changing its behavior.
needs auth probed 2026-11-15 · HTTP 403
The server needs auth, so these tool definitions were read from the publisher's open-source package npm:workbuddy-code-refactor-connector, started in a container with placeholder values and the network off, on 2026-11-15. Tool definitions do not depend on the token, so this is what an authorized user loads, unless the server hides tools by plan or role.
Streamable HTTP error: Error POSTing to endpoint: <!doctype html> <html lang="zh-CN"> <head> <meta charset="utf-8" /> <meta name="viewport" content="width=d
- Endpoint
- https://code-refactor-api.app.workbuddy.host/mcp (streamable-http)
- Host
- code-refactor-api.app.workbuddy.host
- Of a 1M window
- <0.1 % of a 1M context window
- Getting access
- The server answers HTTP 403 with no WWW-Authenticate header and no OAuth metadata, so the publisher's documentation is the only guide.
Read from the server's public OAuth metadata, without a token. Method. - Repository
- https://github.com/zhouhengchang/code-refactor
- Website
- https://code-refactor-api.app.workbuddy.host
- Registry
- active, updated 2026-10-18 · registry entry
- Changes
- 5 recorded, reachable in 5 of them. A row is added when the result, the tool count or the cost changes.
Compare this server with others.
More servers
Servers that mention refactor.
- CleanCode AI io.github.Evozim/cleancode-ai · not found
- Yul-GasMaster io.github.Evozim/yul-gasmaster · not found
- Tentra — Memory for AI Coding Agents io.github.rdanieli/tentra · needs auth
- SoftwareForge io.github.shailesh-opsera/softwareforge · needs auth
- Python Code Reviewer org.duckdns.43-134-36-21/python-code-reviewer · timeout
- io.github.rlawogh1005/green-mcp · needs mcp<2
- SharpLens io.github.pzalutski-pixel/sharplens · crashed on start
- io.github.ryudi84/code-quality · alive
History
We add a row when the result changes. A server with no change keeps its last row.
| Probed | Result | Init | Tools | Claude | o200k |
|---|---|---|---|---|---|
| 2026-11-12 11:56 | needs auth | ||||
| 2026-10-25 21:39 | alive | 5.6 s | 18 | 5.3k | 3.3k |
| 2026-10-25 08:51 | alive | 6.0 s | 18 | 3.3k | |
| 2026-10-23 09:58 | alive | 8.0 s | 13 | 2.3k | |
| 2026-10-18 08:49 | alive | 8.9 s | 2 | 247 |
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The server answers HTTP 403 to an unauthenticated initialize, so the probe cannot list its tools. That is correct for a private server. Some public servers answer initialize and tools/list without credentials and ask for auth on tool calls only; those get a token count here.
Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.