Toolwork

Ingested from the official MCP Registry

FastDrop pulled this entry from the official MCP Registry as org.toolwork/toolwork and probed the endpoint. The maker did not submit it, so the outbound link is not endorsed and the description is not theirs.

If this is your server, claim the listing to edit it and take ownership. The registry index lists everything else still awaiting a probe.

Tools this endpoint exposes

Read directly from the endpoint on 28 Oct 2026. Not supplied by the maker.

• search_tools

  Find tools (MCP servers, HTTP APIs, CLIs, libraries) for a job described in your own words. Results are sorted by the final score (relevance + evidence), with a best pick, a transparent score breakdow

• get_tool

  Full Agent Tool Card for one ID: operator, vendor-official vs publisher-verified, capabilities, endpoints and per-client install, auth, side effects (per server for bundles), human steps, blockers, pr

• resolve_tool

  Turn a URL (remote endpoint, website, docs), GitHub repo, package (npm:/pypi:/oci: or bare name) or registry name into Toolwork IDs. ID scheme: mcp:<registry name>, mcp:docker/<key>, api:<apis.guru ke

• compare_tools

  Compare 2-5 tools side by side for a job: best pick now and why, transparent scores, and the tradeoffs that differ (auth, side effects, health, official, human steps).

• get_playbook

  What agents of a given type typically need at a lifecycle stage, with recommended categories, known blockers and live top picks.

• check_stack

  Health, risks and better alternatives for the tools your agent currently uses.

• get_changes

  Append-only change feed: added/updated entries, health and schema changes, and deprecations with suggested replacements (e.g. Smithery proxy ends 2026-10-31, custom GPTs retire 2026-12-11).

• report

  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