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.

Communicate Developer Docs

REMOTE · COMMUNICATE.SO · SCANNED OCT 4

Read-only access to Communicate developer guides, OpenAPI summaries, and support contact.

Available components

remote · communicate.so 77
77 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 Security80
Transport & Reachability100
Schema Quality & AI Usability88
  • 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 282 tokens (~40/item across 7 items; 3 tools + 4 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
  • Stability observed for 3 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
  • 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 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
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
  • Supports UI / widget rendering.Pass
Install

How do I install the Communicate Developer Docs MCP server?

Communicate Developer Docs is a hosted endpoint at https://communicate.so/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 · communicate.so

# add to Claude Code
claude mcp add --transport http uditgoenka-communicate-docs 'https://communicate.so/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "uditgoenka-communicate-docs": {
      "url": "https://communicate.so/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "uditgoenka-communicate-docs": {
      "type": "http",
      "url": "https://communicate.so/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.uditgoenka-communicate-docs]
url = "https://communicate.so/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "uditgoenka-communicate-docs": {
      "type": "remote",
      "url": "https://communicate.so/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add uditgoenka-communicate-docs --url 'https://communicate.so/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  uditgoenka-communicate-docs:
    url: "https://communicate.so/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "uditgoenka-communicate-docs": {
      "Transport": "http",
      "Url": "https://communicate.so/mcp"
    }
  }
}
# add to Vellum
assistant mcp add uditgoenka-communicate-docs -t streamable-http -u 'https://communicate.so/mcp'
// mcp.json
{
  "mcpServers": {
    "uditgoenka-communicate-docs": {
      "type": "http",
      "url": "https://communicate.so/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.

  • 3 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 2 Oct 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 1 Oct 26 76

    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 5 Oct 2026 · Probed https://communicate.so/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=communicate.so CN=WE1,O=Google Trust Services,C=US 27 Aug 2026 25 Nov 2026 ECDSA 256 ECDSA-SHA256 2bf060f2ef6d58790ef1b9f90ed2f701
SANs: communicate.so, *.communicate.so
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 communicate.so. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
so. 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
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://communicate.so/mcp Verified 200
http (plaintext) http://communicate.so/mcp HTTPS enforced 301 https://communicate.so/mcp
MCP tools · 3 exposed · ~175 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
communicate_get_developer_guide ~64

Return the canonical Communicate API URLs, authentication boundary, and support contact. This tool is public, read-only, and never accesses workspace or customer data.

NameTypeReqDescription
querystring–Optional keyword describing the documentation focus. The complete canonical summary is always returned.
NameTypeReqDescription
apiBaseUrlstringyes–
authenticationstringyes–
docsUrlstringyes–
markdownUrlstringyes–
openapiUrlstringyes–
summarystringyes–
supportstringyes–
titlestringyes–

No examples provided.

communicate_get_openapi_summary ~57

Return the canonical OpenAPI URL, API base URL, authentication boundary, and currently published REST operations without calling the authenticated API.

NameTypeReqDescription
querystring–Optional keyword describing the documentation focus. The complete canonical summary is always returned.
NameTypeReqDescription
apiBaseUrlstringyes–
authenticationstringyes–
openapiUrlstringyes–
operationsarrayyes–
titlestringyes–

No examples provided.

communicate_get_support_contact ~54

Return the official Communicate support email, contact page, support policy, and supported inquiry categories without sending a message.

NameTypeReqDescription
querystring–Optional keyword describing the documentation focus. The complete canonical summary is always returned.
NameTypeReqDescription
contactUrlstringyes–
emailstringyes–
supportPolicyUrlstringyes–
topicsarrayyes–

No examples provided.

Common questions

What is the Communicate Developer Docs MCP server?

Communicate Developer Docs is an MCP server listed in the public MCP registry as io.github.uditgoenka/communicate-docs. Read-only access to Communicate developer guides, OpenAPI summaries, and support contact. This page covers its hosted endpoint (https://communicate.so/mcp).

Is the Communicate Developer Docs MCP server safe to use?

Communicate Developer Docs 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 Communicate Developer Docs MCP server expose?

Communicate Developer Docs exposes 3 tools: communicate_get_developer_guide, communicate_get_openapi_summary, communicate_get_support_contact. Their descriptions and schemas cost roughly 175 tokens of context every time the server is loaded.

Does the Communicate Developer Docs MCP server require authentication?

No. We connected to Communicate Developer Docs without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Communicate Developer Docs MCP server still maintained?

Communicate Developer Docs is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.