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 AI Content Studio

REMOTE · CONTENT.MCP.GOAIMOAT.COM

Bilingual cross-border and AI content generation.

−18 this week 0 Trust /100

Last scanned (39 days ago)

Scores higher than 0% of remote servers

Unreachable for 7 days in a row. Last reached 3 Oct 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.

Recent critical change

TLS certificate (4 Oct 2026). See the changelog before you install this server.

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://content.mcp.goaimoat.com/mcp
    Package shows
    Certificate names ai-visibility-cn.mcp.goaimoat.com, ai-visibility.mcp.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.

  • 13 Oct 26 −4

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

  • 12 Oct 26 −3

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

  • 10 Oct 26 −4

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

  • 9 Oct 26 −3

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

  • 7 Oct 26 −4

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

  • 4 Oct 26 0
    • TLS certificate: pass → fail ▼ critical
    • Score status: scored → failed ▼ critical
    • Endpoint reachability: not serving MCP → unreachable ▼ security
    • HSTS header: fail → unverified ▼ security
    • Transport: Transport check failed: declared streamable-http, but the TLS certificate failed verification. security
  • 28 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
  • 26 Sept 26 0
    • Endpoint reachability: reachable → not serving MCP ▼ security
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 13 Oct 2026 · Probed https://content.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=ai-visibility.mcp.goaimoat.com CN=YE1,O=Let's Encrypt,C=US 3 Oct 2026 1 Jan 2027 ECDSA 256 ECDSA-SHA384 5b5d2b444c5c21dd7b31ad82021a84873b1
SANs: ai-visibility-cn.mcp.goaimoat.com, ai-visibility.mcp.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 content.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://content.mcp.goaimoat.com/mcp TLS failed
http (plaintext) http://content.mcp.goaimoat.com/mcp Inconclusive 404
MCP tools · 3 exposed · ~396 tokens

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 →

Tool Tokens
draft_outreach_email ~161

生成一封定制 B2B 触达邮件初稿(点名道姓、不群发式话术)。 用于路径三获客(传统制造/贸易企业 AI 落地),语气专业克制、给竞对情报价值而非硬推销。

NameTypeReqDescription
companystringyes目标企业名。
contact_namestring–收件人称呼(如「王总」),留空则用「您好」。
contextstring–已核实的触达背景(竞对动向/该企业公开信号/价值主张)。留空则生成通用模板。
langstring–输出语言,zh/en(默认 zh)。

Structured output declared, but exposes no named fields.

No examples provided.

draft_weekly_brief ~167

按主题生成一期「出海 × AI」周报初稿(本期焦点 + 本周信号 + 行动清单)。 DeepSeek 只做内容加工,传入的 signals 应是已核实的信号素材;未提供时仅生成框架, 不会凭空编造数据。发布前需人工核对事实口径。

NameTypeReqDescription
langstring–输出语言,zh=中文 / en=英文(默认 zh)。
signalsstring–已核实的本周信号素材(分号分隔的要点,可含来源)。留空则只生成结构框架。
themestringyes本周主题(如「AI 开始替人下单了」)。

Structured output declared, but exposes no named fields.

No examples provided.

translate ~68

中英双向翻译(面向出海场景,保留品牌名与术语一致)。

NameTypeReqDescription
textstringyes待翻译文本。
to_langstring–目标语言,zh=译成中文 / en=译成英文(默认 en)。

Structured output declared, but exposes no named fields.

No examples provided.

Install

How do I install the GoAI Moat AI Content Studio MCP server?

GoAI Moat AI Content Studio is a hosted endpoint at https://content.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 · content.mcp.goaimoat.com

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

What is the GoAI Moat AI Content Studio MCP server?

GoAI Moat AI Content Studio is an MCP server listed in the public MCP registry as com.goaimoat/content-studio. Bilingual cross-border and AI content generation. This page covers its hosted endpoint (https://content.mcp.goaimoat.com/mcp).

What tools does the GoAI Moat AI Content Studio MCP server expose?

GoAI Moat AI Content Studio exposes 3 tools: draft_weekly_brief, draft_outreach_email, translate. Their descriptions and schemas cost roughly 396 tokens of context every time the server is loaded.

Does the GoAI Moat AI Content Studio MCP server require authentication?

Its publisher declares no required credentials for GoAI Moat AI Content Studio. 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 AI Content Studio MCP server still maintained?

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