codefmt
REMOTE · CODEFMT.DEV · SCANNED SEP 20
Format/lint JS, Python, HubL for automation platforms. Tools: format_code, format_json, ask_codefmt
Available components
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 Security66
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability85
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 478 tokens (~119/item across 4 items; 3 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities73
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
- Supports UI / widget rendering.Pass
How do I install the codefmt MCP server?
codefmt is a hosted endpoint at https://codefmt.dev/api/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 · codefmt.dev
claude mcp add --transport http dev-codefmt-codefmt 'https://codefmt.dev/api/mcp'
{
"mcpServers": {
"dev-codefmt-codefmt": {
"url": "https://codefmt.dev/api/mcp"
}
}
} {
"servers": {
"dev-codefmt-codefmt": {
"type": "http",
"url": "https://codefmt.dev/api/mcp"
}
}
} [mcp_servers.dev-codefmt-codefmt] url = "https://codefmt.dev/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dev-codefmt-codefmt": {
"type": "remote",
"url": "https://codefmt.dev/api/mcp",
"enabled": true
}
}
} openclaw mcp add dev-codefmt-codefmt --url 'https://codefmt.dev/api/mcp' --transport streamable-http
mcp_servers:
dev-codefmt-codefmt:
url: "https://codefmt.dev/api/mcp" {
"McpServers": {
"dev-codefmt-codefmt": {
"Transport": "http",
"Url": "https://codefmt.dev/api/mcp"
}
}
} assistant mcp add dev-codefmt-codefmt -t streamable-http -u 'https://codefmt.dev/api/mcp'
{
"mcpServers": {
"dev-codefmt-codefmt": {
"type": "http",
"url": "https://codefmt.dev/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 17 Sept 26 +1
- Stability: 0.97 → pass security
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
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 20 Sept 2026 · Probed https://codefmt.dev/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=codefmt.dev | CN=YR1,O=Let's Encrypt,C=US | 30 Jul 2026 | 28 Oct 2026 | RSA 2048 | SHA256-RSA | 514f12093f658a74beb285f1512665d3332 |
| SANs: codefmt.dev | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of codefmt.dev. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| codefmt.dev. | present | 4588 | 13 | Verified |
| codefmt.dev. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://codefmt.dev/api/mcp | Verified | 200 | |
| http (plaintext) | http://codefmt.dev/api/mcp | HTTPS enforced | 308 | https://codefmt.dev/api/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 →
ask_codefmt Ask codefmt ~120
Ask a natural-language question about codefmt: formatting and linting JavaScript, Python, and HubL for automation platforms (Zapier, n8n, Pipedream, Make, HubSpot). Returns a grounded answer drawn from codefmt's own content with cited source URLs and a confidence score (0-1, how much of the question the answer covers, weighted toward its rarer terms); off-topic or too-weakly-matched questions are refused rather than guessed.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | The natural-language question about codefmt. |
No output schema declared.
No examples provided.
format_code Format code for automation platforms ~132
Format and lint JavaScript, Python, or HubL code for Zapier, n8n, Pipedream, Make, or HubSpot. Wraps the source in each platform's runtime shell before formatting so top-level await, bare return, and injected globals don't break the formatter. Returns formatted code plus lint diagnostics.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | Source code to format (≤50KB). |
| language | string | – | Defaults to javascript. zapier, n8n, pipedream, make, and hubspot support python; hubl does not. |
| platform | string | yes | Target automation platform. |
No output schema declared.
No examples provided.
format_json Format a JSON document ~105
Format (pretty-print or minify) a JSON document, optionally sorting object keys. Number literals are preserved exactly (64-bit IDs safe); parse errors report the exact line and column.
| Name | Type | Req | Description |
|---|---|---|---|
| indent | string | – | Indentation: '2' or '4' spaces, 'tab', or 'minify'. Defaults to '2'. |
| json | string | yes | The JSON text to format. |
| sort_keys | boolean | – | Sort object keys alphabetically. Defaults to false. |
No output schema declared.
No examples provided.
What is the codefmt MCP server?
codefmt is an MCP server listed in the public MCP registry as dev.codefmt/codefmt. Format/lint JS, Python, HubL for automation platforms. Tools: format_code, format_json, ask_codefmt. This page covers its hosted endpoint (https://codefmt.dev/api/mcp).
Is the codefmt MCP server safe to use?
codefmt scores 83 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 codefmt MCP server expose?
codefmt exposes 3 tools: format_code, ask_codefmt, format_json. Their descriptions and schemas cost roughly 357 tokens of context every time the server is loaded.
Does the codefmt MCP server require authentication?
No. We connected to codefmt without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the codefmt MCP server still maintained?
codefmt is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.