Proxylang website translation
REMOTE · PROXYLANG.DEV · SCANNED OCT 12
Translate a website into other languages from one script tag. Free trial, no signup.
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability72
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 927 tokens (~154/item across 6 items; 6 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 Management40
- Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 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
How do I install the Proxylang website translation MCP server?
Proxylang website translation is a hosted endpoint at https://proxylang.dev/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 · proxylang.dev
claude mcp add --transport http dev-proxylang-translate 'https://proxylang.dev/mcp'
{
"mcpServers": {
"dev-proxylang-translate": {
"url": "https://proxylang.dev/mcp"
}
}
} {
"servers": {
"dev-proxylang-translate": {
"type": "http",
"url": "https://proxylang.dev/mcp"
}
}
} [mcp_servers.dev-proxylang-translate] url = "https://proxylang.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dev-proxylang-translate": {
"type": "remote",
"url": "https://proxylang.dev/mcp",
"enabled": true
}
}
} openclaw mcp add dev-proxylang-translate --url 'https://proxylang.dev/mcp' --transport streamable-http
mcp_servers:
dev-proxylang-translate:
url: "https://proxylang.dev/mcp" {
"McpServers": {
"dev-proxylang-translate": {
"Transport": "http",
"Url": "https://proxylang.dev/mcp"
}
}
} assistant mcp add dev-proxylang-translate -t streamable-http -u 'https://proxylang.dev/mcp'
{
"mcpServers": {
"dev-proxylang-translate": {
"type": "http",
"url": "https://proxylang.dev/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.
- 11 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Oct 26 +1
- Schema quality: pass → fail ▼ functional
- 5 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 30 Sept 26 72
First indexed and scored.
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 12 Oct 2026 · Probed https://proxylang.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=proxylang.dev | CN=WE1,O=Google Trust Services,C=US | 10 Oct 2026 | 8 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 79ab99b5e71ee9cd0e848ee679b98779 |
| SANs: proxylang.dev, api.proxylang.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of proxylang.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| proxylang.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
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=31536000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' blob: https://proxy.proxylang.dev https://proxy-staging.proxylang.dev https://proxy-dev.proxylang.dev https://cloud.umami.is https://www.googletagmanager.com https://stape.proxylang.dev https://www.google.com https://www.gstatic.com https://googleads.g.doubleclick.net https://www.googleadservices.com https://chat.proxylang.dev https://chat-staging.proxylang.dev https://cdn.portone.io; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src 'self' https://fonts.gstatic.com data:; img-src 'self' data: https: blob:; connect-src 'self' https://*.supabase.co wss://*.supabase.co https://api.proxylang.dev https://api-staging.proxylang.dev https://api-dev.proxylang.dev https://proxy.proxylang.dev https://proxy-staging.proxylang.dev https://proxy-dev.proxylang.dev https://chat.proxylang.dev wss://chat.proxylang.dev https://chat-staging.proxylang.dev wss://chat-staging.proxylang.dev https://generativelanguage.googleapis.com wss://generativelanguage.g |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | accelerometer=(), camera=(), geolocation=(), gyroscope=(), magnetometer=(), microphone=(), payment=(), usb=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://proxylang.dev/mcp | Verified | 200 | |
| http (plaintext) | http://proxylang.dev/mcp | HTTPS enforced | 301 | https://proxylang.dev/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 →
proxylang_change_site Change or add the trial's site ~149
Use when the trial was started for the wrong website (action "move": the old site stops), or the tag must also work on a test or staging site (action "add": both work). Same agent_token, script tag, claim_url and free words; all sites share one limit. Not needed for localhost: use localhost_script_tag.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | "move" (default): replace the site. "add": keep the site and also allow this test site (up to 3). |
| agent_token | string | yes | The agent_token from proxylang_start. |
| domain | string | yes | The other website hostname, e.g. "test.example.com". |
No output schema declared.
No examples provided.
proxylang_check Check the install ~63
Is the Proxylang tag on the live site, and have words been translated? If words_translated is 0, a real browser visit to preview_url is needed first.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_token | string | yes | The agent_token from proxylang_start. |
No output schema declared.
No examples provided.
proxylang_next Message for the user ~84
Returns message_for_user: the message to end setup with (the site works, the link to keep it, and only the Proxylang features that fit this site). Show it as it is, in the user's language, with <claim_url> replaced by the saved claim_url.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_token | string | yes | The agent_token from proxylang_start. |
No output schema declared.
No examples provided.
proxylang_start Start a Proxylang trial ~153
Set up Proxylang on a website with no signup: returns the script tag, install steps for the site's platform, an agent_token for the other tools, and claim_url (sent once; save it). If the user named a language, use it; otherwise pick the one their customers most likely speak and say why. The free trial shows the first language; list other recommended languages after it.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | The website hostname, e.g. "example.com". |
| languages | array | yes | Language codes, most important first, e.g. ["ja", "ko"]. |
| source_lang | string | – | Optional. The site's own language; read from the page when left out. |
No output schema declared.
No examples provided.
proxylang_status Trial status ~41
Free words left, trial expiry, and whether the user claimed or paid.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_token | string | yes | The agent_token from proxylang_start. |
No output schema declared.
No examples provided.
proxylang_style Match the language menu to the site ~260
Restyle the language menu so it looks like part of the site. Read the site's brand color, background, text color, button roundness and dark mode first, then send only the fields to change in `style`. Colors: #hex, rgb(), hsl() or a CSS color name; each has a Light and a Dark version. Full field list: https://proxylang.dev/agents.md step 7.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_token | string | yes | The agent_token from proxylang_start. |
| style | object | yes | Fields to change, e.g. {"accent": "#0a7cff", "triggerBgLight": "#ffffff", "triggerTextLight": "#111827", "borderRadius": "pill"}. Fields: triggerBg/triggerText/triggerHover/dropdownBg/dropdownText/bg… |
No output schema declared.
No examples provided.
What is the Proxylang website translation MCP server?
Proxylang website translation is an MCP server listed in the public MCP registry as dev.proxylang/translate. Translate a website into other languages from one script tag. Free trial, no signup. This page covers its hosted endpoint (https://proxylang.dev/mcp).
Is the Proxylang website translation MCP server safe to use?
Proxylang website translation scores 77 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 Proxylang website translation MCP server expose?
Proxylang website translation exposes 6 tools: proxylang_start, proxylang_check, proxylang_next, proxylang_status, proxylang_change_site, proxylang_style. Their descriptions and schemas cost roughly 750 tokens of context every time the server is loaded.
Does the Proxylang website translation MCP server require authentication?
No. We connected to Proxylang website translation without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Proxylang website translation MCP server still maintained?
Proxylang website translation is still listed as active in the MCP registry. We last reached this channel on 12 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.