# Thruact (remote · thruact.com)

Name the job, not the vendor. Routes a provider, fails over, catalog off the tool list.

- Trust score: 86/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- remote · `thruact.com`: 86/100 (this document), [markdown](https://verifymcp.io/servers/com-thruact-thruact/thruact.md), [page](https://verifymcp.io/servers/com-thruact-thruact/thruact)

## Channel facts

- Endpoint: `https://thruact.com/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `0.2.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-21.

- **Endpoint Security**: 94/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 66/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 511 tokens (~73/item across 7 items; 7 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 90/100
  - Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 84/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 53% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "thruact_proxy" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Thruact MCP server?

Thruact is a hosted endpoint at https://thruact.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-thruact-thruact 'https://thruact.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-thruact-thruact": {
      "url": "https://thruact.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-thruact-thruact": {
      "type": "http",
      "url": "https://thruact.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-thruact-thruact]
url = "https://thruact.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-thruact-thruact": {
      "type": "remote",
      "url": "https://thruact.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-thruact-thruact --url 'https://thruact.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-thruact-thruact:
    url: "https://thruact.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-thruact-thruact": {
      "Transport": "http",
      "Url": "https://thruact.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-thruact-thruact -t streamable-http -u 'https://thruact.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-thruact-thruact": {
      "type": "http",
      "url": "https://thruact.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-21 (score 86, +1)

No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-19 (score 85, +1)

No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-17 (score 84, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-15 (score 83, +1)

No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-12 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-10 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-08 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-06 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (7)

### `thruact_discover` (~47 tokens)

Find capabilities for a job, with prices and measured reliability. Search first, execute second.

Input parameters:

- `limit` (integer): Max candidates
- `query` (string, required): Natural language job

### `thruact_act` (~155 tokens)

Run a capability. Routes across providers and fails over automatically on provider faults. The reply's `route` says which providers were considered, what each scored, and why any were not used — including ones dropped for a missing credential.

Input parameters:

- `capability` (string, required)
- `hedge` (boolean): Race a backup provider if the first is slower than usual. Cuts tail latency; you are charged for one answer.
- `input` (object)
- `max_cost_usd` (number): Ceiling for this call. Narrows which providers may be used rather than refusing outright; if nothing fits, the error names the cheapest price that would.
- `prefer` (string): What to optimise for among the providers that fit the ceiling.

### `thruact_compare` (~84 tokens)

Ask every provider behind a capability the same question at once and report where their answers differ. Use it when the answer matters enough to want it corroborated. Costs more than act: every provider called is paid.

Input parameters:

- `capability` (string, required)
- `input` (object)
- `providers` (integer): How many providers to ask. Omit for all of them.

### `thruact_call` (~34 tokens)

Run one specific tool by id. No failover.

Input parameters:

- `params` (object)
- `tool` (string, required)

### `thruact_wallet` (~16 tokens)

Prepaid balance and recent charges.

### `thruact_iq` (~29 tokens)

Measured reliability per tool over the last 7 days.

Input parameters:

- `capability` (string)

### `thruact_proxy` (~146 tokens)

Send an authenticated request to a third-party vendor the workspace has connected. The stored API key is injected server-side — you never see it. Give the vendor id from the directory (e.g. openai, sendgrid), an HTTP method, and a path on that vendor's own API. Use it to act through a connected vendor that is not a Thruact capability. Metered per call.

Input parameters:

- `body` (object): JSON request body for POST/PUT/PATCH
- `method` (string)
- `path` (string, required): Path on the vendor's API, e.g. /v1/models
- `vendor` (string, required): Vendor id from the directory

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-thruact-thruact/thruact#diagnostics

## Score history

- 2026-09-21: 86
- 2026-09-20: 85
- 2026-09-19: 85
- 2026-09-18: 84
- 2026-09-17: 84
- 2026-09-16: 83
- 2026-09-15: 83
- 2026-09-14: 82
- 2026-09-13: 82
- 2026-09-12: 82
- 2026-09-11: 81
- 2026-09-10: 81
- 2026-09-09: 80
- 2026-09-08: 80
- 2026-09-07: 79
- 2026-09-06: 79
- 2026-09-05: 78
- 2026-09-04: 78
- 2026-09-03: 77
- 2026-09-02: 77
- 2026-09-01: 76
- 2026-08-31: 76
- 2026-08-30: 75
- 2026-08-29: 75
- 2026-08-28: 75
- 2026-08-27: 74
- 2026-08-26: 74
- 2026-08-25: 72

## Common questions

### What is the Thruact MCP server?

Thruact is an MCP server listed in the public MCP registry as com.thruact/thruact. Name the job, not the vendor. Routes a provider, fails over, catalog off the tool list. This page covers its hosted endpoint (https://thruact.com/mcp).

### Is the Thruact MCP server safe to use?

Thruact scores 86 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Thruact MCP server expose?

Thruact exposes 7 tools: thruact_discover, thruact_act, thruact_compare, thruact_call, thruact_wallet, and 2 more. Their descriptions and schemas cost roughly 511 tokens of context every time the server is loaded.

### Does the Thruact MCP server require authentication?

Yes. Thruact asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the Thruact MCP server still maintained?

Thruact is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://thruact.com/mcp
- Authorisation metadata: https://thruact.com/.well-known/oauth-protected-resource/mcp
- Website: https://thruact.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-thruact-thruact/thruact.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-thruact-thruact/thruact.json
- HTML version of this page: https://verifymcp.io/servers/com-thruact-thruact/thruact