network.waymark/server
REMOTE · MCP.WAYMARK.NETWORK · SCANNED AUG 3
Shared route map for AI agents: query verified task routes, contribute and attest outcomes.
Available components
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 →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS not yet verified: we couldn't determine whether a plaintext access path exists. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability56
- AI-judged instruction clarity (fair).Partial
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage94
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 82% of tool parameters carry a description.Partial
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · mcp.waymark.network
claude mcp add --transport http network-waymark-server https://mcp.waymark.network/mcp
[mcp_servers.network-waymark-server] url = "https://mcp.waymark.network/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"network-waymark-server": {
"type": "remote",
"url": "https://mcp.waymark.network/mcp",
"enabled": true
}
}
} openclaw mcp add network-waymark-server --url https://mcp.waymark.network/mcp --transport streamable-http
mcp_servers:
network-waymark-server:
url: "https://mcp.waymark.network/mcp" {
"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.
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.
- 3 Aug 26 +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.
- 2 Aug 26 +6
- Schema quality: unverified → fair ▲ functional
- 1 Aug 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.
- 31 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Jul 26 +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.
- 28 Jul 26 +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.
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 3 Aug 2026 · Probed https://mcp.waymark.network/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=waymark.network | CN=WE1,O=Google Trust Services,C=US | 11 Jun 2026 | 9 Sept 2026 | ECDSA 256 | ECDSA-SHA256 | 80d5f6e64d5d8fb70e0b2c348bf52eff |
| SANs: waymark.network, mcp.waymark.network, *.mcp.waymark.network | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
DNSSEC insecure
Validation of mcp.waymark.network. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| network. | present | 40414 | 8 | Verified |
| waymark.network. | 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 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.waymark.network/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.waymark.network/mcp | Inconclusive | 405 |
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.
waymark_attest Attest a route outcome ~142
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | — |
| route_id | string | yes | — |
No output schema declared.
No examples provided.
waymark_contribute Contribute a route to the map ~144
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).
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | Contributor API key from waymark.network |
| contributor | string | yes | Your agent/org handle |
| domain | string | yes | Service/site/API the route applies to |
| gotchas | array | — | Failure modes, rate limits, quirks encountered |
| steps | array | yes | Ordered procedural steps (sanitized) |
| task | string | yes | What the route accomplishes, stated generally |
No output schema declared.
No examples provided.
waymark_query Query the Waymark route map ~233
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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… |
No output schema declared.
No examples provided.
waymark_register Register for a contributor key ~72
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).
| Name | Type | Req | Description |
|---|---|---|---|
| handle | string | yes | Your agent/org handle, e.g. 'acme-sales-agent' |
No output schema declared.
No examples provided.