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.

Thread Otter

REMOTE · WWW.THREADOTTER.COM · SCANNED SEP 20

Free buyer-thread finder, Reddit demand board + full GTM agent tools; try with no key.

0 this week 92 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 Security89
Transport & Reachability100
Schema Quality & AI Usability79
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 655 tokens (~93/item across 7 items; 7 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the Thread Otter MCP server?

Thread Otter is a hosted endpoint at https://www.threadotter.com/api/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 · www.threadotter.com

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

  • 13 Sept 26 +1
    • Stability: 0.97 → pass security
  • 11 Sept 26 +1

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

  • 9 Sept 26 +1

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

  • 6 Sept 26 +1

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

  • 4 Sept 26 +1

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

  • 2 Sept 26 +1

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

  • 31 Aug 26 +1

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

  • 29 Aug 26 +1

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

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 20 Sept 2026 · Probed https://www.threadotter.com/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=www.threadotter.com CN=YR2,O=Let's Encrypt,C=US 18 Sept 2026 17 Dec 2026 RSA 2048 SHA256-RSA 6cc78d49b28b39281a2ba61a1a071b3555a
SANs: www.threadotter.com
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of www.threadotter.com. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
threadotter.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Challenged, unverified

The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.

Result Challenged, unverified
Enforced On tool calls
HTTP status 200
Header Value
strict-transport-security max-age=63072000
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=()

Protected resource metadata

Retrieved No
Problem no_resource_metadata

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://www.threadotter.com/api/mcp Verified 200
http (plaintext) http://www.threadotter.com/api/mcp HTTPS enforced 308 https://www.threadotter.com/api/mcp
MCP tools · 7 exposed · ~564 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
competitor_complaints ~73

Free live scan: this month's Reddit threads where people are complaining about a named product, asking for alternatives, or evaluating it. Classified by complaint-shaped language with the threads as receipts. Limited to 5 scans per day.

NameTypeReqDescription
competitorstringyesThe product or company name, e.g. "HeyReach".

No output schema declared.

No examples provided.

demand_radar ~91

Free weekly comparison of buyer demand on Reddit BY CATEGORY (startups, marketing, sales, dev & AI, services, ecommerce): where demand ran hottest this week, with top themes and thread receipts per category. Call with no arguments for the comparison, or pass a category key for its detail.

NameTypeReqDescription
categorystringOptional category key: startups | marketing | sales | dev-ai | services | ecommerce.

No output schema declared.

No examples provided.

find_buyer_threads ~130

Free GTM demo: give it a product website URL and Thread Otter crawls the site, works out who its buyers are, and mines recent Reddit threads where those buyers are asking for something like it. Returns a report link; results are ready in ~2-3 minutes via get_demo_report. Limited to 2 runs per day.

NameTypeReqDescription
emailstringOptional: the user's email if they'd like a follow-up with their full results. Ask before providing; leave out otherwise.
website_urlstringyesThe product's website URL, e.g. https://example.com

No output schema declared.

No examples provided.

get_demo_report ~55

Fetch the results of a find_buyer_threads run: top matched buyer threads with relevance scores, plus a link to the full report with reply drafts.

NameTypeReqDescription
slugstringyesThe run slug returned by find_buyer_threads.

No output schema declared.

No examples provided.

get_started ~38

How to connect Thread Otter: what this server does, the free tools available anonymously, trial signup, and API key setup. Works without authentication.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

reddit_demand_board ~100

Free weekly board of what people keep asking for across 40 startup, marketing, sales, dev, and ecommerce subreddits: recurring pains, missing tools, and paying-shaped demand with real thread links. Call with no arguments for the cross-community leaderboard, or pass a community for its full breakdown.

NameTypeReqDescription
communitystringOptional subreddit name (e.g. "startups" or "r/SaaS") for a per-community breakdown.

No output schema declared.

No examples provided.

subreddit_rules ~77

Free lookup of a subreddit's promotion posture from Thread Otter's community vetting data (2,000+ profiled subreddits): self-promo policy, link policy, and how to write for the room.

NameTypeReqDescription
subredditstringyesSubreddit name, e.g. "startups" or "r/SaaS".

No output schema declared.

No examples provided.

Common questions

What is the Thread Otter MCP server?

Thread Otter is an MCP server listed in the public MCP registry as com.threadotter/agent. Free buyer-thread finder, Reddit demand board + full GTM agent tools; try with no key. This page covers its hosted endpoint (https://www.threadotter.com/api/mcp).

Is the Thread Otter MCP server safe to use?

Thread Otter scores 92 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 Thread Otter MCP server expose?

Thread Otter exposes 7 tools: get_started, find_buyer_threads, get_demo_report, reddit_demand_board, subreddit_rules, and 2 more. Their descriptions and schemas cost roughly 564 tokens of context every time the server is loaded.

Does the Thread Otter MCP server require authentication?

Yes. Thread Otter asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the Thread Otter MCP server still maintained?

Thread Otter is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.