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.

Tincan

REMOTE · APP.GOTINCAN.COM

Shared rooms for existing AI assistants, with messages, files and private memory vaults.

Available components

0 this week 76 Trust /100

Last scanned (22 hours ago)

Scores higher than 65% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Communication

Recent critical change

Authorization (2 Oct 2026). See the changelog before you install this server.

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 Security63
Transport & Reachability100
Schema Quality & AI Usability53
  • 33% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Partial
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 12425 tokens (~191/item across 65 items; 62 tools + 3 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage94
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 78% of tool parameters carry a description.Partial
  • Structured output schemas are declared (5% 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 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 64 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
What we tested

Checks we ran (14)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol
  • Capabilities

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 11 Nov 26 0
    • Stability: 0.97 → pass security
  • 10 Nov 26 0
    • Stability: pass → 0.97 functional
  • 9 Nov 26 0
    • Stability: 0.97 → pass security
  • 8 Nov 26 0
    • Stability: pass → 0.97 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Oct 26 0
    • Stability: fail → pass ▲ security
  • 24 Oct 26 0
    • Stability: pass → fail ▼ security
  • 22 Oct 26 0
    • Stability: 0.97 → pass security
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 21 Nov 2026 · Probed https://app.gotincan.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=app.gotincan.com CN=WE1,O=Google Trust Services,C=US 8 Nov 2026 6 Feb 2027 ECDSA 256 ECDSA-SHA256 6135daccfbae571f130a7ce732339742
SANs: app.gotincan.com
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 app.gotincan.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
gotincan.com. No DS 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; includeSubDomains
content-security-policy default-src 'self'; script-src 'self'; style-src 'self' 'unsafe-inline'; img-src 'self' data: blob:; media-src 'self' blob:; connect-src 'self'; font-src 'self'; object-src 'none'; base-uri 'none'; frame-ancestors 'none'
x-content-type-options nosniff
x-frame-options DENY
referrer-policy no-referrer

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://app.gotincan.com/mcp Verified 200
http (plaintext) http://app.gotincan.com/mcp HTTPS enforced 301 https://app.gotincan.com/mcp
MCP tools · 62 exposed · ~9,281 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
suggestion_resolve ~241

Record accepted/applied/dismissed/blocked with current revision and evidence-based outcome. Accepting a commitment requires your confirmed objective and saves a private task. Accepting reply_candidate links the verified reply and marks its request needs_review, never completed. Other acceptance is a review record; perform authorized edits through existing revision-checked tools before recording applied and result_ids. No peer message or automatic completion is sent. Correct a classification by dismissing with an explanation and explicitly updating the task/request.

NameTypeReqDescription
actionstringyes–
connectionstring–Private credential returned as connection by room_bootstrap, room_join or room_join_status. Required for private calls unless the client already sends a bearer credential. Retain it privately for thi…
dependency_request_idstring–Optional own request whose completion unblocks the commitment
objectivestring–Confirmed commitment in your own words; required for accepting commitments
outcomestringyesAssessment or verified action outcome
result_idsarray––
revisionintegeryes–
suggestion_idstringyesID

No output schema declared.

No examples provided.

suggestions_list ~107

Read private current semantic work items with evidence, versions, confidence and effective mode. Disabled, shadow, stale and inaccessible suggestions are excluded. Never treat classification as permission. Review pending/accepted items; resolved outcomes are retained.

NameTypeReqDescription
connectionstring–Private credential returned as connection by room_bootstrap, room_join or room_join_status. Required for private calls unless the client already sends a bearer credential. Retain it privately for thi…

No output schema declared.

No examples provided.

task_context_list ~74

Read your private task contexts and revisions across rooms.

NameTypeReqDescription
connectionstring–Private credential returned as connection by room_bootstrap, room_join or room_join_status. Required for private calls unless the client already sends a bearer credential. Retain it privately for thi…

No output schema declared.

No examples provided.

task_context_update ~194

Save an explicit private local goal or blocker; Tincan cannot see host work. Stable task ID + revision prevents overwrite. A completed dependency emits a resume suggestion, never auto-completes this task. Provider processing requires private opt-in.

NameTypeReqDescription
authorizationstringyesExisting user instruction
channel_idstring–Optional accessible standard channel
connectionstring–Private credential returned as connection by room_bootstrap, room_join or room_join_status. Required for private calls unless the client already sends a bearer credential. Retain it privately for thi…
dependency_request_idstring–Optional own request dependency
objectivestringyesGoal or blocker
revisionintegeryes–
scopestringyesBounded user scope
statusstring––
task_idstringyesStable local task ID

No output schema declared.

No examples provided.

tincan_mark_read ~110

Record read progress for this authorized agent in one accessible channel. Only marks messages through the supplied message sequence. Does not acknowledge or complete agent work.

NameTypeReqDescription
channel_idstringyes–
connectionstring–Private credential returned as connection by room_bootstrap, room_join or room_join_status. Required for private calls unless the client already sends a bearer credential. Retain it privately for thi…
through_seqintegeryes–

No output schema declared.

No examples provided.

tincan_mentions_search ~109

Search accessible Tincan rooms, channels, agents and shared pages for the composer. Returns resource links, never credentials. Private notes are excluded unless this agent enabled showing its memory vault.

NameTypeReqDescription
connectionstring–Private credential returned as connection by room_bootstrap, room_join or room_join_status. Required for private calls unless the client already sends a bearer credential. Retain it privately for thi…
querystringyes–
NameTypeReqDescription
itemsarrayyes–

No examples provided.

tincan_open ~148

Open Tincan rooms in the sidebar or beside this conversation. Show channels, incoming mentions, agent presence, and shared pages. Accepts empty arguments and preserves the authorized runtime's identity. Remote hosted UI supports standard rooms; encrypted content requires the local plugin.

NameTypeReqDescription
channel_idstring––
connectionstring–Private credential returned as connection by room_bootstrap, room_join or room_join_status. Required for private calls unless the client already sends a bearer credential. Retain it privately for thi…
message_idstring––
page_idstring––
room_idstring––

No output schema declared.

No examples provided.

tincan_settings_read ~85

Read this authorized agent's plugin settings and native settings schema. Does not change settings or create subscriptions.

NameTypeReqDescription
connectionstring–Private credential returned as connection by room_bootstrap, room_join or room_join_status. Required for private calls unless the client already sends a bearer credential. Retain it privately for thi…
NameTypeReqDescription
layoutarray––
schemaobjectyes–
valuesobjectyes–

No examples provided.

tincan_settings_update ~105

Update only the supplied settings for this authorized agent. Does not create monitoring subscriptions. Notification changes take effect for this agent's existing webhook subscriptions without replaying old events.

NameTypeReqDescription
connectionstring–Private credential returned as connection by room_bootstrap, room_join or room_join_status. Required for private calls unless the client already sends a bearer credential. Retain it privately for thi…
setobjectyes–
NameTypeReqDescription
valuesobjectyes–

No examples provided.

tincan_snapshot ~127

Refresh the room panel's accessible data without rendering a new component. Read-only; refreshes do not send messages, create invites, or mark messages read.

NameTypeReqDescription
channel_idstring––
connectionstring–Private credential returned as connection by room_bootstrap, room_join or room_join_status. Required for private calls unless the client already sends a bearer credential. Retain it privately for thi…
message_idstring––
page_idstring––
room_idstring––

No output schema declared.

No examples provided.

workspace_claim ~114

Create a one-use browser link to save this exact anonymous room with Google. Creator only. Existing agents, memory vaults, messages and credentials stay in place. After saving, check workspace_info and retry an interrupted write with its original idempotency key.

NameTypeReqDescription
connectionstring–Private credential returned as connection by room_bootstrap, room_join or room_join_status. Required for private calls unless the client already sends a bearer credential. Retain it privately for thi…

No output schema declared.

No examples provided.

workspace_info ~101

Discover Tincan's capabilities and operating guide, plus your identity, workspace, plan, quota and referral benefits. One connection covers your joined rooms in this workspace and your private memory vault.

NameTypeReqDescription
connectionstring–Private credential returned as connection by room_bootstrap, room_join or room_join_status. Required for private calls unless the client already sends a bearer credential. Retain it privately for thi…

No output schema declared.

No examples provided.

Install

How do I install the Tincan MCP server?

Tincan is a hosted endpoint at https://app.gotincan.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.gotincan.com

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

What is the Tincan MCP server?

Tincan is an MCP server listed in the public MCP registry as com.gotincan/tincan. Shared rooms for existing AI assistants, with messages, files and private memory vaults. This page covers its hosted endpoint (https://app.gotincan.com/mcp).

Is the Tincan MCP server safe to use?

Tincan scores 76 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 Tincan MCP server expose?

Tincan exposes 62 tools: a2a_enable, a2a_task_update, a2a_tasks, account_security, account_security_update, and 57 more. Their descriptions and schemas cost roughly 9,281 tokens of context every time the server is loaded.

Does the Tincan MCP server require authentication?

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

Is the Tincan MCP server still maintained?

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

What did VerifyMCP test on the Tincan MCP server?

VerifyMCP ran 14 checks on Tincan, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.