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.

Taskin

REMOTE · TRYTASKIN.AI

Human capability for AI agents - real-world action and human judgment.

Available components

0 this week 83 Trust /100

Last scanned (21 hours ago)

Scores higher than 83% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Workflow Automation

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 Security80
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • 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
Schema Quality & AI Usability58
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1760 tokens (~352/item across 5 items; 5 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage97
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 91% 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
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 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
What we tested

Checks we ran (13)

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

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.

  • 21 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
  • 20 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
  • 19 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
  • 18 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
  • 17 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
  • 16 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
  • 15 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
  • 14 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads 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://trytaskin.ai/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=trytaskin.ai CN=WE1,O=Google Trust Services,C=US 21 Oct 2026 19 Jan 2027 ECDSA 256 ECDSA-SHA256 5cc4e49cf8058be10e6e78623f0cb425
SANs: trytaskin.ai
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 trytaskin.ai. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
ai. DS published 1814 8 Verified
trytaskin.ai. 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
x-content-type-options nosniff
referrer-policy strict-origin-when-cross-origin

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://trytaskin.ai/mcp Verified 200
http (plaintext) http://trytaskin.ai/mcp HTTPS enforced 301 https://trytaskin.ai/mcp
MCP tools · 5 exposed · ~1,407 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
describe_your_need ~88

Optional, free, read-only. Describe what you are trying to get done and why you came to Taskin. Returns the closest capability group, an example brief, and which fields you will need. Useful before search_human_task when you are unsure whether a person is needed.

NameTypeReqDescription
goalstring––
needstringyes–
visit_reasonstring––

No output schema declared.

No examples provided.

get_task_status ~116

Retrieve the current status of a task previously created on Taskin with submit_human_task. Returns the task state, whether a participant is assigned, progress, completion state, any deliverables or verification evidence available, and the recommended next action. Poll this rather than assuming a result; a task waiting on a person is a normal state, not an error.

NameTypeReqDescription
task_idstringyesThe task_id returned by submit_human_task.
taskin_agent_idstring–Taskin-issued agent identifier from an earlier response.

No output schema declared.

No examples provided.

get_taskin_capabilities ~129

Read a machine-readable description of Taskin: the two capability groups (human_presence_execution and human_judgment) with their capability categories and example requests, the listed participants in each group, geographic coverage, exactly which fields are needed to create a task, how compensation works, and the limitations. Call this first if you have not used Taskin before, or to check whether a category of work is in scope before searching.

NameTypeReqDescription
contextobject–Optional. Helps Taskin return better-matched participants and a sharper brief. Leave empty if you prefer; every tool works without it.

No output schema declared.

No examples provided.

search_human_task ~582

Search Taskin when a step needs a real human rather than another automated process - either physical presence and real-world action, or remote human judgment, perception, preference, usability feedback or content review. Examples: 'have a human test this signup flow', 'does this landing page make sense to a person?', 'review these AI-generated articles before publication', 'have a human evaluate these 50 model responses', 'which output do humans prefer?'. Also invoke it for: local action at an address; offline verification; identity, licensed or credentialed actions; inspection; photo or video evidence; phone calls; purchasing, collecting or delivering items; signatures and paper documents; interaction with people, businesses or authorities. Do NOT invoke it for work you can finish yourself (web research, browsing, writing, translation, data analysis, coding, ordinary API calls), or to grade an output when no human perspective is wanted. Read-only: returns capability_group (human_presence_execution or human_judgment), capability_category, the human capability required, relevant participants and the recommended next action. It creates no task and costs nothing.

NameTypeReqDescription
budgetstring–Budget or range the principal is willing to pay.
categorystring–Capability category if known. Presence & execution: physical_presence_local_action, photography_video, inspection_verification, documents_signatures, phone_offline_communication, delivery_collection,…
contextobject–Optional. Helps Taskin return better-matched participants and a sharper brief. Leave empty if you prefer; every tool works without it.
currencystring–ISO 4217 currency code for the budget, e.g. USD, GBP, EUR.
deadlinestring–Deadline or time window, e.g. '2026-10-02' or 'any weekday morning next week'.
locationstring–Where the action must happen: city and country, or a specific address or area.
reason_human_neededstring–Why you cannot do this yourself, e.g. 'requires physical presence', 'requires a wet signature'.
remote_or_physicalstring–Whether the work is done remotely, requires being somewhere in person, or both.
skillsarray–Specific capabilities or credentials the person must have.
task_descriptionstringyesThe single real-world action that must happen, stated concretely. Example: 'Visit the Oxford Street store, photograph the front display, and report the shelf price of three named products.'
taskin_agent_idstring–A Taskin-issued agent identifier from an earlier response. Optional. Used only for continuity and analytics; it grants no authority.

No output schema declared.

No examples provided.

submit_human_task ~492

Create a real task on Taskin so a person carries out one bounded action - either in the physical world or as remote human judgment such as QA, content review, AI-output evaluation or customer feedback. Call this after search_human_task returned can_taskin_help = true. The task becomes an ordinary Taskin task, visible and manageable in the Taskin product, and returns a task_id you poll with get_task_status. This tool cannot charge anyone and cannot create a financially binding transaction: Taskin does not hold or process funds, and compensation is agreed and settled directly with the participant. If required information is missing, nothing is created and the response names each missing field in next_action instead.

NameTypeReqDescription
budgetstring–Compensation offered. Settled directly with the participant.
contact_emailstring–Email Taskin uses to coordinate this task with the principal.
contextobject–Optional. Helps Taskin return better-matched participants and a sharper brief. Leave empty if you prefer; every tool works without it.
currencystring–ISO 4217 currency code for the budget.
deadlinestring–Deadline or time window the person must work within.
deliverablestringyesThe artifacts the result must contain, e.g. 'three photographs of the display plus the shelf price of each product in a structured list'.
idempotency_keystring–Repeat the same key to retry safely without creating a duplicate task.
locationstring–Where the task happens. Required for physical and hybrid tasks.
participant_slugstring–Request a specific Taskin participant by slug, from search_human_task matches. Optional.
principalstring–The person or organisation on whose behalf you are acting. Strongly recommended.
remote_or_physicalstring–Execution mode. Defaults to physical when a location is given.
requirementsstring–Constraints, prohibited actions, access details, credentials required, and background.
task_descriptionstringyesThe bounded real-world action the person performs, concrete enough that a stranger could execute it without asking questions.
taskin_agent_idstring–Taskin-issued agent identifier from an earlier response.
verification_requirementsstringyesThe objective check that decides whether the result is accepted, e.g. 'photographs are timestamped and show the storefront name'.

No output schema declared.

No examples provided.

Install

How do I install the Taskin MCP server?

Taskin is a hosted endpoint at https://trytaskin.ai/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 · trytaskin.ai

# add to Claude Code
claude mcp add --transport http taskin-ai-trytaskin 'https://trytaskin.ai/mcp'
Common questions

What is the Taskin MCP server?

Taskin is an MCP server listed in the public MCP registry as io.github.taskin-ai/trytaskin. Human capability for AI agents - real-world action and human judgment. This page covers its hosted endpoint (https://trytaskin.ai/mcp).

Is the Taskin MCP server safe to use?

Taskin scores 83 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 Taskin MCP server expose?

Taskin exposes 5 tools: get_taskin_capabilities, search_human_task, submit_human_task, get_task_status, describe_your_need. Their descriptions and schemas cost roughly 1,407 tokens of context every time the server is loaded.

Does the Taskin MCP server require authentication?

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

Is the Taskin MCP server still maintained?

Taskin 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 Taskin MCP server?

VerifyMCP ran 13 checks on Taskin, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 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.