Data · Remote MCP server
Thinkstack
Governed map of company knowledge for humans + agents.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
com.thinkstack-app/thinkstack- Version
- 1.0.0
- Status
- Active
- Category
- data
- Transport
- Streamable HTTP
- Published
- 2026-09-19
- Updated
- 2026-09-19
- Publisher
- com.thinkstack-app
- Namespace
- Namespace verified by the MCP Registry via the domain thinkstack-app.com · how
- Listed under
- Maps MCP servers
- Website
- thinkstack-home.com
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.thinkstack-app.com/mcp/ | Authorization (required, secret) |
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; a Bearer token is asked for
- Checked on
- 2026-10-05
How to connect Thinkstack
Thinkstack is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.thinkstack-app.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.
The registry entry declares an HTTP header for the connection: Authorization (required, secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
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, thinkstack-home.com, was checked for the files that tell AI systems about a site.
| File | Result |
|---|---|
/llms.txt | No real file found |
/.well-known/mcp.json | No real file found |
/.well-known/ai-plugin.json | No real file found |
/agents.json | No real file found |
More data servers
| Server | Runs |
|---|---|
| TheRundown Data MCPSix Product API tools require authentication; protocol metadata discovery is keyless. | Remote · HTTPLive check: ✓ handshake |
| TheRundown Documentation MCPOfficial TheRundown API documentation search. No live data or authenticated Product API calls. | Remote · HTTPLive check: ✓ handshake |
| Thesportsdb MCPSports data from TheSportsDB. No key required. | Local · stdio |
| TheWholeTorahTorah lessons in six languages: grounded search, cited lessons, sources, honest ask. | Remote · HTTPLive check: ✓ handshake |
| ThirdtrailElevation-corrected sun, moon, twilight, solar and tide data for any point on Earth. | Remote · HTTPLive check: sign-in required |
| ThisispaperSearch 2,500+ curated architecture, design, photography and art projects. Free tier, no signup. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| Thor Henning Hetland - signed knowledge webThor Henning Hetland's signed knowledge web: plan, load and verify ed25519-signed KCP units. | Remote · HTTPLive check: ✓ handshake |
| ThothRead-only MCP over an agentic SLR workspace with per-claim citation verification. | Remote · HTTPLive check: sign-in required |