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 Decision-Maker Lookup

REMOTE · CONTACTS.MCP.GOAIMOAT.COM · SCANNED SEP 28

Find B2B decision makers and verify work emails.

63 Trust /100
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 Security57
Transport & Reachability100
Schema Quality & AI Usability64
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 611 tokens (~152/item across 4 items; 4 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 Management13
  • Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage88
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 59% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 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
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Install

How do I install the GoAI Moat Decision-Maker Lookup MCP server?

GoAI Moat Decision-Maker Lookup is a hosted endpoint at https://contacts.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 · contacts.mcp.goaimoat.com

# add to Claude Code
claude mcp add --transport http com-goaimoat-decision-maker-lookup 'https://contacts.mcp.goaimoat.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-goaimoat-decision-maker-lookup": {
      "url": "https://contacts.mcp.goaimoat.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-goaimoat-decision-maker-lookup": {
      "type": "http",
      "url": "https://contacts.mcp.goaimoat.com/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.com-goaimoat-decision-maker-lookup]
url = "https://contacts.mcp.goaimoat.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-goaimoat-decision-maker-lookup": {
      "type": "remote",
      "url": "https://contacts.mcp.goaimoat.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-goaimoat-decision-maker-lookup --url 'https://contacts.mcp.goaimoat.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-goaimoat-decision-maker-lookup:
    url: "https://contacts.mcp.goaimoat.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-goaimoat-decision-maker-lookup": {
      "Transport": "http",
      "Url": "https://contacts.mcp.goaimoat.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add com-goaimoat-decision-maker-lookup -t streamable-http -u 'https://contacts.mcp.goaimoat.com/mcp'
// mcp.json
{
  "mcpServers": {
    "com-goaimoat-decision-maker-lookup": {
      "type": "http",
      "url": "https://contacts.mcp.goaimoat.com/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

  • 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
  • 27 Sept 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.

  • 26 Sept 26 +1
    • Schema quality: 493 → 611 ▼ functional
    • Tool coverage: 50% → 59% ▲ functional
    • New tool “verify_email” functional
  • 25 Sept 26 −3
    • 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 64

    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 28 Sept 2026 · Probed https://contacts.mcp.goaimoat.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

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 contacts.mcp.goaimoat.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
goaimoat.com. 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

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://contacts.mcp.goaimoat.com/mcp Verified 200
http (plaintext) http://contacts.mcp.goaimoat.com/mcp HTTPS enforced 301 https://contacts.mcp.goaimoat.com/mcp
MCP tools · 4 exposed · ~496 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
find_decision_makers ~195

免费搜索目标企业的决策者名单(返回存在性 flag,不扣费)。 底层:`monid run -p hunterio -e /multi-domain-search --query '{...}'`(免费端点)。 返回每行带 decision_maker / phone_number_exists / linkedin_exists 等 flag, 先筛出真正的决策者,再对选中的行调用 reveal_work_email()(付费)。

NameTypeReqDescription
companystringyes目标企业域名或名称(如 "example.com")。
departmentstring–部门(sales/marketing/engineering...,默认 sales)。
emailstring––
license_keystring––
limitinteger–最多返回行数(默认 20)。
locationstring–地区(如 "US" / "Shenzhen"),可选。
titlestring––

Structured output declared, but exposes no named fields.

No examples provided.

get_balance ~36

查询 Monid 账户余额(`monid balance`)。

NameTypeReqDescription
emailstring––
license_keystring––

Structured output declared, but exposes no named fields.

No examples provided.

reveal_work_email ~147

付费 reveal:把选定的决策者行变成一条带验证状态的邮箱地址(每行扣一次费)。 两种用法: - 传 reveal_handle(来自 find_decision_makers 结果里的 handle) - 或传 name + company,用 contactout 二次核验

NameTypeReqDescription
companystring–企业名称/域名。
emailstring––
license_keystring––
namestring–决策者姓名(与 company 搭配,作为 contactout 核验的备选)。
reveal_handlestring–搜索结果的 reveal handle(优先)。

Structured output declared, but exposes no named fields.

No examples provided.

verify_email ~118

核验单个邮箱地址是否可投递(在发信前先确认,避免 bounce)。 与 reveal_work_email 的区别:reveal 是「找出你还没有的邮箱」, verify 是「检查你已经有的邮箱能不能用」。用途不同,别用错。

NameTypeReqDescription
addressstringyes要核验的邮箱地址,如 "jane@example.com"。
emailstring–可选,用于记录免费额度。
license_keystring–可选,付费授权。

Structured output declared, but exposes no named fields.

No examples provided.

Common questions

What is the GoAI Moat Decision-Maker Lookup MCP server?

GoAI Moat Decision-Maker Lookup is an MCP server listed in the public MCP registry as com.goaimoat/decision-maker-lookup. Find B2B decision makers and verify work emails. This page covers its hosted endpoint (https://contacts.mcp.goaimoat.com/mcp).

Is the GoAI Moat Decision-Maker Lookup MCP server safe to use?

GoAI Moat Decision-Maker Lookup scores 63 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 GoAI Moat Decision-Maker Lookup MCP server expose?

GoAI Moat Decision-Maker Lookup exposes 4 tools: find_decision_makers, reveal_work_email, verify_email, get_balance. Their descriptions and schemas cost roughly 496 tokens of context every time the server is loaded.

Does the GoAI Moat Decision-Maker Lookup MCP server require authentication?

No. We connected to GoAI Moat Decision-Maker Lookup without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the GoAI Moat Decision-Maker Lookup MCP server still maintained?

GoAI Moat Decision-Maker Lookup is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.