network.waymark/server
REMOTE · MCP.WAYMARK.NETWORK · SCANNED OCT 4
Query 17,000+ verified task routes with known gotchas and API drift alerts. Free keyless reads.
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 → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. 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 Usability64
- AI-judged instruction clarity (good).Pass
- 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the network.waymark/server MCP server?
network.waymark/server is a hosted endpoint at https://mcp.waymark.network/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 · mcp.waymark.network
claude mcp add --transport http network-waymark-server 'https://mcp.waymark.network/mcp'
{
"mcpServers": {
"network-waymark-server": {
"url": "https://mcp.waymark.network/mcp"
}
}
} {
"servers": {
"network-waymark-server": {
"type": "http",
"url": "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": {
"Transport": "http",
"Url": "https://mcp.waymark.network/mcp"
}
}
} assistant mcp add network-waymark-server -t streamable-http -u '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.
- 28 Sept 26 +7
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 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
- 26 Aug 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
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 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
- 2 Aug 26 0
- Schema quality: unverified → fair ▲ functional
- 31 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
- 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
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 5 Oct 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 | 9 Aug 2026 | 7 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 6b7458ea5a8d898b0ed990631b4ebf09 |
| 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 |
Background: What to check on a remote MCP endpoint →
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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
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. 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 →
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.
What is the network.waymark/server MCP server?
network.waymark/server is an MCP server listed in the public MCP registry as network.waymark/server. Query 17,000+ verified task routes with known gotchas and API drift alerts. Free keyless reads. This page covers its hosted endpoint (https://mcp.waymark.network/mcp).
Is the network.waymark/server MCP server safe to use?
network.waymark/server scores 78 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 network.waymark/server MCP server expose?
network.waymark/server exposes 4 tools: waymark_query, waymark_contribute, waymark_attest, waymark_register. Their descriptions and schemas cost roughly 591 tokens of context every time the server is loaded.
Does the network.waymark/server MCP server require authentication?
No. We connected to network.waymark/server without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the network.waymark/server MCP server still maintained?
network.waymark/server is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.