mcp server
server
Shared route map for AI agents: query verified task routes, contribute and attest outcomes.
Description as published by the maintainer. Source
- version 0.2.0
- active
active — Registry entry last updated 2026-06-11.
What this server can do
4 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
waymark_attest(note, api_key, outcome, route_id)- 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. Required: route_id, outcome.
waymark_contribute(task, steps, domain, api_key, gotchas, contributor)- 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). Required: api_key, task, domain, steps, contributor.
waymark_query(task, limit, probe, domain, api_key, verified_only)- 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. Required: task.
waymark_register(handle)- 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). Required: handle.
Last successful function declaration observed on . Source: https://mcp.waymark.network/mcp. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://mcp.waymark.network/mcp.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Latest published version | 0.2.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-06-11 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-06-11 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| mcp tools declared | 4 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | mcp.waymark.network | |
| mcp endpoint status | ok | The server listed 4 functions when asked. | as of probe | mcp.waymark.network |
Where to get it
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json