mcpbeat

Waymark MCP Server

network.waymark/server
answering

Waymark is answering right now. Last checked 9 min ago. It exposes 4 tools.

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

Uptime history 42 hours of history
42 hours agonow
100.0%
Uptime 24h
91 of 91 checks
4
Tools
read from the server
970 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 9 min ago.

run in your terminal
claude mcp add server --transport http https://mcp.waymark.network/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "server": {
      "url": "https://mcp.waymark.network/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.server]
url = "https://mcp.waymark.network/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "server": {
      "url": "https://mcp.waymark.network/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "server": {
      "url": "https://mcp.waymark.network/mcp"
    }
  }
}

Available tools 4

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

waymark
waymark_attest
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.
waymark_contribute
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).
waymark_query
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.
waymark_register
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).

Endpoints

URLTransportStateLatencyChecked
https://mcp.waymark.network/mcp streamable-http answering 999 ms 9 min ago

Waymark — questions

Answers built from our own checks of this server.

What can Waymark do?
It exposes 4 tools, read directly from the server on our last check. Among them: waymark_attest, waymark_contribute, waymark_query, waymark_register. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Waymark working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 970 ms. The bar chart above shows every period we have measured.
How do I connect Waymark?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Waymark need an API key?
No. Waymark completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 4 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Waymark?
It answers our handshake in 970 ms on average, which is faster than 6% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.