13F ownership behavior for 96 managers: signals, estimated cost basis, daily watchlist events.
Connect Remote server
claude mcp add --transport http tidemark https://tidemark-ohc1.onrender.com/mcp --header "X-API-Key: <X_API_KEY>"{
"mcpServers": {
"tidemark": {
"url": "https://tidemark-ohc1.onrender.com/mcp",
"headers": {
"X-API-Key": "<X_API_KEY>"
}
}
}
}{
"servers": {
"tidemark": {
"type": "http",
"url": "https://tidemark-ohc1.onrender.com/mcp",
"headers": {
"X-API-Key": "<X_API_KEY>"
}
}
}
}Settings > Connectors > Add custom connector
URL: https://tidemark-ohc1.onrender.com/mcpReplace the values in angle brackets with your own. Keys stay on your machine; we never see them.
Tools
This server asks for a key before it lists its tools. Connect it with your own key to see them.
Headers
| Name | Description |
|---|---|
X-API-KeyOptional, secret | Tidemark API key (starts with tdmk_). Generate one signed in at https://tidemarkresearch.com/app/account -- shown once, at creation. Optional: this server also supports OAuth natively -- a client that authorizes via the 401 challenge's resource_metadata does not need this header. |
Details
| Endpoint | https://tidemark-ohc1.onrender.com/mcp (Streamable HTTP) |
| First published | 24 Aug 2026 |
| Last updated | 24 Aug 2026 |
| Registry name | com.tidemarkresearch/tidemark |
More other servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.