Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Pathwize

REMOTE · WWW.GOPATHWIZE.COM

Run data annotation and evaluation tasks with vetted domain experts: create, publish, get results.

+4 this week 71 Trust /100

Last scanned (16 hours ago)

Scores higher than 61% of remote servers

Reachable. Last reached 23 Oct 2026.

Category Data and Analytics

Trust breakdown (7 categories)

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
Transport & Reachability100
Schema Quality & AI Usability73
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 1018 tokens (~101/item across 10 items; 10 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management63
  • Stability observed for 19 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage81
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 43% 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; "publish_task" implies "publish" 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 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Changelog

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.

  • 23 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

  • 21 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 27. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 9 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 17. That category is still filling its 30-day observation window: 2 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.

Diagnostics

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 23 Oct 2026 · Probed https://www.gopathwize.com/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=www.gopathwize.com CN=YR2,O=Let's Encrypt,C=US 30 Aug 2026 28 Nov 2026 RSA 2048 SHA256-RSA 59e5bf069bf70579c127314c2630aad05c8
SANs: www.gopathwize.com
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of www.gopathwize.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
gopathwize.com. 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
Header Value
strict-transport-security max-age=63072000; includeSubDomains; preload
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(self), microphone=(self), geolocation=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://www.gopathwize.com/api/mcp Verified 200
http (plaintext) http://www.gopathwize.com/api/mcp HTTPS enforced 308 https://www.gopathwize.com/api/mcp
MCP tools · 10 exposed · ~953 tokens

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 →

Tool Tokens
add_items ~80

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.

NameTypeReqDescription
itemsarrayyes–
referenceboolean––
taskIdstringyes–

No output schema declared.

No examples provided.

close_task ~37

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

NameTypeReqDescription
statusstring––
taskIdstringyes–

No output schema declared.

No examples provided.

create_task ~304

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 the user confirms.

NameTypeReqDescription
allow_cant_tellboolean–Let experts skip an item without a class (default true)
allow_noteboolean––
annotationstring–Default classification
classesarray–Class names experts choose from
deadlinestring––
domainstring––
examplesarray–Example images by public URL with the class they show. Labeling tasks need one per class before they can open.
expertisestring–What experts need to know, one line
instructionsstring–Instructions for the experts in Markdown. A table whose first column names the classes becomes the per-class briefing.
languagestring–Language of the instructions
members_onlyboolean–Only members of these pools see the task, even on public pools
multi_selectboolean––
pool_idsarray–Pools the task runs on (see list_pools)
qualificationobject––
ratenumber–Hourly pay for the expert in EUR
seconds_per_iteminteger––
titlestringyes–
typestring–Default data_labeling

No output schema declared.

No examples provided.

get_results ~60

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

NameTypeReqDescription
limitinteger––
sincestring––
starting_afterstring––
taskIdstringyes–

No output schema declared.

No examples provided.

get_task ~36

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

NameTypeReqDescription
taskIdstringyes–

No output schema declared.

No examples provided.

list_pools ~27

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_tasks ~21

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

open_dashboard ~51

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.

NameTypeReqDescription
taskIdstring––

No output schema declared.

No examples provided.

publish_task ~68

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.

NameTypeReqDescription
confirmbooleanyes–
taskIdstringyes–

No output schema declared.

No examples provided.

update_task ~269

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

NameTypeReqDescription
allow_cant_tellboolean–Let experts skip an item without a class (default true)
allow_noteboolean––
annotationstring–Default classification
classesarray–Class names experts choose from
deadlinestring––
domainstring––
examplesarray–Example images by public URL with the class they show. Labeling tasks need one per class before they can open.
expertisestring–What experts need to know, one line
instructionsstring–Instructions for the experts in Markdown. A table whose first column names the classes becomes the per-class briefing.
languagestring–Language of the instructions
members_onlyboolean–Only members of these pools see the task, even on public pools
multi_selectboolean––
pool_idsarray–Pools the task runs on (see list_pools)
qualificationobject––
ratenumber–Hourly pay for the expert in EUR
seconds_per_iteminteger––
taskIdstringyes–
titlestring––

No output schema declared.

No examples provided.

Install

How do I install the Pathwize MCP server?

Pathwize is a hosted endpoint at https://www.gopathwize.com/api/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 · www.gopathwize.com

# add to Claude Code
claude mcp add --transport http com-gopathwize-pathwize 'https://www.gopathwize.com/api/mcp'
Common questions

What is the Pathwize MCP server?

Pathwize is an MCP server listed in the public MCP registry as com.gopathwize/pathwize. Run data annotation and evaluation tasks with vetted domain experts: create, publish, get results. This page covers its hosted endpoint (https://www.gopathwize.com/api/mcp).

Is the Pathwize MCP server safe to use?

Pathwize scores 71 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 Pathwize MCP server expose?

Pathwize exposes 10 tools: list_pools, list_tasks, get_task, create_task, update_task, and 5 more. Their descriptions and schemas cost roughly 953 tokens of context every time the server is loaded.

Does the Pathwize MCP server require authentication?

No. We connected to Pathwize without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Pathwize MCP server still maintained?

Pathwize is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.