Check the connection, the permission and the action.
Availability is specific to an operation and a workspace. Start with the scope that has been verified, then identify the access and evidence your workflow still needs.
Verified: the board and bounded MCP operations
The reviewed Taskin web board stores tasks with human responsibility, completion criteria, sources and comments. Bounded native MCP reads and writes have been verified within a defined scope. This does not establish that every connector or every account is available.
Email: connection is not an agent grant
A mailbox connection identifies a source. An agent grant determines which agent may use that source and for which operations. Reading, preparing a draft, sending and verifying delivery are separate steps. Do not treat a configured mailbox as permission to send; the exact account, recipient, content and authority need their own check.
Calendar, Telegram and app channels
Coverage for reading a calendar, changing an event, receiving a Telegram request or continuing it in the app has not been established here as a universal feature set. Reliable continuity between channels is in development. For your workflow, name the channel, the operation and the account so the team can confirm the actual scope.
Voice and native devices: separate acceptance
The Efir audio source is not active in the public app under the current approved scope. Voice capture, recording and background behavior on iPhone or Watch require separate real-device acceptance. This page does not activate a microphone, place a call or connect a device.
Prepare one operation for discussion
Bring one request: which source, which account, which operation, who authorizes it and what evidence would prove success. Unknown access stays unknown until checked. Call TASKIN at +373 60 456 690 to discuss that scope; this page does not connect accounts or collect your details.