# TwexAPI (remote · api.twexapi.io)

Search public X (Twitter) posts and read profiles, timelines, followers, trends and X Articles.

- Trust score: 33/100 (low)
- Change this week: −20
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-24

## Components

- remote · `api.twexapi.io`: 33/100 (this document), [markdown](https://verifymcp.io/servers/io-twexapi-mcp/api.md), [page](https://verifymcp.io/servers/io-twexapi-mcp/api)

## Channel facts

- Endpoint: `https://api.twexapi.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.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-10-24.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 0/100
  - Schema blocked by authentication: the endpoint requires auth we don't have to read it.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.
- **Tool Safety**: 0/100
  - Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.
- **Capabilities**: 0/100
  - Capabilities blocked by authentication: the endpoint requires auth we don't have to read them.

**Unverified: 5 categories.** Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

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

TwexAPI is a hosted endpoint at https://api.twexapi.io/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 io-twexapi-mcp 'https://api.twexapi.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-twexapi-mcp": {
      "url": "https://api.twexapi.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-twexapi-mcp": {
      "type": "http",
      "url": "https://api.twexapi.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-twexapi-mcp]
url = "https://api.twexapi.io/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add io-twexapi-mcp --url 'https://api.twexapi.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-twexapi-mcp:
    url: "https://api.twexapi.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-twexapi-mcp": {
      "Transport": "http",
      "Url": "https://api.twexapi.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-twexapi-mcp -t streamable-http -u 'https://api.twexapi.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-twexapi-mcp": {
      "type": "http",
      "url": "https://api.twexapi.io/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-10-24 (score 33, −28)

- [security regression] Endpoint reachability: reachable → behind authorisation
- [security regression] Tool safety: pass → unverified
- [security regression] Stability: 0.27 → unverified
- [security] Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes.
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-10-23 (score 61, +1)

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

### 2026-10-21 (score 60, +5)

- [security improvement] HTTPS: unverified → pass

### 2026-10-20 (score 55, +1)

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

### 2026-10-18 (score 54, +1)

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

### 2026-10-17 (score 53, −4)

- [security regression] HTTPS: pass → unverified

### 2026-10-16 (score 57, +5)

- [security improvement] HTTPS: unverified → pass
- [functional improvement] Stability: unverified → 0.03

### 2026-10-15 (score 52)

First indexed and scored.

## MCP tools (2)

### `explore` (~37 tokens)

Search allowed TwexAPI endpoints.

Input parameters:

- `category` (string)
- `include_writes` (boolean)
- `query` (string)

### `twexapi_request` (~45 tokens)

Call an allowed TwexAPI REST endpoint.

Input parameters:

- `body`
- `method` (string, required)
- `path` (string, required)
- `query` (object)

## Diagnostics

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

## Score history

- 2026-10-24: 33
- 2026-10-23: 61
- 2026-10-22: 60
- 2026-10-21: 60
- 2026-10-20: 55
- 2026-10-19: 54
- 2026-10-18: 54
- 2026-10-17: 53
- 2026-10-16: 57
- 2026-10-15: 52

## Common questions

### What is the TwexAPI MCP server?

TwexAPI is an MCP server listed in the public MCP registry as io.twexapi/mcp. Search public X (Twitter) posts and read profiles, timelines, followers, trends and X Articles. This page covers its hosted endpoint (https://api.twexapi.io/mcp).

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

TwexAPI scores 33 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 TwexAPI MCP server expose?

TwexAPI exposes 2 tools: explore, twexapi_request. Their descriptions and schemas cost roughly 82 tokens of context every time the server is loaded.

### Does the TwexAPI MCP server require authentication?

No. We connected to TwexAPI without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the TwexAPI MCP server still maintained?

TwexAPI is still listed as active in the MCP registry. We last reached this channel on 24 October 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://api.twexapi.io/mcp
- Authorisation metadata: https://api.twexapi.io/.well-known/oauth-protected-resource/mcp
- Website: https://docs.twexapi.io/mcp/overview
- Changelog RSS feed: https://verifymcp.io/servers/io-twexapi-mcp/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-twexapi-mcp/api.json
- HTML version of this page: https://verifymcp.io/servers/io-twexapi-mcp/api