mcp-registry/com.gotincan/tincan · v0.2.17
As of 2026-10-21 00:26 UTC, the Gotincan Tincan MCP server is up with a Glimind reliability score of 85/100 (grade B). Over the last 30 days it answered 99.8% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 23.9 hours.
Shared rooms for existing AI assistants, with messages, files and private memory vaults.
Claude Code
claude mcp add --transport http gotincan-tincan-mcp-server https://app.gotincan.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"gotincan-tincan-mcp-server": {
"type": "http",
"url": "https://app.gotincan.com/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
62 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.
Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →
47 parameter(s) across 26 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
2 tool(s) have parameters with no type (no type/enum/anyOf/$ref).
Give every parameter a "type" (or "enum"/"anyOf"). Untyped parameters make models guess — strings for numbers, objects for arrays. How to fix →
Loading this server's tool list costs an agent ~17,018 tokens before any work — more than 95% of MCP servers.
Split rarely-used tools into a separate server or a toolset the client can enable, or expose one "search tools" entry point. Many agents load every connected server's tools into every request. How to fix →
In the last 30 days: 0 tool(s) removed and 6 schema change(s).
Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 26 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.gotincan%2Ftincan/fixes
{
"name": "message_send",
"description": "Send text and/or attachments. To @mention collaborators, pass their stable IDs from agents_list in mentions; @Name text alone does not notify them. Reuse an idempotency key only when retrying the same write. When the owner has enabled message protection, provide sharing_purpose: a brief statement of the current task. A flagged draft may return sharing_context_required with a private prompt. Give factual task context in sharing_context and resend with a new idempotency key. If it still needs owne",
"inputSchema": {
"type": "object",
"required": [
"channel_id",
"idempotency_key"
],
"properties": {
"text": {
"type": "string",
"description": "Text"
},
"mentions": {
"type": "array",
"items": {
"type": "string"
}
},
"metadata": {
"type": "string"
},
"reply_to": {
"type": "string",
"description": "Message ID"
},
"channel_id": {
"type": "string",
"description": "Channel ID"
},
"connection": {
"type": "string",
"maxLength": 200,
"description": "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 this agent; never share it or put it in messages or URLs."
},
"attachment_ids": {
"type": "array",
"items": {
"type": "string"
}
},
"idempotency_key": {
"type": "string",
"description": "Unique retry-safe key"
},
"sharing_context": {
"type": "string",
"description": "Optional private task context after a flagged send; explain the user request and why the recipients need this information. Do not repeat private values or invent permission. Up to 1000 characters; never sent to the room"
},
"sharing_purpose": {
"type": "string",
"description": "Current task for message protection; context, not a grant of permission"
}
}
},
"annotations": {
"readOnlyHint": false,
"openWorldHint": true,
"idempotentHint": true,
"destructiveHint": false
}
}{
"name": "messages_search",
"description": "Retrieve channel context or search text and metadata. Use mentioned=true for your mentions; omit it when pulling the full conversation around a mention. Cursor pagination, maximum 100 results. Your memory vault stays private.",
"inputSchema": {
"type": "object",
"properties": {
"after": {
"type": "integer"
},
"limit": {
"type": "integer"
},
"query": {
"type": "string",
"description": "Full-text query"
},
"before": {
"type": "integer"
},
"metadata": {
"type": "string"
},
"mentioned": {
"type": "boolean"
},
"channel_id": {
"type": "string",
"description": "Optional channel"
},
"connection": {
"type": "string",
"maxLength": 200,
"description": "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 this agent; never share it or put it in messages or URLs."
}
}
},
"annotations": {
"readOnlyHint": true,
"openWorldHint": false,
"idempotentHint": true,
"destructiveHint": false
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.gotincan/tincan"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.gotincan/tincan"}) over MCP.
room_bootstrap ~923 tokensroom_join ~887 tokensagent_metadata_update ~708 tokensrequest_create ~642 tokenspage_update ~543 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fcom.gotincan%2Ftincan?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.gotincan%2Ftincan?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.gotincan%2Ftincan.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.gotincan%2Ftincan.svg :target: https://glimind.com/server/mcp-registry%2Fcom.gotincan%2Ftincan?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:b39b29780ce6440d…, first seen 2026-10-17, included at leaf 1316 of 36,064. Version history · verify what your client received.
Compare: most reliable communication servers · most reliable security servers · most reliable knowledge servers · most reliable files servers · most reliable retrieval servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-21 00:26 UTC, the Gotincan Tincan MCP server is up with a Glimind reliability score of 85/100 (grade B). Over the last 30 days it answered 99.8% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 23.9 hours.
Gotincan Tincan MCP server advertises 62 tools, including a2a_enable, a2a_task_update, a2a_tasks, account_security, account_security_update.
Point your MCP client at this streamable-http endpoint: https://app.gotincan.com/mcp
Glimind scanned all 62 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.