Pathwize MCP server

• Registry namecom.gopathwize/pathwizeverified in the MCP registry

The registry name sits under gopathwize.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-24
• Tools10
• Server calls itselfpathwize
• Server version1.0.0
• Protocol version2025-06-18

On 2026-10-24 the server answered initialize and tools/list without a sign-in. First answer in 125 ms.

• Whether its tools do the product's job has not been judged yet.
• Checked on 3 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP scoreafter a weeka score needs 7 daily checks: 3 so far
• Answeredmeasuring3 of the 7 daily checks it takes to print a share
• Median first answer159 ms
• Space in an agent's context≈ 1,901 tokensthe definitions of all its tools (10), which an agent carries on every turn
• Tool definitionsB · 77 of 100
• Typed results0 of 10 toolsdeclared outputSchema: results come typed, read once

• Parameters without a description: in 8 of 10
• Not saying whether it only reads or can destroy: 6 of 10

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• list_pools

  Pools a task can run on: active curated pools plus your own, with member counts.

• list_tasks

  Your AI tasks, newest first, with status and item counts.

• get_task

  One task with settings, classes, examples, qualification, reference item count and item counts by status.

• create_task

  Create a labeling or evaluation task as a draft; nobody is notified until publish_task. Typical order: list_pools, create_task with instructions, classes, rate, pool_ids and one example image per class, add_items, then publish_task after…

• update_task

  Change a task's settings; only the fields you pass change, examples are added. Does not publish.

• add_items

  Add items by public URL; Pathwize copies the files into its own storage. reference: true adds them to the qualification set (optionally with gold_label for automatic scoring). Idempotent per id, up to 1000 per call.

• publish_task

  Open a task for experts. This emails every expert in the task's pools once and cannot be undone, so call it only after the user explicitly confirmed, with confirm: true. Fails with a list of anything missing.

• close_task

  closed ends the task, draft pauses it. Experts are not emailed.

• get_results

  Finished items with final label, agreement, notes and flags. Page with starting_after (the last item id).

• open_dashboard

  One-time link that opens the Pathwize business dashboard signed in as this business (optionally one task). Single use, one hour; give it only to the user.