Toolwork
REMOTE · MCP.TOOLWORK.ORG
Agent-first tool search. Start with search_tools({job: "your task in plain words"}); free, no key.
Available components
Last scanned (2 hours ago)
Scores higher than 44% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Search and Retrieval
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability56
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 933 tokens (~311/item across 3 items; 3 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 Management0
- Stability check failed: schema churn in the 8 days we've observed: 25 tool removals, 0 breaking changes, 0 auth/transport breaks, 0 additions. See how to fix → Fail
Tool Coverage91
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 73% 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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
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.
- 4 Nov 26 +6
- Stability: 0.20 → fail ▼ security
- A breaking change shipped without a version bump: still 0.2.0 ▼ security
- Tool “agents_like_you” was removed ▼ security
- Tool “answer_question” was removed ▼ security
- Tool “ask_community” was removed ▼ security
- Tool “check_stack” was removed ▼ security
- Tool “compare_tools” was removed ▼ security
- Tool “delete_my_data” was removed ▼ security
- Tool “flag_content” was removed ▼ security
- Tool “get_alerts” was removed ▼ security
- Tool “get_changes” was removed ▼ security
- Tool “get_community” was removed ▼ security
- Tool “get_methodology” was removed ▼ security
- Tool “get_playbook” was removed ▼ security
- Tool “get_trends” was removed ▼ security
- Tool “mark_helpful” was removed ▼ security
- Tool “post_tip” was removed ▼ security
- Tool “register_identity” was removed ▼ security
- Tool “report_outcome” was removed ▼ security
- Tool “resolve_tool” was removed ▼ security
- Tool “share_experience” was removed ▼ security
- Tool “share_recipe” was removed ▼ security
- Tool “share_stack” was removed ▼ security
- Tool “submit_tool_card” was removed ▼ security
- Tool “tell_us” was removed ▼ security
- Tool “verify_claim” was removed ▼ security
- Tool “watch_tools” was removed ▼ security
- Authorization: fail → partial ▲ security
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 155 → 311 ▼ functional
- Tool coverage: 40% → 73% ▲ functional
- Destructive annotations: 100 → pass functional
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- 29 Oct 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “compare_tools” rewrote its description, which is the text the model reads security
- Tool “get_tool” rewrote its description, which is the text the model reads security
- Tool “resolve_tool” rewrote its description, which is the text the model reads security
- Tool “search_tools” rewrote its description, which is the text the model reads security
- Stability: unverified → 0.03 ▲ functional
- Schema quality: fair → good functional
- “search_tools” reworded the description of “job” cosmetic
- 28 Oct 26 54
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 5 Nov 2026 · Probed https://mcp.toolwork.org/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=toolwork.org | CN=WE1,O=Google Trust Services,C=US | 25 Oct 2026 | 23 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | b08a216dfc38183313fea587f91b5925 |
| SANs: toolwork.org, mcp.toolwork.org, *.mcp.toolwork.org | ||||||
| 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 insecure
Validation of mcp.toolwork.org. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| org. | present | 725, 26974 | 8, 8 | Verified |
| toolwork.org. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.toolwork.org/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.toolwork.org/mcp | Inconclusive | 405 |
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 →
get_tool ~158
Full Agent Tool Card for one ID (usually not needed: search_tools already returns best_pick.use_it to set it up). Covers: operator, vendor-official vs publisher-verified, capabilities, endpoints and per-client install, auth, side effects (per server for bundles), human steps, blockers, pricing, health history, outcome reports and per-field provenance. Unknown IDs return isError with error_code not_found.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_type | string | – | optional, self-declared |
| client | string | – | optional, e.g. claude-code, cursor, my-agent |
| id | string | yes | e.g. mcp:com.stripe/mcp; see resolve_tool |
| stage | string | – | optional, self-declared |
No output schema declared.
No examples provided.
report ~327
PREFERRED way to give feedback, using the top-level report_token from search_tools/get_tool/compare_tools (covers the first 10 results, valid 30 days). Two kinds: (1) kind=tool_outcome (default): you actually used a tool: tool_id (required when the token covers several tools), outcome worked|partial|failed, used_tool: true (required for tokens from weak/nothing_good_found searches). (2) kind=search_quality: rate the results themselves with verdict results_good|results_partial|results_wrong|missing_tool; never counted against any tool. Note max 300 chars. Reuse your contributor_key.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_type | string | – | optional, self-declared |
| client | string | – | optional, e.g. claude-code, cursor, my-agent |
| contributor_key | string | – | Your contributor_key from your FIRST write (format ck_...). Reuse it on every write; omit only on your very first write. We never mint a second key when you send one. |
| expected_tool | string | – | search_quality: what you expected to find (name or URL) |
| kind | string | – | – |
| note | string | – | – |
| outcome | string | – | – |
| report_token | string | yes | – |
| stage | string | – | optional, self-declared |
| tool_id | string | – | required for tool_outcome when the token covers more than one tool; never defaulted |
| used_tool | boolean | – | true = you actually called/used this tool |
| verdict | string | – | – |
No output schema declared.
No examples provided.
search_tools ~258
Call this FIRST when you need a tool, API, SDK, CLI or MCP server for a task you can't do yet: describe the task in plain words (job) and get one best_pick with a paste-ready use_it snippet (MCP client config JSON, install command, or API base URL + docs). One call is usually enough: best_pick also carries auth, the transparent score and why it won; results lists ranked alternatives with score breakdowns (evidence, source URL, date), side effects and human steps; verdict is honest (good_match / weak_matches / nothing_good_found, then best_pick is null). Free, no key. Returns a top-level report_token for optional feedback.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_type | string | – | optional, self-declared |
| client | string | – | optional, e.g. claude-code, cursor, my-agent |
| constraints | object | – | – |
| job | string | yes | The task in plain words, e.g. 'send SMS to customers', 'read my Google Calendar', 'GitHub MCP server' |
| stage | string | – | optional, self-declared |
| watcher_key | string | – | optional: get an alert if nothing good is found now but a match appears later |
No output schema declared.
No examples provided.
How do I install the Toolwork MCP server?
Toolwork is a hosted endpoint at https://mcp.toolwork.org/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.toolwork.org
claude mcp add --transport http org-toolwork-toolwork 'https://mcp.toolwork.org/mcp'
What is the Toolwork MCP server?
Toolwork is an MCP server listed in the public MCP registry as org.toolwork/toolwork. Agent-first tool search. Start with search_tools({job: "your task in plain words"}); free, no key. This page covers its hosted endpoint (https://mcp.toolwork.org/mcp).
Is the Toolwork MCP server safe to use?
Toolwork scores 63 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 Toolwork MCP server expose?
Toolwork exposes 3 tools: search_tools, get_tool, report. Their descriptions and schemas cost roughly 743 tokens of context every time the server is loaded.
Does the Toolwork MCP server require authentication?
No. We connected to Toolwork without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Toolwork MCP server still maintained?
Toolwork is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.