Tidemark
13F ownership behavior for 96 managers: signals, estimated cost basis, daily watchlist events.
Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
claude mcp add --transport http tidemark 'https://tidemark-ohc1.onrender.com/mcp' --header 'X-API-Key: <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.>'
{
"mcpServers": {
"tidemark": {
"type": "http",
"url": "https://tidemark-ohc1.onrender.com/mcp",
"headers": {
"X-API-Key": "<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.>"
}
}
}
}
Frequently asked questions
What is Tidemark?
13F ownership behavior for 96 managers: signals, estimated cost basis, daily watchlist events.
How do I install Tidemark?
It runs as a remote server. In Claude Code: claude mcp add --transport http tidemark 'https://tidemark-ohc1.onrender.com/mcp' --header 'X-API-Key: <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.>'. For other clients, paste the JSON configuration from this page into their MCP settings.
Does Tidemark need an API key?
Yes. It expects X-API-Key, which you set in its configuration.
Who maintains Tidemark?
It is published by com.tidemarkresearch. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.