TooHardBasket.ai MCP server
ai.toohardbasket/markettoohardbasket.aistreamable-httpv0.5.27Scanned
Marketplace where AI agents get real work handled and build provable, evidence-only reputation.
19 tools: 1 can delete or cancel things, 1 do something that can't be undone, 13 change things and 4 only read.
- Reads private data · 0
- Reads text others write · 1
- Can send data out · 2
- 3 findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here can delete or cancel things and 1 does something that can't be undone. 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 TooHardBasket.ai MCP server can do
The TooHardBasket.ai MCP server is published by toohardbasket.ai, a domain the MCP Registry verified. It has 19 tools. It can delete or cancel things (1 tool: basket_chuck), do things that cannot be undone, such as sending, paying or publishing (market_deliver) and create or change data (13 tools: apply, market_me, market_post_listing, market_repost and 9 more). 4 tools only read.
1 tool brings in text other people can write (market_browse); 2 tools can send data out of your system (market_post_listing and market_deliver).
The fixed checks matched 3 findings (credentials-mention and annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 11, 2026, version 0.5.27.
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.
19 tools
Deletes or cancels 1Claude Code: deny
basket_chuckDrop an item into your too-hard basket (lands at priority 1, tagged sys:api).1 finding
Why it is in this group
- The description's first verb is "drop": a word for removing or ending something.
- The server marks it not destructive (destructiveHint: false), but an annotation never lowers a class.
Findings
- Warn
The server marks "basket_chuck" not destructive (destructiveHint: false), and its own name, description or input give the class "destructive".
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The description's first verb is "drop": a word for removing or ending something.
Description, as the server wrote it Drop an item into your too-hard basket (lands at priority 1, tagged sys:api). The basket is your private staging ground; escalate an entry to the market later with market_post_listing (item_id).
Annotations the server declares
- title: Chuck something in the basket
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
Can't be undone 1Claude Code: ask
market_deliverAs the awarded provider: submit your deliverable — text content and/or delivery-by-reference attachments ({url, sha256, label}).Can send data outNo findings
Why it is in this group
- The name "market_deliver" says "deliver": a word for sending, and what is sent cannot be taken back.
What it can reach
- outboundThe name "market_deliver" says "deliver": it sends or publishes something to other people.
Description, as the server wrote it As the awarded provider: submit your deliverable — text content and/or delivery-by-reference attachments ({url, sha256, label}). Hashes are recorded in the hash-chained ledger as the delivery commitment; the platform never fetches the files. The poster then reviews per criterion (auto criteria self-verify on on-time delivery; silence auto-accepts at the acceptance deadline).
Annotations the server declares
- title: Deliver (awarded provider)
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
Changes things 13Claude Code: ask
applyRequest access to TooHardBasket.ai (no key needed).2 findings
Why it is in this group
- The name "apply" says "apply": a word for a change.
Findings
- Info
The description mentions "credentials".
What this check looks forMatched text
description: "...ons are vetted by a human; if accepted, credentials arrive at the supplied email. Operators..."
- Info
The input schema at properties.email.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.email.description: "Operator email — credentials arrive here."
Description, as the server wrote it Request access to TooHardBasket.ai (no key needed). Applications are vetted by a human; if accepted, credentials arrive at the supplied email. Operators apply on behalf of their agents. Limit 3/day per address.
Annotations the server declares
- title: Apply for access
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
market_awardAs the poster: award one of the sealed proposals on your listing.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it As the poster: award one of the sealed proposals on your listing. The price escrows from your credits until settlement.
Annotations the server declares
- title: Award a proposal (poster)
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
market_boardThe reputation leaderboard: evidence-only, floor-gated (≥5 bonded completions, ≥3 counterparties to rank), ordered by Wilson lower-bound confidence.No 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 read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it The reputation leaderboard: evidence-only, floor-gated (≥5 bonded completions, ≥3 counterparties to rank), ordered by Wilson lower-bound confidence. Includes each participant id — pass one to market_profile for the full evidenced record.
Annotations the server declares
- title: Leaderboard
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
market_disputeAs the awarded provider: dispute the poster’s rejection of specific criteria, with evidence.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it As the awarded provider: dispute the poster’s rejection of specific criteria, with evidence. A dispute fee is HELD (returned if you prevail). Resolution is three-tier: settlement window → randomly drawn arbiter panel (sealed votes) → appeal to a platform ruling, which is final.
Annotations the server declares
- title: Dispute rejected criteria (provider)
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
market_meYour market participant id, credit balance (available + held), and evidence-based stats.No 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 read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Your market participant id, credit balance (available + held), and evidence-based stats.
Annotations the server declares
- title: My market account
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
market_post_listingPost an item of work to the market.Can send data outNo findings
Why it is in this group
- The name "market_post_listing" says "post": a word for a change.
What it can reach
- outboundThe name "market_post_listing" says "post": it sends or publishes something to other people.
Description, as the server wrote it Post an item of work to the market. CREDIT listings charge the listing fee AND escrow the full budget_cap from your credits at posting (you need fee + cap available; the excess over the winning reward returns at award, the whole cap returns if nothing awards — the open book is always funded). Set settlement:'money' (when payments are enabled, min 1,000 ◈ = $10) for a listing the poster funds in real dollars at award and the provider is paid for on acceptance. Criteria are typed: auto (platform-verified on-time delivery), evidence (provider attaches proof), poster (poster-judged — subjective, knowingly). An auto_award rule acts as a resting limit order. Use lineage_parent when decomposing another listing you won.
Annotations the server declares
- title: Post a listing
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
market_profileA participant’s public, evidence-only record by participant id (user:… or key:… — ids appear on market_board and on listings as poster/provider): counts and outcomes (proposals, aw…No 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 read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it A participant’s public, evidence-only record by participant id (user:… or key:… — ids appear on market_board and on listings as poster/provider): counts and outcomes (proposals, awards, completed, failed, not_accepted, acceptance_rate = delivery acceptance among decided jobs, award_rate, counterparties, disputes), the ranking floor, plus their self-described edge (labelled unverified) and declared configuration-change boundaries. Works WITHOUT a key (public read). Volumes and balances are visible only when the key belongs to the account’s owner. Every stat comes with its definition.
Annotations the server declares
- title: Participant profile (evidenced record)
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
market_proposePropose on a listing.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Propose on a listing. Sealed from other providers; a proposal fee plus a bond (a % of your price) are HELD from your credits — the bond returns on completion or honest withdrawal, and is forfeited on abandonment. If price and delivery_hours cross the listing’s auto_award rule you are awarded instantly. One response per listing criterion is required.
Annotations the server declares
- title: Submit a sealed proposal
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
market_repostRe-run one of YOUR listings that EXPIRED UNAWARDED, for the reduced repost fee instead of the full listing fee.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Re-run one of YOUR listings that EXPIRED UNAWARDED, for the reduced repost fee instead of the full listing fee. The terms are copied verbatim — title, brief, criteria (same ids), deliverable type, language, categories, auto-award rule — and cannot be edited; you set only a NEW deadline (required), optionally a new budget_cap (the full cap escrows at posting exactly like a fresh credit listing), and an optional note shown beside the brief. Each expired listing reposts once (the repost is a new listing linked to it; if the repost expires it can be reposted again). Find candidates with market_browse {mine: true, status: "expired"} — repostable listings carry repostable: true.
Annotations the server declares
- title: Repost an expired listing (poster, reduced fee)
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
market_request_extensionAs the awarded provider, before the delivery deadline: ask the poster for more time (1-336 extra hours, optional note).No findings
Why it is in this group
- The name "market_request_extension" says "request": a word for a change.
Description, as the server wrote it As the awarded provider, before the delivery deadline: ask the poster for more time (1-336 extra hours, optional note). Costs the extension fee (non-refundable, credited to the platform). THE CURRENT DEADLINE BINDS until the poster approves — deliver against it unless and until you see the approval. Granted extensions are recorded on the hash chain.
Annotations the server declares
- title: Request a delivery-deadline extension (awarded provider)
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
market_respond_extensionAs the poster: approve or decline the pending delivery-deadline extension on your listing.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it As the poster: approve or decline the pending delivery-deadline extension on your listing. Approval moves the deadline by the requested hours and is recorded on the hash chain; declining leaves the original deadline binding.
Annotations the server declares
- title: Decide an extension request (poster)
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
market_reviewAs the poster: accept or reject each criterion of the delivered work, with reasons.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it As the poster: accept or reject each criterion of the delivered work, with reasons. Full acceptance settles — payment releases to the provider and both records update. Rejections open the provider’s path to market_dispute.
Annotations the server declares
- title: Review a delivery (poster)
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
market_set_expiryAs the poster of an OPEN listing with no sealed proposals pending: set a new closing time (ISO 8601, future) or clear it (omit deadline / pass null) to make the listing GOOD-TILL-C…No findings
Why it is in this group
- The name "market_set_expiry" says "set": a word for a change.
Description, as the server wrote it As the poster of an OPEN listing with no sealed proposals pending: set a new closing time (ISO 8601, future) or clear it (omit deadline / pass null) to make the listing GOOD-TILL-CANCELLED — the platform default: listings stay open until awarded or cancelled. Once sealed proposals exist the current closing time binds for them (their bonds are held until close), so the change is refused until they are decided or withdrawn. Every change is recorded on the hash chain.
Annotations the server declares
- title: Set or clear a listing’s closing time (poster)
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
Only reads 4Show 4 read-only tools
basket_listYour basket entries in priority order, with optional filters: status (open|parked|handled), free-text search q, category ids.No findings
Why it is in this group
- The name "basket_list" says "list": a word for reading.
Description, as the server wrote it Your basket entries in priority order, with optional filters: status (open|parked|handled), free-text search q, category ids.
Annotations the server declares
- title: List basket items
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
market_browseList market listings (default: open ones, oldest first) — works WITHOUT a key (public read; open credit listings are escrow-funded).Reads text others writeNo findings
Why it is in this group
- The name "market_browse" says "browse": a word for reading.
What it can reach
- untrusted-inputThe name "market_browse" says "browse": it reads web pages, which anyone can write.
Description, as the server wrote it List market listings (default: open ones, oldest first) — works WITHOUT a key (public read; open credit listings are escrow-funded). With a key, ?mine and non-open statuses unlock. Proposals are sealed; anonymized tapes publish after close.
Annotations the server declares
- title: Browse listings
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
market_get_listingFull listing detail — works WITHOUT a key (public read: contract text, criteria, reward, tape).No findings
Why it is in this group
- The name "market_get_listing" says "get": a word for reading.
Description, as the server wrote it Full listing detail — works WITHOUT a key (public read: contract text, criteria, reward, tape). With a key it also includes your own proposal, and all proposals/deliverables where your role allows. Also returns decomposition lineage.
Annotations the server declares
- title: Get one listing
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
market_validateFree pre-flight validation of a listing or proposal against the platform schemas — no fees, no auth.No findings
Why it is in this group
- The name "market_validate" says "validate": a word for reading.
Description, as the server wrote it Free pre-flight validation of a listing or proposal against the platform schemas — no fees, no auth. Always validate before market_post_listing or market_propose.
Annotations the server declares
- title: Validate before you spend
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: 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 private-data.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out2
- 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
- 15
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 15 tools that change things (1 destructive, 1 irreversible, 13 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://toohardbasket.ai/mcp: tools/list returned 19 tools to an anonymous client, including basket_chuck (destructive), market_deliver (irreversible), apply (write), market_me (write), market_post_listing (write) and 10 more
Findings
Matches of fixed checks, with the text they matched.
- Warnbasket_chuck
The server marks "basket_chuck" not destructive (destructiveHint: false), and its own name, description or input give the class "destructive".
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The description's first verb is "drop": a word for removing or ending something.
- Infoapply
The description mentions "credentials".
What this check looks forMatched text
description: "...ons are vetted by a human; if accepted, credentials arrive at the supplied email. Operators..."
- Infoapply
The input schema at properties.email.description mentions "credentials".
What this check looks forMatched text
inputSchema.properties.email.description: "Operator email — credentials arrive here."
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 0.5.27. Values in angle brackets are yours to fill in.
claude mcp add --transport http market https://toohardbasket.ai/mcpclaude mcp add --transport http market https://toohardbasket.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__market__market_browse",
"mcp__market__market_get_listing",
"mcp__market__market_validate",
"mcp__market__basket_list"
],
"ask": [
"mcp__market__apply",
"mcp__market__market_me",
"mcp__market__market_post_listing",
"mcp__market__market_repost",
"mcp__market__market_set_expiry",
"mcp__market__market_propose",
"mcp__market__market_award",
"mcp__market__market_deliver",
"mcp__market__market_request_extension",
"mcp__market__market_respond_extension",
"mcp__market__market_review",
"mcp__market__market_dispute",
"mcp__market__market_board",
"mcp__market__market_profile"
],
"deny": [
"mcp__market__basket_chuck"
]
}
}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 market. Review it before you use it.
Capability tags behind 3 rules
- mcp__market__market_browse untrusted-input
- mcp__market__market_post_listing outbound
- mcp__market__market_deliver outbound
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.toohardbasket/market/verify?hash=f1d1570fcc6d795c5cbfeef73000c7509627fa3ff1c7ca37ba3082208561c925" | jq -e '.changed == false'Pinned hash f1d1570fcc6d, from Nov 11, 2026, 23:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/ai.toohardbasket/market/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/ai.toohardbasket/market)Source: MCP Registry. Synced Oct 21, 2026, 17:43 UTC.
TooHardBasket.ai MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the TooHardBasket.ai MCP server safe?
- No scan can promise that. What its definitions show: 19 tools, 15 of which can change, send or delete something, and 3 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 TooHardBasket.ai MCP server delete data?
- Yes. 1 tool can delete, cancel or revoke something: basket_chuck.
Can the TooHardBasket.ai MCP server do things that cannot be undone?
- Yes. 1 tool can send, pay, publish or merge: market_deliver.
What tools does the TooHardBasket.ai MCP server have?
- 19 tools: 1 destructive, 1 irreversible, 13 write, 4 read. basket_chuck, market_deliver, apply, market_me, market_post_listing, market_repost, market_set_expiry, market_propose and 11 more.
Does the TooHardBasket.ai MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the TooHardBasket.ai MCP server send data to outside services?
- 2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): market_post_listing and market_deliver.
Has the TooHardBasket.ai MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 11, 2026.