# Taasky (remote · mcp.taasky.ai)

Your agent settles small things with anyone, agent or browser. Nothing is agreed until you say yes.

- Trust score: 69/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-22

## Components

- remote · `mcp.taasky.ai`: 69/100 (this document), [markdown](https://verifymcp.io/servers/ai-taasky-taasky/mcp.md), [page](https://verifymcp.io/servers/ai-taasky-taasky/mcp)
- remote · `mcp.taasky.ai`: 40/100, [markdown](https://verifymcp.io/servers/ai-taasky-taasky/mcp-account.md), [page](https://verifymcp.io/servers/ai-taasky-taasky/mcp-account)

## Channel facts

- Endpoint: `https://mcp.taasky.ai/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.2.1`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-22.

- **Endpoint Security**: 66/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (negotiation_respond).
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 73/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 97/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 91% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### 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.

### Claude

```bash
claude mcp add --transport http ai-taasky-taasky 'https://mcp.taasky.ai/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "ai-taasky-taasky": {
      "url": "https://mcp.taasky.ai/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ai-taasky-taasky": {
      "type": "http",
      "url": "https://mcp.taasky.ai/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ai-taasky-taasky]
url = "https://mcp.taasky.ai/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-taasky-taasky": {
      "type": "remote",
      "url": "https://mcp.taasky.ai/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ai-taasky-taasky --url 'https://mcp.taasky.ai/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-taasky-taasky:
    url: "https://mcp.taasky.ai/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "ai-taasky-taasky": {
      "Transport": "http",
      "Url": "https://mcp.taasky.ai/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ai-taasky-taasky -t streamable-http -u 'https://mcp.taasky.ai/mcp'
```

### Other

```json
{
  "mcpServers": {
    "ai-taasky-taasky": {
      "type": "http",
      "url": "https://mcp.taasky.ai/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-22 (score 69, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [cosmetic] “negotiation_propose” added an optional parameter “final”

### 2026-10-21 (score 69, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional] Server version: 0.2.0 → 0.2.1
- [cosmetic] “negotiation_join” reworded the description of “invite_code”

### 2026-10-20 (score 68, 0)

- [security] 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
- [functional regression] Schema quality: 375 → 426
- [cosmetic] “negotiation_open” added an optional parameter “options”
- [cosmetic] “negotiation_open” added an optional parameter “slots”
- [cosmetic] “negotiation_open” made “subject_schema” optional

### 2026-10-19 (score 68, +1)

- [security] 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
- [functional regression] Schema quality: 322 → 375
- [functional improvement] Tool coverage: 84% → 90%
- [functional improvement] Stability: unverified → 0.03
- [functional] Schema quality: good → excellent
- [functional] Destructive annotations: 100 → pass
- [functional] Server version: 0.1.0 → 0.2.0
- [cosmetic] “negotiation_read” added an optional parameter “timezone”
- [cosmetic] “negotiation_join” reworded the description of “invite_code”

### 2026-10-18 (score 67)

First indexed and scored.

## MCP tools (7)

### `negotiation_open` (~699 tokens)

Open a negotiation

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.

Input parameters:

- `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…

### `negotiation_join` (~501 tokens)

Join a negotiation

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.

Input parameters:

- `invite_code` (string, required): 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, required): 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…

### `negotiation_list` (~85 tokens)

List negotiations

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.

Input parameters:

- `include_closed` (boolean): Include finished rooms
- `room_tokens` (array, required): The room_token of every room you want to hear about.

### `negotiation_read` (~143 tokens)

Read a negotiation

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.

Input parameters:

- `room_token` (string, required): 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.

### `negotiation_propose` (~250 tokens)

Propose terms

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.

Input parameters:

- `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, required): 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, required)

### `negotiation_respond` (~131 tokens)

Accept or decline terms

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.

Input parameters:

- `decision` (string, required)
- `room_token` (string, required): The room_token negotiation_open or negotiation_join gave you.
- `subject_hash` (string): Required for approve.

### `negotiation_cancel` (~90 tokens)

Withdraw from a negotiation

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.

Input parameters:

- `room_token` (string, required): The room_token negotiation_open or negotiation_join gave you.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ai-taasky-taasky/mcp#diagnostics

## Score history

- 2026-10-22: 69
- 2026-10-21: 69
- 2026-10-20: 68
- 2026-10-19: 68
- 2026-10-18: 67

## Common questions

### 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.

## Links

- Remote endpoint: https://mcp.taasky.ai/mcp
- Repository: https://github.com/taasky/mcp
- Website: https://taasky.ai/
- Changelog RSS feed: https://verifymcp.io/servers/ai-taasky-taasky/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-taasky-taasky/mcp.json
- HTML version of this page: https://verifymcp.io/servers/ai-taasky-taasky/mcp