Look up Conservatory oboe fingerings, half-hole, left/forked F rules, octave keys & trills.
Developer ToolsData access / search
- Passed: Handshake
- Passed: Tools listed
- Passed: Updated recently
Median latency 66 ms · Last checked
Explore
Evidence for your next connection.
Independent measurements of remote MCP servers. Every observation has a timestamp.
Read-only probesMCP server · Data access / search
Agent-first tool search. Start with search_tools({job: "your task in plain words"}); free, no key.
2 failed · 8 not measured
Median of successful probes over 7 days
Share of countable probes over 30 days, including daily rollups. Auth challenges are excluded.
Tool definitions returned by this server
Independent monitoring
Responded
The server completed its last measured handshake. This is an observation, not a guarantee.
Last checked| Test area | Passed | Failed | Unmeasured |
|---|---|---|---|
ConnectionCan a client connect and discover tools? | 5 | 0 | 0 |
Reliability & speedDoes it respond consistently and quickly? | 0 | 0 | 4 |
Access & authenticationWhat is required to use this server? | 1 | 0 | 2 |
Tool qualityAre the tool definitions usable by an agent? | 3 | 1 | 0 |
Publisher identityCan the publisher be traced to its source? | 3 | 1 | 2 |
Unmeasured means there is not enough evidence to decide. How these checks work
Start using Toolwork
Choose your client, copy the configuration, then enable the server in your client’s MCP settings.
Run this command in your terminal, then restart Claude Code.
Claude Code
claude mcp add --transport http toolwork https://mcp.toolwork.org/mcpCapabilities
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.
DiscoveredPREFERRED 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.
DiscoveredCall 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.summary says in one line what to use and why (reasons: vendor-official or third-party, live check, auth, read-only or can send/spend, outcome reports), best_pick.report_call is the one-line report to send after you use it; 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.
DiscoveredRecent measurements
| Checked | Result | Response | Tools |
|---|---|---|---|
| Connected | 68 ms | 3 |