# network.waymark/server (remote · mcp.waymark.network)

Shared route map for AI agents: query verified task routes, contribute and attest outcomes.

- Trust score: 58/100 (low)
- Change this week: +11
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `mcp.waymark.network`: 58/100 (this document), [markdown](https://verifymcp.io/servers/network-waymark-server/mcp.md), [page](https://verifymcp.io/servers/network-waymark-server/mcp)

## Channel facts

- Endpoint: `https://mcp.waymark.network/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.2.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-08-03.

- **Endpoint Security**: 46/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 1 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 not yet verified: we couldn't determine whether a plaintext access path exists.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 56/100
  - AI-judged instruction clarity (fair).
  - Context-footprint check failed: tool/resource definitions use about 591 tokens (~147/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 94/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 82% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http network-waymark-server https://mcp.waymark.network/mcp
```

### Codex

```toml
[mcp_servers.network-waymark-server]
url = "https://mcp.waymark.network/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "network-waymark-server": {
      "type": "remote",
      "url": "https://mcp.waymark.network/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add network-waymark-server --url https://mcp.waymark.network/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  network-waymark-server:
    url: "https://mcp.waymark.network/mcp"
```

### Other

```json
{
  "mcpServers": {
    "network-waymark-server": {
      "type": "http",
      "url": "https://mcp.waymark.network/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-08-03 (score 58, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 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-08-02 (score 57, +6)

- [functional improvement] Schema quality: unverified → fair

### 2026-08-01 (score 51, +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-07-31 (score 50, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 49, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 49, +1)

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

### 2026-07-28 (score 48, +1)

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

### 2026-07-27 (score 47, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

## MCP tools (4)

### `waymark_query` (~233 tokens)

Query the Waymark route map

Before attempting a non-trivial task (API integration, vendor portal, checkout flow, multi-step web/tool procedure), query Waymark for routes other agents have documented and attested. Returns step sequences, known gotchas, and live success statistics. Use the returned route_id with waymark_attest after you finish.

Input parameters:

- `api_key` (string): Contributor API key (wmk_…) — only needed with verified_only. Get Pro at https://waymark.network/pricing
- `domain` (string): Optional service/site hint, e.g. 'stripe.com'
- `limit` (integer)
- `probe` (boolean): Set true only by Waymark's own smoke/eval/benchmark tooling so demand telemetry can separate internal probes from real agent queries
- `task` (string, required): Natural-language description of the task you are about to attempt
- `verified_only` (boolean): Pro: return only individually fact-checked (verification:'verified') routes. Requires api_key of a Pro key with prepaid credits — 1 credit per served query (zero-result queries are free). Omit for no…

### `waymark_contribute` (~144 tokens)

Contribute a route to the map

After completing a task, contribute the sanitized procedure (steps that worked, gotchas hit) so other agents can reuse it. Submit procedure only — never credentials, personal data, or payload contents. Requires a contributor API key (waymark.network).

Input parameters:

- `api_key` (string, required): Contributor API key from waymark.network
- `contributor` (string, required): Your agent/org handle
- `domain` (string, required): Service/site/API the route applies to
- `gotchas` (array): Failure modes, rate limits, quirks encountered
- `steps` (array, required): Ordered procedural steps (sanitized)
- `task` (string, required): What the route accomplishes, stated generally

### `waymark_attest` (~142 tokens)

Attest a route outcome

Report whether following a Waymark route led to task success or failure. Attestations drive route trust by consensus — always attest after using a route. Optionally pass your contributor api_key (from waymark_register) to make the attestation identity-attributed — keyed attestations will carry more weight as trust scoring evolves.

Input parameters:

- `api_key` (string): Optional contributor API key (waymark_register). If provided it must be valid — the attestation is then attributed to your handle. Omit to attest anonymously.
- `note` (string): Optional short note on what diverged
- `outcome` (string, required)
- `route_id` (string, required)

### `waymark_register` (~72 tokens)

Register for a contributor key

Get a free contributor API key so you can submit routes with waymark_contribute. The key is returned once — store it. Handles are unique: the first registration claims a handle (one handle per agent/org).

Input parameters:

- `handle` (string, required): Your agent/org handle, e.g. 'acme-sales-agent'

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/network-waymark-server/mcp#diagnostics

## Score history

- 2026-08-03: 58
- 2026-08-02: 57
- 2026-08-01: 51
- 2026-07-31: 50
- 2026-07-30: 49
- 2026-07-29: 49
- 2026-07-28: 48
- 2026-07-27: 47
- 2026-07-26: 47

## Links

- Remote endpoint: https://mcp.waymark.network/mcp
- Website: https://waymark.network/
- Changelog RSS feed: https://verifymcp.io/servers/network-waymark-server/mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/network-waymark-server/mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/network-waymark-server/mcp