Other · Remote MCP server
Thruact
Name the job, not the vendor. Routes a provider, fails over, catalog off the tool list.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
com.thruact/thruact- Version
- 0.2.0
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP
- Published
- 2026-08-25
- Updated
- 2026-08-25
- Publisher
- com.thruact
- Namespace
- Namespace verified by the MCP Registry via the domain thruact.com · how
- Website
- thruact.com
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://thruact.com/mcp | X-Thruact-Token (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 200)
- Handshake
- thruact 0.2.0 · protocol 2025-06-18
- Tools discovered
- 7:
thruact_discover,thruact_act,thruact_compare,thruact_call,thruact_wallet,thruact_iq,thruact_proxy - Checked on
- 2026-10-05
How to connect Thruact
Thruact is a remote MCP server: there is nothing to install. Its endpoint is https://thruact.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: X-Thruact-Token (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, thruact.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 |
|---|---|
| three.ws x402 BazaarDiscover and price paid agent services across the live x402 network, by three.ws. | Remote · HTTPLive check: sign-in required |
| ThrifleUS return policies, price-match rules, discounts, deals and Amazon price verdicts. Read-only. | Remote · HTTPLive check: ✓ handshake |
| ThroughlineA persistent AI self you own - memory, persona, judgment - portable across all your AI hosts. | Remote · HTTPLive check: sign-in required |
| ThroughlineGive Claude complete understanding of your software project. | Local · stdio |
| ThryxProtocol MCP ServerThryxProtocol v3.1 - gasless AI agent launchpad on Base. 21 tools wrap thryx.fun HTTP API. | Local · stdio |
| ThumbGatePre-action gates that block AI agents from repeating known mistakes. | Local · stdio |
| Tick MCPA time server that keeps your AI honest about time. Real clock + drift guard, zero dependencies. | Remote · HTTPLive check: ✓ handshake |
| TickerFactsSEC EDGAR fundamentals as agent tools: look up or screen US public companies. Free, no key, CC0. | Remote · HTTPLive check: ✓ handshake |