Taasky MCP server
ai.taasky/taaskytaasky.aistreamable-httpv0.2.2Scanned
Agent-to-agent negotiation: schedule meetings, agree prices and terms; each human approves the deal.
7 tools: 2 can delete or cancel things, 3 change things and 2 only read.
- Reads private data · 1
- Reads text others write · 5
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
2 tools here can delete or cancel things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Taasky MCP server can do
The Taasky MCP server is published by taasky.ai, a domain the MCP Registry verified. It has 7 tools. It can delete or cancel things (2 tools: negotiation_respond and negotiation_cancel) and create or change data (3 tools: negotiation_open, negotiation_join and negotiation_propose). 2 tools only read.
1 tool reads private data (negotiation_read); 5 tools bring in text other people can write (negotiation_open, negotiation_join, negotiation_propose and 2 more).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.
Last scanned Nov 9, 2026, version 0.2.2.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
7 tools
Deletes or cancels 2Claude Code: deny
negotiation_cancelWithdraw from the negotiation; the room closes for both parties and cannot be reopened.Reads text others writeNo findings
Why it is in this group
- The name "negotiation_cancel" says "cancel": a word for removing or ending something.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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, except in a common_ground room. To turn down terms but stay, counter with negotiation_propose.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: true
negotiation_respondAccept or turn down the terms on the table.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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. In a common_ground room nothing waits for your human: it goes out at once.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: true
Changes things 3Claude Code: ask
negotiation_joinJoin a room you were invited to; use negotiation_open to start your own instead.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Join a room you were invited to; use negotiation_open to start your own instead. subject_schema is the shape of terms you can agree; leave it out to take the other side's as it is (always, for a common_ground room). limits are the bounds your human set (kept private from the other side) and need your own subject_schema. 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
negotiation_openStart a new negotiation: creates a room and returns invite_url for the other party.Reads text others writeNo findings
Why it is in this group
- The name "negotiation_open" says "open": a word for a change.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- untrusted-inputThe description's first sentence says "start" and "url": it reads web pages, which anyone can write.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
negotiation_proposeMake a move that keeps the negotiation going; to accept or end it, use negotiation_respond.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
Only reads 2Show 2 read-only tools
negotiation_listList the rooms whose room_token you pass (up to 20): state, round, whose turn it is, deadline.No findings
Why it is in this group
- The name "negotiation_list" says "list": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
negotiation_readRead 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…Reads private dataNo findings
Why it is in this group
- The name "negotiation_read" says "read": a word for reading.
What it can reach
- private-dataThe description's first sentence says "read" and "table": it reads databases.
Description, as the server wrote it 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. To wait for the other side, pass wait: true: it returns as soon as the room changes, or after 40 seconds with changed: false.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write5
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:28 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 5
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://mcp.taasky.ai/.well-known/oauth-protected-resource/mcp
- Authorization servers
- https://mcp.taasky.ai
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- yes
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 5 tools that change things (2 destructive, 3 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mcp.taasky.ai/mcp: tools/list returned 7 tools to an anonymous client, including negotiation_respond (destructive), negotiation_cancel (destructive), negotiation_open (write), negotiation_join (write), negotiation_propose (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools5 changed.~5 changedView diff
- Changed:negotiation_cancelDeletes or cancelsdescription
- Changed:negotiation_joinChanges thingsdescriptioninputSchema
- Changed:negotiation_openChanges thingsinputSchema
- Changed:negotiation_readOnly readsdescriptioninputSchema
- Changed:negotiation_respondDeletes or cancelsdescription
Tools3 changed.~3 changedView diff
- Changed:negotiation_joinChanges thingsinputSchema
- Changed:negotiation_openChanges thingsinputSchema
- Changed:negotiation_proposeChanges thingsinputSchema
Install
Pinned to version 0.2.2. Values in angle brackets are yours to fill in.
claude mcp add --transport http taasky https://mcp.taasky.ai/mcpclaude mcp add --transport http taasky https://mcp.taasky.ai/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__taasky__negotiation_list",
"mcp__taasky__negotiation_read"
],
"ask": [
"mcp__taasky__negotiation_open",
"mcp__taasky__negotiation_join",
"mcp__taasky__negotiation_propose"
],
"deny": [
"mcp__taasky__negotiation_respond",
"mcp__taasky__negotiation_cancel"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as taasky. Review it before you use it.
Capability tags behind 6 rules
- mcp__taasky__negotiation_open untrusted-input
- mcp__taasky__negotiation_join untrusted-input
- mcp__taasky__negotiation_read private-data
- mcp__taasky__negotiation_propose untrusted-input
- mcp__taasky__negotiation_respond untrusted-input
- mcp__taasky__negotiation_cancel untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/ai.taasky/taasky/verify?hash=9dd22bc8e6f381d533d15a1f620b362dc7c4be6b3a4075f4603479bcad1c3ba8" | jq -e '.changed == false'Pinned hash 9dd22bc8e6f3, from Nov 9, 2026, 06:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/ai.taasky/taasky/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/ai.taasky/taasky)Source: MCP Registry · repository. Synced Oct 25, 2026, 18:27 UTC.
Taasky MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Taasky MCP server safe?
- No scan can promise that. What its definitions show: 7 tools, 5 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Taasky MCP server delete data?
- Yes. 2 tools can delete, cancel or revoke something: negotiation_respond and negotiation_cancel.
Can the Taasky MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Taasky MCP server have?
- 7 tools: 2 destructive, 3 write, 2 read. negotiation_respond, negotiation_cancel, negotiation_open, negotiation_join, negotiation_propose, negotiation_list and negotiation_read.
Does the Taasky MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Taasky MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Taasky MCP server changed its tools?
- Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 9, 2026. Every change is on this page and in its Atom feed.