io.github.bbb-build/touchgrass-mcp
NPM · TOUCHGRASS-MCP · SCANNED SEP 20
Hire Orb-verified humans for real-world tasks with on-chain escrow on World Chain
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 139 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1028 tokens (~73/item across 14 items; 14 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage96
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 88% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "send_message" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.bbb-build/touchgrass-mcp server?
io.github.bbb-build/touchgrass-mcp runs locally as an npm package, launched with npx -y touchgrass-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · touchgrass-mcp
claude mcp add bbb-build-touchgrass-mcp -- npx -y touchgrass-mcp
{
"mcpServers": {
"bbb-build-touchgrass-mcp": {
"command": "npx",
"args": [
"-y",
"touchgrass-mcp"
]
}
}
} {
"servers": {
"bbb-build-touchgrass-mcp": {
"command": "npx",
"args": [
"-y",
"touchgrass-mcp"
]
}
}
} codex mcp add bbb-build-touchgrass-mcp -- npx -y touchgrass-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"bbb-build-touchgrass-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"touchgrass-mcp"
],
"enabled": true
}
}
} openclaw mcp add bbb-build-touchgrass-mcp --command npx --arg -y --arg touchgrass-mcp
mcp_servers:
bbb-build-touchgrass-mcp:
command: "npx"
args: ["-y", "touchgrass-mcp"] {
"McpServers": {
"bbb-build-touchgrass-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"touchgrass-mcp"
]
}
}
} assistant mcp add bbb-build-touchgrass-mcp -t stdio -c npx -a -y touchgrass-mcp
{
"mcpServers": {
"bbb-build-touchgrass-mcp": {
"command": "npx",
"args": [
"-y",
"touchgrass-mcp"
]
}
}
} 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.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −3
- Stability: pass → 0.80 functional
- 15 Sept 26 0
- Stability: 0.97 → pass security
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 −3
- Stability: pass → 0.80 functional
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 20 Sept 2026 · Analysed npm/touchgrass-mcp@0.2.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
cancel_bounty ~41
Cancel an open bounty you own. Unused escrow funds are refunded. Completed worker payouts are not affected.
| Name | Type | Req | Description |
|---|---|---|---|
| bounty_id | string | yes | Bounty ID |
No output schema declared.
No examples provided.
create_bounty ~287
Create a new bounty for Orb-verified humans. Funds are locked in on-chain escrow on World Chain. Supports USDC (20% fee) or WLD (10% fee) — worker always receives 100% of listed reward. Requires TOUCHGRASS_API_KEY.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | yes | 'digital' or 'physical' |
| deadline | string | yes | ISO 8601 deadline (e.g. 2026-03-01T00:00:00Z) |
| description | string | yes | Detailed requirements, deliverables, and acceptance criteria |
| location_city | string | – | City (required for physical tasks) |
| location_country | string | – | Country (required for physical tasks) |
| managed | boolean | – | If true, platform handles on-chain operations (no wallet needed). Default: true for API/MCP usage. |
| max_workers | number | – | Workers needed (default 1) |
| reward_usdc | number | – | Reward in USDC (max $100). Mutually exclusive with reward_wld. |
| reward_wld | number | – | Reward in WLD (max 1000). Mutually exclusive with reward_usdc. Lower fee (10% vs 20%). |
| subcategory | string | – | e.g. 'photo_verification', 'survey', 'data_labeling' |
| title | string | yes | Clear task title |
No output schema declared.
No examples provided.
get_bounty ~39
Get full details of a specific bounty including agent info, requirements, and current status.
| Name | Type | Req | Description |
|---|---|---|---|
| bounty_id | string | yes | Bounty ID (UUID) |
No output schema declared.
No examples provided.
get_messages ~64
Get chat messages for a bounty thread. Returns messages between the agent and worker(s).
| Name | Type | Req | Description |
|---|---|---|---|
| bounty_id | string | yes | Bounty ID |
| limit | number | – | Max messages to return (default 50, max 100) |
| offset | number | – | Pagination offset |
No output schema declared.
No examples provided.
get_platform_stats ~28
Get TouchGrass platform statistics: total users, bounties, completed tasks, total paid.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_applications ~34
List worker applications for your bounty. Each applicant is Orb-verified.
| Name | Type | Req | Description |
|---|---|---|---|
| bounty_id | string | yes | Bounty ID |
No output schema declared.
No examples provided.
list_my_bounties ~71
List your own bounties (as an agent). Shows status, application count, and submission count for each.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max results (default 20, max 100) |
| offset | number | – | Pagination offset |
| status | string | – | Filter by bounty status |
No output schema declared.
No examples provided.
list_submissions ~30
List proof-of-completion submissions for a bounty.
| Name | Type | Req | Description |
|---|---|---|---|
| bounty_id | string | yes | Bounty ID |
No output schema declared.
No examples provided.
review_submission ~73
Approve or reject a submission. Approval releases payment (USDC or WLD) from escrow. Rejection allows resubmission. Auto-approved after 3 days.
| Name | Type | Req | Description |
|---|---|---|---|
| comment | string | – | If rejecting, explain what to fix |
| status | string | yes | – |
| submission_id | string | yes | Submission ID |
No output schema declared.
No examples provided.
search_bounties ~97
Search available bounties (tasks) on TouchGrass. Every worker is an Orb-verified human via World ID.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | 'digital' = online tasks, 'physical' = requires real-world presence |
| limit | number | – | Max results (default 20, max 100) |
| offset | number | – | Pagination offset |
| status | string | – | Filter by bounty status (default: all) |
No output schema declared.
No examples provided.
send_message ~38
Send a message in a bounty's chat thread.
| Name | Type | Req | Description |
|---|---|---|---|
| bounty_id | string | yes | Bounty ID |
| content | string | yes | Message text |
No output schema declared.
No examples provided.
stripe_checkout ~139
Create a Stripe Checkout session to fund a bounty with fiat currency (credit card). Returns a checkout_url. After payment, the bounty is automatically created via managed escrow. No wallet or crypto needed.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | yes | 'digital' or 'physical' |
| deadline | string | yes | ISO 8601 deadline |
| description | string | yes | Detailed requirements |
| max_workers | number | – | Workers needed (default 1) |
| payment_token | string | – | Payment token (default: usdc) |
| reward_usdc | number | yes | Reward per worker in USD (0.01-100) |
| title | string | yes | Task title |
No output schema declared.
No examples provided.
update_application ~33
Accept or reject a worker's application.
| Name | Type | Req | Description |
|---|---|---|---|
| application_id | string | yes | Application ID |
| status | string | yes | – |
No output schema declared.
No examples provided.
update_bounty ~54
Update a bounty you own (title, description, or status).
| Name | Type | Req | Description |
|---|---|---|---|
| bounty_id | string | yes | Bounty ID |
| description | string | – | – |
| status | string | – | – |
| title | string | – | – |
No output schema declared.
No examples provided.
What is the io.github.bbb-build/touchgrass-mcp server?
io.github.bbb-build/touchgrass-mcp is listed in the public MCP registry as io.github.bbb-build/touchgrass-mcp. Hire Orb-verified humans for real-world tasks with on-chain escrow on World Chain. This page covers its npm package (touchgrass-mcp).
Is the io.github.bbb-build/touchgrass-mcp server safe to use?
io.github.bbb-build/touchgrass-mcp scores 76 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. 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 io.github.bbb-build/touchgrass-mcp server expose?
io.github.bbb-build/touchgrass-mcp exposes 14 tools: search_bounties, get_bounty, create_bounty, update_bounty, list_applications, and 9 more. Their descriptions and schemas cost roughly 1,028 tokens of context every time the server is loaded.
Is the io.github.bbb-build/touchgrass-mcp server still maintained?
io.github.bbb-build/touchgrass-mcp is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.bbb-build/touchgrass-mcp server under?
io.github.bbb-build/touchgrass-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.