Code Refactor
REMOTE · CODE-REFACTOR-API.APP.WORKBUDDY.HOST · 2 COMPONENTS
Refactor legacy code into modern, idiomatic code without changing its behavior.
Last scanned (2 hours ago)
Scores higher than 58% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Developer Tools
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 2378 tokens (~132/item across 18 items; 18 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability check failed: schema churn in the 17 days we've observed: 2 tool removals, 0 breaking changes, 0 auth/transport breaks, 18 additions. See how to fix → Fail
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 18 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 19 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 0
- Stability: unverified → fail ▼ security
- Authorization: unverified → fail ▼ security
- Injection markers: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: unreachable → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- 4 Nov 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Stability: fail → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: fail → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 30 Oct 26 +10
- Authorization: unverified → fail ▼ security
- 29 Oct 26 −10
- Authorization: fail → unverified ▼ security
- 25 Oct 26 +10
- Transport: fail → pass ▲ security
- Schema quality: 1648 → 2378 ▼ functional
- New tool “codetrans” functional
- New tool “regexgen” functional
- New tool “errfix” functional
- New tool “codeexplain” functional
- New tool “commitmsg” functional
- 24 Oct 26 −10
- Transport: pass → fail ▼ security
- 23 Oct 26 +49
- Stability: unverified → fail ▼ security
- Authorization: unverified → fail ▼ security
- A breaking change shipped without a version bump: still 1.0.0 ▼ security
- Tool “check_status” was removed ▼ security
- Tool “refactor_code” was removed ▼ security
- Injection markers: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- The server rewrote its instructions, which are the text every model session reads security
- The server changed its declared name: code-refactor → skillgateway security
- MCP protocol: unverified → fail ▼ functional
- Schema quality: pass → fail ▼ functional
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- New tool “codegen” functional
- New tool “contract” functional
- New tool “copywriter” functional
- New tool “docgen” functional
- New tool “get_order” functional
- New tool “list_orders” functional
- New tool “resume” functional
- New tool “review” functional
- New tool “script” functional
- New tool “skill_info” functional
- New tool “sqlgen” functional
- New tool “testgen” functional
- New tool “translate” functional
- 22 Oct 26 −41
- Endpoint reachability: reachable → not serving MCP ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: 0.07 → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://code-refactor-api.app.workbuddy.host/mcp
TLS valid
Negotiated TLS 1.2 with TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.workbuddy.host,O=Tencent Technology (Shenzhen) Company Limited,L=Shenzhen,ST=Guangdong Province,C=CN | CN=DigiCert Secure Site OV G2 TLS CN RSA4096 SHA256 2022 CA1,O=DigiCert\, Inc.,C=US | 10 Sept 2026 | 27 Mar 2027 | RSA 2048 | SHA256-RSA | 42d0278b23e5092a1c8540bc7c33f21 |
| SANs: *.workbuddy.host, workbuddy.host, *.app-staging.workbuddy.host, *.app-tencent.workbuddy.host, *.app.workbuddy.host, *.apps-staging.workbuddy.host, *.apps.workbuddy.host | ||||||
| CN=DigiCert Secure Site OV G2 TLS CN RSA4096 SHA256 2022 CA1,O=DigiCert\, Inc.,C=US (CA) | CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US | 15 Dec 2022 | 14 Dec 2032 | RSA 4096 | SHA256-RSA | 4c1b960191fcabedcda9301a6cd78c3 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of code-refactor-api.app.workbuddy.host. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| host. | present | 29155 | 13 | Verified |
| workbuddy.host. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer
BearerProtected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://code-refactor-api.app.workbuddy.host/mcp | Verified | 200 | |
| http (plaintext) | http://code-refactor-api.app.workbuddy.host/mcp | HTTPS enforced | 302 | HTTPS://code-refactor-api.app.workbuddy.host/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
codeexplain 代码逐行讲解（按次计费） ~147
按读者水平（零基础→资深）拆解代码逻辑、关键点与坑。按次计费：业务成功才确认扣款，内容违规、模型超时或生成失败会自动全额退款。
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | 要讲解的代码，最多 20000 字符。 |
| language | string | – | 代码语言，不填自动判断。 |
| level | string | – | 读者水平：beginner=零基础 / intermediate=中等 / expert=资深。 |
| requestId | string | – | 幂等键。同一次业务重试时复用同一个值，可避免重复扣费。 |
No output schema declared.
No examples provided.
codegen AI 代码生成（按次计费） ~128
根据需求描述生成可运行的示例代码。按次计费：业务成功才确认扣款，内容违规、模型超时或生成失败会自动全额退款。
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | – | 目标编程语言。 |
| prompt | string | yes | 代码需求描述，最多 4000 字。 |
| requestId | string | – | 幂等键。同一次业务重试时复用同一个值，可避免重复扣费。 |
| style | string | – | 可选风格要求，如「函数式」「兼容 Python 3.8」。 |
No output schema declared.
No examples provided.
codetrans 代码语言迁移（按次计费） ~131
A 语言 → B 语言等价实现 + 依赖替换与行为差异清单。按次计费：业务成功才确认扣款，内容违规、模型超时或生成失败会自动全额退款。
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | 要迁移的源代码，最多 20000 字符。 |
| from | string | – | 源语言，不填自动判断。 |
| requestId | string | – | 幂等键。同一次业务重试时复用同一个值，可避免重复扣费。 |
| to | string | yes | 目标语言。 |
No output schema declared.
No examples provided.
commitmsg Git 提交信息生成（按次计费） ~148
粘贴 diff → Conventional Commits 中英双语提交信息 + 风险提示。按次计费：业务成功才确认扣款，内容违规、模型超时或生成失败会自动全额退款。
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | – | 可选：变更背景（需求单/bug 单号等）。 |
| diff | string | yes | git diff 或变更描述，最多 12000 字符。 |
| requestId | string | – | 幂等键。同一次业务重试时复用同一个值，可避免重复扣费。 |
| style | string | – | conventional=规范提交 / plain=简洁一句话 / detailed=详细变更说明。 |
No output schema declared.
No examples provided.
contract 合同条款风险审查（按次计费） ~122
标出高/中风险条款与缺失条款，并给出可替换表述。按次计费：业务成功才确认扣款，内容违规、模型超时或生成失败会自动全额退款。
| Name | Type | Req | Description |
|---|---|---|---|
| party | string | – | 审查立场：站在哪一方看这份合同。 |
| requestId | string | – | 幂等键。同一次业务重试时复用同一个值，可避免重复扣费。 |
| text | string | yes | 合同文本，最多 20000 字符。 |
No output schema declared.
No examples provided.
copywriter 爆款文案生成（按次计费） ~133
小红书/抖音/公众号等多平台文案，一次给 3 个版本。按次计费：业务成功才确认扣款，内容违规、模型超时或生成失败会自动全额退款。
| Name | Type | Req | Description |
|---|---|---|---|
| brief | string | yes | 产品/内容描述，写清卖点、人群、场景，最多 2000 字。 |
| platform | string | – | 目标平台。 |
| requestId | string | – | 幂等键。同一次业务重试时复用同一个值，可避免重复扣费。 |
| tone | string | – | 文案调性。 |
No output schema declared.
No examples provided.
docgen 技术文档生成（按次计费） ~164
README / API 文档 / 变更日志 / 技术方案一键生成。按次计费：业务成功才确认扣款，内容违规、模型超时或生成失败会自动全额退款。
| Name | Type | Req | Description |
|---|---|---|---|
| audience | string | – | developer=开发者 / pm=产品 / ops=运维 / enduser=最终用户。 |
| docType | string | – | readme=项目说明 / api=接口文档 / changelog=变更日志 / design=技术方案 / onboarding=上手指南。 |
| requestId | string | – | 幂等键。同一次业务重试时复用同一个值，可避免重复扣费。 |
| source | string | yes | 代码或接口说明素材，最多 20000 字符。 |
No output schema declared.
No examples provided.
errfix 报错诊断与修复（按次计费） ~154
报错栈 + 代码 → 根因定位 + 最小修复补丁 + 验证步骤。按次计费：业务成功才确认扣款，内容违规、模型超时或生成失败会自动全额退款。
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | – | 可选：相关代码，给了能定位更准。 |
| context | string | – | 可选：运行环境（Node 版本 / OS / 框架版本等）。 |
| error | string | yes | 报错信息 / 堆栈，最多 6000 字符。 |
| requestId | string | – | 幂等键。同一次业务重试时复用同一个值，可避免重复扣费。 |
No output schema declared.
No examples provided.
get_order 查询订单 ~47
按订单号查询一笔调用的状态、金额、耗时与失败原因。不收费。
| Name | Type | Req | Description |
|---|---|---|---|
| orderNo | string | yes | 订单号，形如 SG20261018… |
No output schema declared.
No examples provided.
list_orders 订单列表 ~92
列出最近的调用订单，可按状态或平台过滤，用于对账。不收费。
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | 返回条数，默认 20，最大 100 |
| platform | string | – | 按来源平台过滤，如 coze、dify、gpts |
| status | string | – | 按状态过滤：created / preauthorized / succeeded / failed / refunding / refunded |
No output schema declared.
No examples provided.
regexgen 正则表达式生成（按次计费） ~150
自然语言 → 精确正则 + 逐段解释 + 匹配示例，防灾难性回溯。按次计费：业务成功才确认扣款，内容违规、模型超时或生成失败会自动全额退款。
| Name | Type | Req | Description |
|---|---|---|---|
| flavor | string | – | 正则方言。 |
| requestId | string | – | 幂等键。同一次业务重试时复用同一个值，可避免重复扣费。 |
| requirement | string | yes | 匹配需求，用自然语言描述，如「匹配中国大陆手机号」。 |
| sample | string | – | 可选：待匹配的示例文本，给得越准结果越准。 |
No output schema declared.
No examples provided.
resume 简历优化与岗位匹配（按次计费） ~150
按 JD 诊断匹配度并用 STAR 结构重写（绝不虚构经历）。按次计费：业务成功才确认扣款，内容违规、模型超时或生成失败会自动全额退款。
| Name | Type | Req | Description |
|---|---|---|---|
| goal | string | – | optimize=整体优化 / match=匹配度诊断 / rewrite=按 JD 重写。 |
| jd | string | – | 目标岗位 JD（goal 为 match/rewrite 时必填）。 |
| requestId | string | – | 幂等键。同一次业务重试时复用同一个值，可避免重复扣费。 |
| resume | string | yes | 原始简历全文，最多 12000 字符。 |
No output schema declared.
No examples provided.
review AI 代码审查（按次计费） ~126
审查代码并给出分级的修改建议。按次计费：业务成功才确认扣款，内容违规、模型超时或生成失败会自动全额退款。
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | 待审查的代码原文，最多 20000 字符。 |
| focus | string | – | 审查重点，默认全部。 |
| language | string | – | 代码语言，不填则自动判断。 |
| requestId | string | – | 幂等键。同一次业务重试时复用同一个值，可避免重复扣费。 |
No output schema declared.
No examples provided.
script 短视频脚本与分镜（按次计费） ~134
开头钩子 3 版 + 分镜表 + 口播文案，可直接拍摄。按次计费：业务成功才确认扣款，内容违规、模型超时或生成失败会自动全额退款。
| Name | Type | Req | Description |
|---|---|---|---|
| duration | string | – | 目标时长。 |
| platform | string | – | 发布平台，决定节奏与时长习惯。 |
| requestId | string | – | 幂等键。同一次业务重试时复用同一个值，可避免重复扣费。 |
| topic | string | yes | 视频主题或产品卖点，最多 1500 字。 |
No output schema declared.
No examples provided.
skill_info 技能与定价信息 ~29
返回当前技能是否上架、单次价格、支持的编程语言与免责声明。不收费。
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
sqlgen SQL 生成与优化（按次计费） ~139
按表结构生成/优化 SQL，自动拦截破坏性语句。按次计费：业务成功才确认扣款，内容违规、模型超时或生成失败会自动全额退款。
| Name | Type | Req | Description |
|---|---|---|---|
| dialect | string | – | 数据库类型。 |
| question | string | yes | 查询需求，例如「统计最近 7 天每日新增用户数」。 |
| requestId | string | – | 幂等键。同一次业务重试时复用同一个值，可避免重复扣费。 |
| schema | string | – | 相关表结构（CREATE TABLE 或字段说明），给得越准 SQL 越准。 |
No output schema declared.
No examples provided.
testgen 单元测试生成（按次计费） ~194
为核心代码生成可运行的单元测试（自动 mock 外部依赖）。按次计费：业务成功才确认扣款，内容违规、模型超时或生成失败会自动全额退款。
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | 被测代码，最多 20000 字符。 |
| framework | string | – | 测试框架，按语言可选：python=[pytest|unittest]，javascript=[jest|vitest|mocha]，typescript=[jest|vitest]，java=[junit5|testng]，go=[gotest]，rust=[cargo-test]，csharp=[xunit|nunit]，php=[phpunit] |
| language | string | – | 代码语言，不填则自动判断。 |
| requestId | string | – | 幂等键。同一次业务重试时复用同一个值，可避免重复扣费。 |
No output schema declared.
No examples provided.
translate 翻译与母语级润色（按次计费） ~140
10 种语言，直译+润色+术语表三档输出。按次计费：业务成功才确认扣款，内容违规、模型超时或生成失败会自动全额退款。
| Name | Type | Req | Description |
|---|---|---|---|
| requestId | string | – | 幂等键。同一次业务重试时复用同一个值，可避免重复扣费。 |
| style | string | – | literal 忠实直译 / polished 母语润色 / seo 关键词布局 / academic 学术正式。 |
| target | string | yes | 目标语言。 |
| text | string | yes | 待翻译内容，最多 8000 字符。 |
No output schema declared.
No examples provided.
How do I install the Code Refactor MCP server?
Code Refactor is a hosted endpoint at https://code-refactor-api.app.workbuddy.host/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · code-refactor-api.app.workbuddy.host
claude mcp add --transport http zhouhengchang-code-refactor 'https://code-refactor-api.app.workbuddy.host/mcp'
What is the Code Refactor MCP server?
Code Refactor is an MCP server listed in the public MCP registry as io.github.zhouhengchang/code-refactor. Refactor legacy code into modern, idiomatic code without changing its behavior. This page covers its hosted endpoint (https://code-refactor-api.app.workbuddy.host/mcp).
Is the Code Refactor MCP server safe to use?
Code Refactor scores 72 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Code Refactor MCP server expose?
Code Refactor exposes 18 tools: codegen, review, copywriter, translate, sqlgen, and 13 more. Their descriptions and schemas cost roughly 2,328 tokens of context every time the server is loaded.
Does the Code Refactor MCP server require authentication?
Yes. Code Refactor asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Code Refactor MCP server still maintained?
Code Refactor is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.