# Pathwize (remote · www.gopathwize.com)

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

- Trust score: 71/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-23

## Components

- remote · `www.gopathwize.com`: 71/100 (this document), [markdown](https://verifymcp.io/servers/com-gopathwize-pathwize/api-mcp.md), [page](https://verifymcp.io/servers/com-gopathwize-pathwize/api-mcp)

## Channel facts

- Endpoint: `https://www.gopathwize.com/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-23.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 73/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 1018 tokens (~101/item across 10 items; 10 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 63/100
  - Stability observed for 19 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 81/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 43% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 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.
  - An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## 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.

### Claude

```bash
claude mcp add --transport http com-gopathwize-pathwize 'https://www.gopathwize.com/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-gopathwize-pathwize": {
      "url": "https://www.gopathwize.com/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-gopathwize-pathwize": {
      "type": "http",
      "url": "https://www.gopathwize.com/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-gopathwize-pathwize]
url = "https://www.gopathwize.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-gopathwize-pathwize": {
      "type": "remote",
      "url": "https://www.gopathwize.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-gopathwize-pathwize --url 'https://www.gopathwize.com/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-gopathwize-pathwize:
    url: "https://www.gopathwize.com/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-gopathwize-pathwize": {
      "Transport": "http",
      "Url": "https://www.gopathwize.com/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-gopathwize-pathwize -t streamable-http -u 'https://www.gopathwize.com/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-gopathwize-pathwize": {
      "type": "http",
      "url": "https://www.gopathwize.com/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-23 (score 71, +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.

### 2026-10-21 (score 70, +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.

### 2026-10-19 (score 69, +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.

### 2026-10-17 (score 68, +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.

### 2026-10-15 (score 67, +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.

### 2026-10-12 (score 66, +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.

### 2026-10-10 (score 65, +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.

### 2026-10-09 (score 64, +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.

## MCP tools (10)

### `list_pools` (~27 tokens)

List expert pools

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

### `list_tasks` (~21 tokens)

List AI tasks

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

### `get_task` (~36 tokens)

Get an AI task

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

Input parameters:

- `taskId` (string, required)

### `create_task` (~304 tokens)

Create an AI task (draft)

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.

Input parameters:

- `allow_cant_tell` (boolean): Let experts skip an item without a class (default true)
- `allow_note` (boolean)
- `annotation` (string): Default classification
- `classes` (array): Class names experts choose from
- `deadline` (string)
- `domain` (string)
- `examples` (array): Example images by public URL with the class they show. Labeling tasks need one per class before they can open.
- `expertise` (string): What experts need to know, one line
- `instructions` (string): Instructions for the experts in Markdown. A table whose first column names the classes becomes the per-class briefing.
- `language` (string): Language of the instructions
- `members_only` (boolean): Only members of these pools see the task, even on public pools
- `multi_select` (boolean)
- `pool_ids` (array): Pools the task runs on (see list_pools)
- `qualification` (object)
- `rate` (number): Hourly pay for the expert in EUR
- `seconds_per_item` (integer)
- `title` (string, required)
- `type` (string): Default data_labeling

### `update_task` (~269 tokens)

Update an AI task

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

Input parameters:

- `allow_cant_tell` (boolean): Let experts skip an item without a class (default true)
- `allow_note` (boolean)
- `annotation` (string): Default classification
- `classes` (array): Class names experts choose from
- `deadline` (string)
- `domain` (string)
- `examples` (array): Example images by public URL with the class they show. Labeling tasks need one per class before they can open.
- `expertise` (string): What experts need to know, one line
- `instructions` (string): Instructions for the experts in Markdown. A table whose first column names the classes becomes the per-class briefing.
- `language` (string): Language of the instructions
- `members_only` (boolean): Only members of these pools see the task, even on public pools
- `multi_select` (boolean)
- `pool_ids` (array): Pools the task runs on (see list_pools)
- `qualification` (object)
- `rate` (number): Hourly pay for the expert in EUR
- `seconds_per_item` (integer)
- `taskId` (string, required)
- `title` (string)

### `add_items` (~80 tokens)

Add items to an AI task

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.

Input parameters:

- `items` (array, required)
- `reference` (boolean)
- `taskId` (string, required)

### `publish_task` (~68 tokens)

Publish an AI 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.

Input parameters:

- `confirm` (boolean, required)
- `taskId` (string, required)

### `close_task` (~37 tokens)

Close or pause an AI task

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

Input parameters:

- `status` (string)
- `taskId` (string, required)

### `get_results` (~60 tokens)

Get labeled results

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

Input parameters:

- `limit` (integer)
- `since` (string)
- `starting_after` (string)
- `taskId` (string, required)

### `open_dashboard` (~51 tokens)

Open the business dashboard, signed in

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.

Input parameters:

- `taskId` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-gopathwize-pathwize/api-mcp#diagnostics

## Score history

- 2026-10-23: 71
- 2026-10-22: 70
- 2026-10-21: 70
- 2026-10-20: 69
- 2026-10-19: 69
- 2026-10-18: 68
- 2026-10-17: 68
- 2026-10-16: 67
- 2026-10-15: 67
- 2026-10-14: 66
- 2026-10-13: 66
- 2026-10-12: 66
- 2026-10-10: 65
- 2026-10-09: 64
- 2026-10-06: 63
- 2026-10-04: 62

## 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.

## Links

- Remote endpoint: https://www.gopathwize.com/api/mcp
- Authorisation metadata: https://www.gopathwize.com/.well-known/oauth-protected-resource/api/mcp
- Website: https://www.gopathwize.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-gopathwize-pathwize/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-gopathwize-pathwize/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-gopathwize-pathwize/api-mcp