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.

io.github.SergioRico1/thrd

NPM · THRD-MCP

Thrd MCP: agent email tools for events/threads, safe send/reply, usage, trust and security.

Available components

0 this week 72 Trust /100

Last scanned (4 hours ago)

Scores higher than 43% of npm servers

Category Communication

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency18
  • Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 259 days ago).Pass
  • Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability79
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 797 tokens (~44/item across 18 items; 16 tools + 2 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 Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (19% 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
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 17 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.

  • 27 Oct 26 0
    • Stability: 0.97 → pass security
  • 26 Oct 26 0
    • Stability: pass → 0.97 functional
  • 24 Oct 26 −5
    • CVE-2023-54404 affects this package: high ▼ security
    • Known CVEs: pass → fail ▼ security
  • 20 Oct 26 0
    • Stability: 0.97 → pass security
  • 19 Oct 26 0
    • Stability: pass → 0.97 functional
  • 17 Oct 26 +2
    • Stability: 0.87 → pass security
  • 15 Oct 26 +1

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

  • 14 Oct 26 −3
    • Stability: pass → 0.80 functional
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 · Analysed npm/thrd-mcp@0.1.5

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 93 packages
Packages resolved 93
Stale 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 16 exposed · ~756 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
thrd.ack_events ~38

Acknowledge processed events by event IDs or by cursor.

NameTypeReqDescription
cursorstring––
eventIdsarray––

No output schema declared.

No examples provided.

thrd.billing_checkout_self ~31

Create a Stripe checkout session for the authenticated tenant to upgrade plan.

NameTypeReqDescription
planstringyes–

No output schema declared.

No examples provided.

thrd.claim_x_start ~27

Start the X (Twitter) human-claim verification flow for the authenticated tenant.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

thrd.claim_x_status ~26

Check X (Twitter) human-claim verification status for the authenticated tenant.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

thrd.create_security_ack ~59

Create a short-lived security_ack_token to approve replying/sending in a high-risk context.

NameTypeReqDescription
actionstringyes–
messageIdstringyes–
reasonstringyes–
threadIdstring––

No output schema declared.

No examples provided.

thrd.get_thread_messages ~33

Fetch all stored messages for a given thread (inbound + outbound).

NameTypeReqDescription
threadIdstringyes–

No output schema declared.

No examples provided.

thrd.health ~23

Get MCP server and Thrd API configuration info (no auth required).

Input schema present but exposes no named parameters.

NameTypeReqDescription
apiBaseUrlstringyes–
hasApiKeybooleanyes–
okbooleanyes–

No examples provided.

thrd.instant_onboarding ~85

Provision a new tenant + agent + inbox + API key via Thrd's public instant onboarding endpoint. Disabled unless ALLOW_THRD_INSTANT_ONBOARDING=1.

NameTypeReqDescription
agentNamestringyes–
contactEmailstring––
inboxPrefixstring––
sourcestring––
tenantNamestring––

No output schema declared.

No examples provided.

thrd.list_threads ~46

List recent threads for the authenticated agent (optionally filtered by inbox).

NameTypeReqDescription
cursorstring––
inboxIdstring––
limitinteger––
NameTypeReqDescription
threadsarrayyes–

No examples provided.

thrd.message_security ~30

Get Prompt Shield / security analysis for a specific message_id.

NameTypeReqDescription
messageIdstringyes–

No output schema declared.

No examples provided.

thrd.outbound_status ~31

Get status for an outbound request_id from send/reply.

NameTypeReqDescription
requestIdstringyes–

No output schema declared.

No examples provided.

thrd.poll_events ~46

Long-poll for inbound events (email received, security signals, etc.).

NameTypeReqDescription
cursorstring––
limitinteger––
timeoutinteger––
NameTypeReqDescription
eventsarrayyes–
next_cursorstringyes–

No examples provided.

thrd.reply ~93

Reply in an existing thread. Requires idempotency. May return security_ack_required when inbound risk is high.

NameTypeReqDescription
attachmentsarray––
ccarray––
htmlstring––
idempotencyKeystring––
securityAckTokenstring––
textstring––
threadIdstringyes–
tostring––

No output schema declared.

No examples provided.

thrd.send ~144

Initiate a new outbound email. Requires idempotency. Tier 3 cold outbound may return por_required. High-risk inbound context may require security_ack_token.

NameTypeReqDescription
attachmentsarray––
consentTokenstring––
grantTokenstring––
htmlstring––
idempotencyKeystring––
inboxIdstringyes–
porAnswerstring––
porTokenstring––
securityAckTokenstring––
sourceMessageIdstring––
subjectstringyes–
textstring––
tostringyes–

No output schema declared.

No examples provided.

thrd.trust_score ~21

Get trust score and factors for the authenticated tenant.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

thrd.usage ~23

Get plan/tier and monthly quota usage for the authenticated tenant.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the io.github.SergioRico1/thrd MCP server?

io.github.SergioRico1/thrd runs locally as an npm package, launched with npx -y thrd-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · thrd-mcp

# add to Claude Code
claude mcp add sergiorico1-thrd -- npx -y thrd-mcp
Common questions

What is the io.github.SergioRico1/thrd MCP server?

io.github.SergioRico1/thrd is an MCP server listed in the public MCP registry as io.github.SergioRico1/thrd. Thrd MCP: agent email tools for events/threads, safe send/reply, usage, trust and security. This page covers its npm package (thrd-mcp).

Is the io.github.SergioRico1/thrd MCP server safe to use?

io.github.SergioRico1/thrd scores 72 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 2026. It declares no install or post-install scripts. 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 io.github.SergioRico1/thrd MCP server expose?

io.github.SergioRico1/thrd exposes 16 tools: thrd.health, thrd.poll_events, thrd.ack_events, thrd.list_threads, thrd.get_thread_messages, and 11 more. Their descriptions and schemas cost roughly 756 tokens of context every time the server is loaded.

Is the io.github.SergioRico1/thrd MCP server still maintained?

io.github.SergioRico1/thrd 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.

What licence is the io.github.SergioRico1/thrd MCP server under?

io.github.SergioRico1/thrd declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.