Productivity · Remote MCP server
waymark.network
Query 17,000+ verified task routes with known gotchas and API drift alerts. Free keyless reads.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
network.waymark/server- Version
- 0.9.2
- Status
- Active
- Category
- productivity
- Transport
- Streamable HTTP
- Published
- 2026-08-12
- Updated
- 2026-08-12
- Publisher
- network.waymark
- Namespace
- Namespace verified by the MCP Registry via the domain waymark.network · how
- Website
- waymark.network
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.waymark.network/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- waymark 0.2.0 · protocol 2025-06-18
- Tools discovered
- 4:
waymark_query,waymark_contribute,waymark_attest,waymark_register - Checked on
- 2026-10-05
How to connect waymark.network
waymark.network is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.waymark.network/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
Site checks
The website's own root, waymark.network, was checked for the files that tell AI systems about a site.
| File | Result |
|---|---|
/llms.txt | Real file, HTTP 200 · 2026-10-04 |
/.well-known/mcp.json | No real file found |
/.well-known/ai-plugin.json | No real file found |
/agents.json | No real file found |
More productivity servers
| Server | Runs |
|---|---|
| WASync - WhatsApp Platform APIWhatsApp for your app or AI agent over OAuth2 - the same connections WASync runs inside your CRM. | Remote · HTTPLive check: ✗ no handshake |
| WatchtowerJob alerts for AI agents: describe a role once, get only new postings from 1,000+ tech job boards. | Remote · HTTPLive check: ✓ handshake |
| waterr.aiList WaterrAI scenarios, fetch AI-run meetings, and pull rubric-scored analyses. | Remote · HTTPLive check: sign-in required |
| WaxsealEd25519 identity for AI agents. Verify seals, sign documents, gate actions with approvals. | Local · stdio |
| waystation.aiToolbox to connect your LLM to popular productivity tools such as Monday, AirTable, Slack. | Remote · HTTP, SSELive check: ✗ no handshake |
| WazapiOperate WhatsApp Business: conversations, contacts, chatbot flows, templates, CRM and store. | Remote · HTTPLive check: sign-in required |
| wazionapps MCP-SERVER244 WhatsApp Business AI tools for messaging, automation, marketing, CRM and Shopify. | Local · stdio |
| wcagc - accessibility scanningDeterministic axe-core accessibility scans (WCAG 2.1 AA, EN 301 549, PDF/UA) via your account. | Remote & Local · HTTP, stdioLive check: sign-in required |