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.

thatsaid

REMOTE · MCP.THATSAID.APP

Search and read your thatsaid meeting transcripts, summaries and action items. OAuth or token.

Available components

72 Trust /100

Last scanned (20 minutes ago)

Scores higher than 58% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Communication

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 Usability69
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 521 tokens (~65/item across 8 items; 8 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
  • Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage84
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 53% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 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
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.

  • 5 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
    • This server's schema is too large to store in full, so we cannot compare its tools day to day functional
  • 4 Nov 26 +32
    • Authorization: pass → partial ▼ security
    • Transport: unverified → pass ▲ security
    • Injection markers: unverified → pass ▲ security
    • First check of Judged manipulation: pass security
    • MCP protocol: unverified → pass ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • First check of Schema quality: fail functional
    • First check of Tool coverage: 53 functional
    • First check of Destructive annotations: pass functional
    • First check of Schema quality: pass functional
    • First check of Schema quality: good functional
  • 3 Nov 26 39

    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 Nov 2026 · Probed https://mcp.thatsaid.app

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=thatsaid.app CN=WE1,O=Google Trust Services,C=US 1 Nov 2026 30 Jan 2027 ECDSA 256 ECDSA-SHA256 b8d21645c4d574720eb7b02b8ce1c717
SANs: thatsaid.app, mcp.thatsaid.app, *.mcp.thatsaid.app
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 mcp.thatsaid.app. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
app. present 23684 8 Verified
thatsaid.app. 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=15552000
x-content-type-options nosniff

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.thatsaid.app Verified 200
http (plaintext) http://mcp.thatsaid.app HTTPS enforced 301 https://mcp.thatsaid.app/
MCP tools · 8 exposed · ~463 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
get_profile ~32

Your account basics: time zone, retention, how many conversations are stored, and when this token expires. No secrets.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_settings ~32

How this cloud copy of thatsaid is set up: retention, time zone, limits and the file format of transcripts.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_summary ~47

Just the metadata, summary and action items of one conversation (much shorter than the transcript).

NameTypeReqDescription
idstringyesTranscript id (as returned by list/search) or thatsaid:// URI.

No output schema declared.

No examples provided.

get_transcript ~70

The full Markdown of one conversation (front matter, summary, action items and timestamped transcript). Very long transcripts come in pages: pass nextCursor back as cursor.

NameTypeReqDescription
cursorstring––
idstringyesTranscript id (as returned by list/search) or thatsaid:// URI.

No output schema declared.

No examples provided.

list_fragments ~32

Retired: thatsaid deletes empty and junk recordings instead of keeping fragments. Always empty; kept for older clients.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_speakers ~36

Names of the people who appear in your conversations (named speakers only; generic labels like "Speaker 2" are left out).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_transcripts ~151

List conversations, newest first. Filter by day (YYYY-MM-DD), date range, a title/speaker/summary query, or status. Archived meetings are hidden unless include_archived is true.

NameTypeReqDescription
cursorstring–nextCursor from a previous call.
datestring–Only this day, YYYY-MM-DD (your profile time zone, else UTC).
fromstring–Earliest day, YYYY-MM-DD.
include_archivedboolean––
limitinteger––
querystring–Words that must appear in the title, speakers or summary.
statusstring––
tostring–Latest day, YYYY-MM-DD.

No output schema declared.

No examples provided.

search_transcripts ~63

Full-text search across every transcript (all words must appear). Returns matching transcripts with matching lines.

NameTypeReqDescription
include_archivedboolean––
include_fragmentsboolean––
limitinteger––
querystringyesWords to find.

No output schema declared.

No examples provided.

Install

How do I install the thatsaid MCP server?

thatsaid is a hosted endpoint at https://mcp.thatsaid.app/, 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 · mcp.thatsaid.app

# add to Claude Code
claude mcp add --transport http app-thatsaid-thatsaid 'https://mcp.thatsaid.app/'
Common questions

What is the thatsaid MCP server?

thatsaid is an MCP server listed in the public MCP registry as app.thatsaid/thatsaid. Search and read your thatsaid meeting transcripts, summaries and action items. OAuth or token. This page covers its hosted endpoint (https://mcp.thatsaid.app).

Is the thatsaid MCP server safe to use?

thatsaid scores 72 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 thatsaid MCP server expose?

thatsaid exposes 8 tools: get_settings, list_transcripts, search_transcripts, get_transcript, get_summary, and 3 more. Their descriptions and schemas cost roughly 463 tokens of context every time the server is loaded.

Does the thatsaid MCP server require authentication?

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

Is the thatsaid MCP server still maintained?

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