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.

Goptin

REMOTE · APP.GOPTIN.COM

One MCP server for all your work accounts: Slack, Teams, Google Chat, Jira, ClickUp, digest, tasks.

Available components

75 Trust /100

Last scanned (21 minutes ago)

Scores higher than 64% 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 Security89
Transport & Reachability100
Schema Quality & AI Usability69
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1773 tokens (~126/item across 14 items; 14 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 Management10
  • Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage95
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 84% 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
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.

  • 4 Nov 26 +1
    • “list_conversations” reworded the description of “channel” cosmetic
    • “search_messages” reworded the description of “channel” cosmetic

    2 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.

  • 3 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “get_ticket” rewrote its description, which is the text the model reads security
    • Tool “list_tickets” rewrote its description, which is the text the model reads security
    • Schema quality: pass → fail ▼ functional
    • Tool coverage: 74% → 84% ▲ functional
    • Stability: unverified → 0.03 ▲ functional
    • Server version: 1.0.0 → 1.2.0 functional
    • New tool “comment_ticket” functional
    • New tool “complete_task” functional
    • New tool “create_task” functional
    • New tool “find_person” functional
    • New tool “get_digest” functional
    • New tool “list_tasks” functional
    • New tool “update_ticket” functional
    • “get_ticket” added an optional parameter “account_id” cosmetic
    • “get_ticket” added an optional parameter “max_description” cosmetic
    • “get_ticket” added an optional parameter “ticket_id” cosmetic
    • “list_tickets” added an optional parameter “assignee” cosmetic
    • “list_tickets” added an optional parameter “include_description” cosmetic
    • “list_tickets” added an optional parameter “list” cosmetic
    • “list_tickets” added an optional parameter “scope” cosmetic
    • “list_tickets” added an optional parameter “tag” cosmetic
    • “get_ticket” reworded the description of “conversation_id” cosmetic
    • “get_ticket” made “conversation_id” optional cosmetic
  • 2 Nov 26 74

    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://app.goptin.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=goptin.com CN=YR1,O=Let's Encrypt,C=US 5 Sept 2026 4 Dec 2026 RSA 2048 SHA256-RSA 56f3da25b3a6534a73504ef0437bae02031
SANs: app.goptin.com, goptin.com, www.goptin.com
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
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 app.goptin.com. — Not signed

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

WWW-Authenticate challenge Bearer realm="goptin"

Bearer realm="goptin"
Header Value
strict-transport-security max-age=63072000

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://app.goptin.com/mcp Verified 200
http (plaintext) http://app.goptin.com/mcp HTTPS enforced 308 https://app.goptin.com/mcp
MCP tools · 14 exposed · ~1,600 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
comment_ticket ~113

Post a comment on a Jira/ClickUp ticket as the user. The team sees it — show the exact text to the user and confirm first.

NameTypeReqDescription
account_idstring–The board's account_id from list_tickets (use with ticket_id)
conversation_idstring–The ticket's conversation_id from list_tickets (when it has one)
textstringyes–
ticket_idstring–ticket_id (ClickUp) or key (Jira) from list_tickets

No output schema declared.

No examples provided.

complete_task ~57

Mark a Goptin task done (or reopen it with done=false). ClickUp-linked tasks are updated in ClickUp too.

NameTypeReqDescription
doneboolean–false reopens the task (default true)
task_idstringyes–

No output schema declared.

No examples provided.

create_task ~86

Add a task to the user's Goptin to-do list (private to the user, nothing is sent to anyone).

NameTypeReqDescription
conversation_idstring–Link the task to the conversation it came from
due_datestring–YYYY-MM-DD
notestring––
titlestringyesShort imperative, e.g. "Send the quote to Minh"

No output schema declared.

No examples provided.

find_person ~84

Find a person by name, nickname or email across all accounts — ignores diacritics and word order ("Lena" finds "Le Na Nguyen" and "Nguyen Le Na"). Returns their identities per app, grouped when the names match, and the conversations they're in (DMs first).

NameTypeReqDescription
querystringyesName, part of a name, username or email

No output schema declared.

No examples provided.

get_digest ~56

Read the user's latest daily digest (one per workspace): a summary of the last 24h across all accounts, tasks due today/overdue, high-priority tickets, and conversations waiting for the user's reply. Start the day here.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_ticket ~185

Get one ticket live: full description, status, assignees, tags, parent, subtasks, linked tickets, attachments (with URLs), plus comments. Pass ticket_id (and account_id when you have several boards) from list_tickets, or a conversation_id. Synced tickets return the inbox thread including status/assignee/due-date change events.

NameTypeReqDescription
account_idstring–account_id of the Jira/ClickUp board (from list_tickets)
comment_limitnumber–Default 20, max 100
conversation_idstring–The ticket's conversation_id, when list_tickets returned one
max_descriptionnumber–Truncate the description to this many characters (default: full)
ticket_idstring–ticket_id (ClickUp) or key (Jira, e.g. SCRUM-3)

No output schema declared.

No examples provided.

list_accounts ~36

List every account the user has connected to Goptin (several per channel is normal). Call this first to pick the right account.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_conversations ~196

List recent inbox conversations (DMs, groups, channels, ticket threads), newest first, across all or one account.

NameTypeReqDescription
accountstring–Which connected account to use: an account_id from list_accounts, or part of its name (e.g. "EverydAI", "Zalo shop"). Omit to search all accounts.
beforestring–ISO date: page back to conversations active before this time
channelstring–Restrict to one channel: slack, msteams, googlechat, jira, clickup, telegram, zalo, gmail, facebook, instagram, whatsapp.
include_hiddenboolean–Also include conversations the user hid
limitnumber–Max results (default 20, max 50)
querystring–Filter by title or last-message text
unread_onlyboolean–Only conversations with unread messages or unread @mentions

No output schema declared.

No examples provided.

list_tasks ~62

List the user's Goptin to-do list (manual, AI-extracted and ClickUp-synced tasks). Open tasks by default.

NameTypeReqDescription
include_doneboolean–Also include completed tasks
limitnumber–Default 50, max 200

No output schema declared.

No examples provided.

list_tickets ~285

List tickets live from Jira / ClickUp with status, assignees, tags, list/sprint, parent, custom fields and linked tickets. Default: open tickets assigned to the user in their current sprint/list. ClickUp: pass list (e.g. "Sprint 102") and scope="anyone" for every ticket in a sprint, include_done for closed statuses.

NameTypeReqDescription
accountstring–Which connected account to use: an account_id from list_accounts, or part of its name (e.g. "EverydAI", "Zalo shop"). Omit to search all accounts.
assigneestring–Only tickets with an assignee matching this name (diacritics-insensitive)
channelstring––
include_descriptionboolean–Return each ticket's full description (useful to find MR/branch links)
include_doneboolean–Include completed statuses
liststring–Sprint / list name fragment or list id (e.g. "Sprint 102"). ClickUp: loads that whole list
scopestring–"me" (default): tickets assigned to the user; "anyone": every ticket in the list (ClickUp)
statusstring–Only statuses whose name contains this text
tagstring–Only tickets with a tag containing this text

No output schema declared.

No examples provided.

read_conversation ~70

Read the messages of one conversation, oldest first. Use `before` with the earliest sent_at to page back.

NameTypeReqDescription
beforestring–ISO date: only messages sent before this time
conversation_idstringyes–
limitnumber–Default 30, max 100

No output schema declared.

No examples provided.

search_messages ~124

Full-text search over stored messages across all or one account.

NameTypeReqDescription
accountstring–Which connected account to use: an account_id from list_accounts, or part of its name (e.g. "EverydAI", "Zalo shop"). Omit to search all accounts.
channelstring–Restrict to one channel: slack, msteams, googlechat, jira, clickup, telegram, zalo, gmail, facebook, instagram, whatsapp.
limitnumber–Default 20, max 50
querystringyes–

No output schema declared.

No examples provided.

send_message ~77

Send a message as the user into an existing conversation, through the account that conversation belongs to. This really delivers to the other person — confirm the text with the user first.

NameTypeReqDescription
conversation_idstringyes–
textstringyes–
thread_idstring–Reply inside a thread (thread_id from read_conversation)

No output schema declared.

No examples provided.

update_ticket ~169

Change a Jira/ClickUp ticket: move it to another status (use a status name shown by list_tickets), set the due date, or replace the description. Changes are visible to the user's team — confirm with the user first.

NameTypeReqDescription
account_idstring–The board's account_id from list_tickets (use with ticket_id)
conversation_idstring–The ticket's conversation_id from list_tickets (when it has one)
descriptionstring–Replaces the whole description
due_datestring–YYYY-MM-DD
statusstring–Target status name, e.g. "qa approved" or "In Review"
ticket_idstring–ticket_id (ClickUp) or key (Jira) from list_tickets

No output schema declared.

No examples provided.

Install

How do I install the Goptin MCP server?

Goptin is a hosted endpoint at https://app.goptin.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 · app.goptin.com

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

What is the Goptin MCP server?

Goptin is an MCP server listed in the public MCP registry as com.goptin/goptin. One MCP server for all your work accounts: Slack, Teams, Google Chat, Jira, ClickUp, digest, tasks. This page covers its hosted endpoint (https://app.goptin.com/mcp).

Is the Goptin MCP server safe to use?

Goptin scores 75 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 Goptin MCP server expose?

Goptin exposes 14 tools: list_accounts, list_conversations, read_conversation, search_messages, send_message, and 9 more. Their descriptions and schemas cost roughly 1,600 tokens of context every time the server is loaded.

Does the Goptin MCP server require authentication?

Yes. Goptin 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 Goptin MCP server still maintained?

Goptin 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.