Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

GoAI Moat Translation

REMOTE · TRANSLATE.MCP.GOAIMOAT.COM

Professional multi-language translation.

−23 this week 0 Trust /100

Last scanned (52 days ago)

Scores higher than 0% of remote servers

Unreachable for 7 days in a row. Last reached 24 Sep 2026.

Deprecated

This server is marked deprecated in the MCP registry. The registry records this reason: Retired after product audit: no paid value for agents. Current lineup: https://goaimoat.com/mcp-catalog.html.

Dead

Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.

Trust breakdown (7 categories)

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 Security0
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

What we tested

Checks we ran (3)

  • TLS certificate
  • DNSSEC
  • Transport

Checks we could not complete (8)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 404, which proves neither a plaintext path nor enforcement.
  • HSTS header in Endpoint SecurityHSTS not yet verified: we couldn't read the response headers to check for it.
  • Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
  • Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Registry listing versus package

Where what the registry lists and what we observed about the package disagree. This is read from the stored diagnostics and is never an input to the score.

  • TLS certificate hostname

    Registry says
    https://translate.mcp.goaimoat.com/mcp
    Package shows
    Certificate names brief.goaimoat.com, comp.mcp.goaimoat.com, contacts.mcp.goaimoat.com, content.mcp.goaimoat.com, goaimoat.com, intel.mcp.goaimoat.com, mcp.goaimoat.com, www.goaimoat.com

    The certificate does not name the host we connected to. See the evidence →

Changelog

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.

  • 1 Oct 26 −5

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 30 Sept 26 −4

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 29 Sept 26 −5

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 28 Sept 26 −4
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Sept 26 −5

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 24 Sept 26 23

    First indexed and scored.

Diagnostics

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 1 Oct 2026 · Probed https://translate.mcp.goaimoat.com/mcp

TLS invalid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Chain error: Hostname mismatch

Subject Issuer Valid from Valid until Key Signature Serial
CN=goaimoat.com CN=YE1,O=Let's Encrypt,C=US 24 Sept 2026 23 Dec 2026 ECDSA 256 ECDSA-SHA384 5809d6369c90f6bc543dafdb576eccea677
SANs: brief.goaimoat.com, comp.mcp.goaimoat.com, contacts.mcp.goaimoat.com, content.mcp.goaimoat.com, goaimoat.com, intel.mcp.goaimoat.com, mcp.goaimoat.com, www.goaimoat.com
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of translate.mcp.goaimoat.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
goaimoat.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://translate.mcp.goaimoat.com/mcp TLS failed
http (plaintext) http://translate.mcp.goaimoat.com/mcp Inconclusive 404
MCP tools

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 →

No tool schema has been captured from this endpoint yet.

Install

How do I install the GoAI Moat Translation MCP server?

GoAI Moat Translation is a hosted endpoint at https://translate.mcp.goaimoat.com/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 · translate.mcp.goaimoat.com

# add to Claude Code
claude mcp add --transport http com-goaimoat-translation 'https://translate.mcp.goaimoat.com/mcp'
Common questions

What is the GoAI Moat Translation MCP server?

GoAI Moat Translation is an MCP server listed in the public MCP registry as com.goaimoat/translation. Professional multi-language translation. This page covers its hosted endpoint (https://translate.mcp.goaimoat.com/mcp).

Does the GoAI Moat Translation MCP server require authentication?

Its publisher declares no required credentials for GoAI Moat Translation. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

Is the GoAI Moat Translation MCP server still maintained?

GoAI Moat Translation is marked deprecated in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.