Taasky
REMOTE · MCP.TAASKY.AI · 2 COMPONENTS
Your agent settles small things with anyone, agent or browser. Nothing is agreed until you say yes.
Available components
Last scanned (14 hours ago)
Scores higher than 59% of remote servers
Reachable. Last reached 22 Oct 2026.
Category Workflow Automation
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 Security66
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (negotiation_respond). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability73
- 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 3064 tokens (~437/item across 7 items; 7 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 Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 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
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.
- 22 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- “negotiation_propose” added an optional parameter “final” cosmetic
- 21 Oct 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 0.2.0 → 0.2.1 functional
- “negotiation_join” reworded the description of “invite_code” cosmetic
- 20 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “negotiation_open” rewrote its description, which is the text the model reads security
- Schema quality: 375 → 426 ▼ functional
- “negotiation_open” added an optional parameter “options” cosmetic
- “negotiation_open” added an optional parameter “slots” cosmetic
- “negotiation_open” made “subject_schema” optional cosmetic
- 19 Oct 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “negotiation_cancel” rewrote its description, which is the text the model reads security
- Tool “negotiation_join” rewrote its description, which is the text the model reads security
- Tool “negotiation_list” rewrote its description, which is the text the model reads security
- Tool “negotiation_open” rewrote its description, which is the text the model reads security
- Tool “negotiation_propose” rewrote its description, which is the text the model reads security
- Tool “negotiation_read” rewrote its description, which is the text the model reads security
- Tool “negotiation_respond” rewrote its description, which is the text the model reads security
- Schema quality: 322 → 375 ▼ functional
- Tool coverage: 84% → 90% ▲ functional
- Stability: unverified → 0.03 ▲ functional
- Schema quality: good → excellent functional
- Destructive annotations: 100 → pass functional
- Server version: 0.1.0 → 0.2.0 functional
- “negotiation_read” added an optional parameter “timezone” cosmetic
- “negotiation_join” reworded the description of “invite_code” cosmetic
- 18 Oct 26 67
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 22 Oct 2026 · Probed https://mcp.taasky.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=taasky.ai | CN=WE1,O=Google Trust Services,C=US | 12 Oct 2026 | 10 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 450fc62ecc27e3620e0586f0c03160eb |
| SANs: taasky.ai, mcp.taasky.ai, *.mcp.taasky.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 secure
Validation of mcp.taasky.ai. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| taasky.ai. | present | 2371 | 13 | Verified |
| mcp.taasky.ai. | Verified address RRset verified with the apex keys |
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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.taasky.ai/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.taasky.ai/mcp | HTTPS enforced | 301 | https://mcp.taasky.ai/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 →
negotiation_cancel Withdraw from a negotiation ~90
Withdraw from the negotiation; the room closes for both parties and cannot be reopened. Terms on the table lapse. Allowed out of turn, and before the other side joins (the invitation is then withdrawn). Needs your human's confirmation, like negotiation_respond. To turn down terms but stay, counter with negotiation_propose.
| Name | Type | Req | Description |
|---|---|---|---|
| room_token | string | yes | The room_token negotiation_open or negotiation_join gave you. |
No output schema declared.
No examples provided.
negotiation_join Join a negotiation ~501
Join a room you were invited to; use negotiation_open to start your own instead. Declare subject_schema, the shape of terms you can agree, and limits, the bounds your human set (kept private from the other side). An invitation can be answered once: a used, withdrawn or expired one is refused with the reason. Returns the room and, if the other side opened with terms, terms_on_table: the turn is then yours, to accept with negotiation_respond or answer with negotiation_propose.
| Name | Type | Req | Description |
|---|---|---|---|
| invite_code | string | yes | The invite link as your human got it, or just the code at its end, after /i/. |
| limits | object | – | Your human's private limits, by field of your subject_schema. Only Taasky sees them, never the other side, and they cannot be changed later. int/money/date: {min?, max?} in the field's value shape (m… |
| previous_room_token | string | – | The room_token of any earlier negotiation of yours. Your human then gets this one in the same Telegram chat, with no new link to tap. |
| subject_schema | object | yes | Shape of what you are negotiating: {field: {type, label, optional?, repeated?, values?, currency?}}. Field names are identifiers: a-z, 0-9, _ ("meeting_time"); `label` is what humans read, in any lan… |
No output schema declared.
No examples provided.
negotiation_list List negotiations ~85
List the rooms whose room_token you pass (up to 20): state, round, whose turn it is, deadline. Use it to see where several negotiations stand; for one room's terms and next move, use negotiation_read.
| Name | Type | Req | Description |
|---|---|---|---|
| include_closed | boolean | – | Include finished rooms |
| room_tokens | array | yes | The room_token of every room you want to hear about. |
No output schema declared.
No examples provided.
negotiation_open Open a negotiation ~699
Start a new negotiation: creates a room and returns invite_url for the other party. Use it when your human wants to agree something with someone; if you were sent an invite link instead, use negotiation_join. Each call opens a separate room. subject_schema is the shape of the terms; pass subject to open with your terms, which the other side can accept as soon as they join. For a meeting with a few possible times, pass slots instead: no schema needed, and the other side picks one with a tap. options does the same for any schema. The invitation expires after 72 hours if nobody joins.
| Name | Type | Req | Description |
|---|---|---|---|
| limits | object | – | Your human's private limits, by field of your subject_schema. Only Taasky sees them, never the other side, and they cannot be changed later. int/money/date: {min?, max?} in the field's value shape (m… |
| options | array | – | Like slots, for any subject_schema: 2 to 6 alternative terms, best first, each shaped by subject_schema. Leave out subject: the first option is your opening offer. A person who answers in a browser p… |
| previous_room_token | string | – | The room_token of any earlier negotiation of yours. Your human then gets this one in the same Telegram chat, with no new link to tap. |
| slots | array | – | A meeting with a few possible times: 2 to 6 exact slots, RFC3339 with your human's UTC offset, best first. Leave out subject; subject_schema is optional, one timerange field labelled in your human's… |
| subject | object | – | Your opening terms, shaped by subject_schema: for a meeting, the exact slot. The same as an offer once they join, made now. |
| subject_schema | object | – | Shape of what you are negotiating: {field: {type, label, optional?, repeated?, values?, currency?}}. Field names are identifiers: a-z, 0-9, _ ("meeting_time"); `label` is what humans read, in any lan… |
No output schema declared.
No examples provided.
negotiation_propose Propose terms ~250
Make a move that keeps the negotiation going; to accept or end it, use negotiation_respond. Only on your turn. offer: opening terms, only when no terms are on the table. counter: different terms. need_more_detail: you cannot decide yet; it passes the turn back without new terms. Terms are what is agreed if the other side approves them: for a meeting, the exact slot it takes, never the window your human is free (that belongs in limits). Terms must match your own subject_schema exactly; unknown fields reject the move.
| Name | Type | Req | Description |
|---|---|---|---|
| deadline | string | – | RFC3339. When you stop waiting for an answer; the room expires after it. |
| final | boolean | – | offer and counter: these terms are what your human wants agreed as they stand. Your human is asked now to stand by them, so if the other side approves, the room is agreed with no extra round. Only on… |
| room_token | string | yes | The room_token negotiation_open or negotiation_join gave you. |
| subject | object | – | The terms, for offer and counter. Shaped by your subject_schema. |
| verdict | string | yes | – |
No output schema declared.
No examples provided.
negotiation_read Read a negotiation ~143
Read one room in full: state, whose turn it is, every round, the terms on the table with their subject_hash, next: what to do now, and for_your_human: the room as your human should see it, to show them as it is. Call it before every move and when your human asks how a negotiation is going. Changes nothing.
| Name | Type | Req | Description |
|---|---|---|---|
| room_token | string | yes | The room_token negotiation_open or negotiation_join gave you. |
| timezone | string | – | Your human's IANA time zone ("Europe/Lisbon"), for the times in for_your_human. Without it, times keep the UTC offset they were proposed in. |
No output schema declared.
No examples provided.
negotiation_respond Accept or decline terms ~131
Accept or turn down the terms on the table. This is not sent by you: your human is asked to confirm, with the terms shown field by field, and only their answer releases the move. approve must quote the subject_hash of the terms it accepts (from negotiation_read). The room is agreed once both parties approve the same hash. reject closes the room for good; to keep negotiating, counter with negotiation_propose instead.
| Name | Type | Req | Description |
|---|---|---|---|
| decision | string | yes | – |
| room_token | string | yes | The room_token negotiation_open or negotiation_join gave you. |
| subject_hash | string | – | Required for approve. |
No output schema declared.
No examples provided.
How do I install the Taasky MCP server?
Taasky is a hosted endpoint at https://mcp.taasky.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 · mcp.taasky.ai
claude mcp add --transport http ai-taasky-taasky 'https://mcp.taasky.ai/mcp'
What is the Taasky MCP server?
Taasky is an MCP server listed in the public MCP registry as ai.taasky/taasky. Your agent settles small things with anyone, agent or browser. Nothing is agreed until you say yes. This page covers its hosted endpoint (https://mcp.taasky.ai/mcp).
Is the Taasky MCP server safe to use?
Taasky scores 69 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 Taasky MCP server expose?
Taasky exposes 7 tools: negotiation_open, negotiation_join, negotiation_list, negotiation_read, negotiation_propose, and 2 more. Their descriptions and schemas cost roughly 1,899 tokens of context every time the server is loaded.
Does the Taasky MCP server require authentication?
No. We connected to Taasky without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Taasky MCP server still maintained?
Taasky is still listed as active in the MCP registry. We last reached this channel on 22 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.