Other · Remote MCP server
Whalesync
Build and manage Whalesync syncs: connect apps, map tables and fields, monitor and fix issues.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
com.whalesync/whalesync- Version
- 1.2.0
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP
- Published
- 2026-08-28
- Updated
- 2026-08-28
- Publisher
- com.whalesync
- Namespace
- Namespace verified by the MCP Registry via the domain whalesync.com · how
- Listed under
- Maps MCP servers
- Website
- www.whalesync.com
- Repository
- github.com/whalesync/whalesync-mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://api.whalesync.com/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 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
How to connect Whalesync
Whalesync is a remote MCP server: there is nothing to install. Its endpoint is https://api.whalesync.com/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, www.whalesync.com, 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 other servers
| Server | Runs |
|---|---|
| wg-easyAdminister wg-easy (WireGuard Easy) v15: manage VPN clients, configs, QR codes and server status. | Local · stdio |
| Wgea MCPQuery the WGEA in plain English - employer pay gap, workforce composition, leave. | Local · stdio |
| Whaber OracleGround truth operational layer for urban transfers in LatAm. | Remote · HTTPLive check: ✗ no handshake |
| WhaleScope MCPBinance Futures market intelligence: funding, OI, order book, klines, cross-exchange comparison. | Remote · HTTPLive check: ✗ no handshake |
| What a Plan! - MCP ServerDescubre eventos en España: filtra por texto, categoría, ubicación, precio y fecha. 38 categorías. | Remote · HTTPLive check: ✓ handshake |
| What Led ToLiving, source-backed timelines of long-running events, with a quote and source per entry. | Remote · HTTPLive check: ✓ handshake |
| What MattersYour personal action-item list - what you owe and what you're owed. AI proposes; you approve. | Remote · HTTPLive check: ✓ handshake |
| What's AllowedMerged agent permission rules: which settings file wins, and which rules your client ignores. | Local · stdio |