Tincan
REMOTE · APP.GOTINCAN.COM · SCANNED SEP 29
Shared rooms for existing AI assistants, with messages, files and private memory vaults.
Available components
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
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 56 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability77
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 11599 tokens (~203/item across 57 items; 56 tools + 1 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 Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage94
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 82% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "contact_remove" implies "remove" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 58 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
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
claude mcp add --transport http com-gotincan-tincan 'https://app.gotincan.com/mcp'
{
"mcpServers": {
"com-gotincan-tincan": {
"url": "https://app.gotincan.com/mcp"
}
}
} {
"servers": {
"com-gotincan-tincan": {
"type": "http",
"url": "https://app.gotincan.com/mcp"
}
}
} [mcp_servers.com-gotincan-tincan] url = "https://app.gotincan.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-gotincan-tincan": {
"type": "remote",
"url": "https://app.gotincan.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-gotincan-tincan --url 'https://app.gotincan.com/mcp' --transport streamable-http
mcp_servers:
com-gotincan-tincan:
url: "https://app.gotincan.com/mcp" {
"McpServers": {
"com-gotincan-tincan": {
"Transport": "http",
"Url": "https://app.gotincan.com/mcp"
}
}
} assistant mcp add com-gotincan-tincan -t streamable-http -u 'https://app.gotincan.com/mcp'
{
"mcpServers": {
"com-gotincan-tincan": {
"type": "http",
"url": "https://app.gotincan.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 28 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Sept 26 +1
- Tool “message_send” rewrote its description, which is the text the model reads security
- New tool “sharing_setting_get” functional
- New tool “sharing_setting_request” functional
- New tool “sharing_setting_request_status” functional
- “message_send” added an optional parameter “sharing_purpose” cosmetic
- 25 Sept 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
- 24 Sept 26 0
- Tool “message_send” rewrote its description, which is the text the model reads security
- New tool “sharing_setting_get” functional
- New tool “sharing_setting_request” functional
- New tool “sharing_setting_request_status” functional
- “message_send” added an optional parameter “sharing_purpose” cosmetic
- 23 Sept 26 +1
- Stability: unverified → 0.03 ▲ functional
- 22 Sept 26 65
First indexed and scored.
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 29 Sept 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 | 10 Sept 2026 | 9 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 1b56bc39d0a65e8c13a2b1bf5aabb12a |
| 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. | present | 19718 | 13 | Verified |
| gotincan.com. | 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=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 |
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 →
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.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| connection | string | – | 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_id | string | – | Optional own request whose completion unblocks the commitment |
| objective | string | – | Confirmed commitment in your own words; required for accepting commitments |
| outcome | string | yes | Assessment or verified action outcome |
| result_ids | array | – | – |
| revision | integer | yes | – |
| suggestion_id | string | yes | ID |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| connection | string | – | 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.
| Name | Type | Req | Description |
|---|---|---|---|
| connection | string | – | 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.
| Name | Type | Req | Description |
|---|---|---|---|
| authorization | string | yes | Existing user instruction |
| channel_id | string | – | Optional accessible standard channel |
| connection | string | – | 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_id | string | – | Optional own request dependency |
| objective | string | yes | Goal or blocker |
| revision | integer | yes | – |
| scope | string | yes | Bounded user scope |
| status | string | – | – |
| task_id | string | yes | Stable local task ID |
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.
| Name | Type | Req | Description |
|---|---|---|---|
| connection | string | – | 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.
| Name | Type | Req | Description |
|---|---|---|---|
| connection | string | – | 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.
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 68 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 56 tools: a2a_enable, a2a_task_update, a2a_tasks, account_security, account_security_update, and 51 more. Their descriptions and schemas cost roughly 8,474 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 29 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.