# HasData ChatGPT (remote · mcp.hasdata.com)

Send a prompt to ChatGPT anonymously and get the answer with its web sources, as JSON.

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

## Components

- remote · `mcp.hasdata.com`: 83/100 (this document), [markdown](https://verifymcp.io/servers/com-hasdata-chatgpt/mcp.md), [page](https://verifymcp.io/servers/com-hasdata-chatgpt/mcp)
- npm · `@hasdata/chatgpt-mcp`: 38/100, [markdown](https://verifymcp.io/servers/com-hasdata-chatgpt/hasdata-chatgpt-mcp.md), [page](https://verifymcp.io/servers/com-hasdata-chatgpt/hasdata-chatgpt-mcp)
- pypi · `hasdata-chatgpt-mcp`: 34/100, [markdown](https://verifymcp.io/servers/com-hasdata-chatgpt/hasdata-chatgpt-mcp-2.md), [page](https://verifymcp.io/servers/com-hasdata-chatgpt/hasdata-chatgpt-mcp-2)

## Channel facts

- Endpoint: `https://mcp.hasdata.com/mcp?apis=chatgpt`
- Transports: `streamable-http`
- Auth: `required`
- 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-16.

- **Endpoint Security**: 97/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 supports Client ID Metadata Documents, the current MCP client-registration mechanism.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 65/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 393 tokens (~393/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 33/100
  - Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the HasData ChatGPT MCP server?

HasData ChatGPT is a hosted endpoint at https://mcp.hasdata.com/mcp?apis=chatgpt, 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-hasdata-chatgpt 'https://mcp.hasdata.com/mcp?apis=chatgpt'
```

### Cursor

```json
{
  "mcpServers": {
    "com-hasdata-chatgpt": {
      "url": "https://mcp.hasdata.com/mcp?apis=chatgpt"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-hasdata-chatgpt": {
      "type": "http",
      "url": "https://mcp.hasdata.com/mcp?apis=chatgpt"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-hasdata-chatgpt]
url = "https://mcp.hasdata.com/mcp?apis=chatgpt"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-hasdata-chatgpt": {
      "type": "remote",
      "url": "https://mcp.hasdata.com/mcp?apis=chatgpt",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-hasdata-chatgpt --url 'https://mcp.hasdata.com/mcp?apis=chatgpt' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-hasdata-chatgpt:
    url: "https://mcp.hasdata.com/mcp?apis=chatgpt"
```

### Netclaw

```json
{
  "McpServers": {
    "com-hasdata-chatgpt": {
      "Transport": "http",
      "Url": "https://mcp.hasdata.com/mcp?apis=chatgpt"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-hasdata-chatgpt -t streamable-http -u 'https://mcp.hasdata.com/mcp?apis=chatgpt'
```

### Other

```json
{
  "mcpServers": {
    "com-hasdata-chatgpt": {
      "type": "http",
      "url": "https://mcp.hasdata.com/mcp?apis=chatgpt"
    }
  }
}
```

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-15 (score 83, +1)

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

### 2026-10-13 (score 82, +1)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

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

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

### 2026-10-10 (score 80, +1)

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

### 2026-10-08 (score 79, 0)

- [functional improvement] Stability: unverified → 0.07

### 2026-10-06 (score 79)

First indexed and scored.

## MCP tools (1)

### `hasdata_chatgpt_chat_getChatgptAnswer` (~319 tokens)

chatgpt_chat: GET /

Get ChatGPT Answer

Sends a prompt to ChatGPT anonymously and returns the answer as markdown text, plus every web source ChatGPT consulted with its domain, page title, snippet, publication date and thumbnail, the links rendered inside the answer, the conversation title ChatGPT generated, the model that answered, and whether a web search was used. The language of the answer follows the prompt — write the prompt in the language you want back, or ask for one in it. Set the frame of reference for words like "today" with timezone. Each request is a fresh conversation with no memory of earlier ones. Use to answer questions with cited sources, to ground an agent or RAG pipeline in ChatGPT's web-search results, to summarise current events with their sources, or to build datasets of model answers.

Input parameters:

- `prompt` (string, required): The question or instruction to send to ChatGPT, up to 8000 characters. A prompt that asks about recent events makes ChatGPT search the web and return sources; a general-knowledge prompt is answered f…
- `timezone` (string): IANA time zone name, for example `America/Chicago` or `Europe/Berlin`. It sets what ChatGPT treats as the current date and time, which matters for prompts that say "today", "this week" or "latest".

## Diagnostics

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

## Score history

- 2026-10-16: 83
- 2026-10-15: 83
- 2026-10-14: 82
- 2026-10-13: 82
- 2026-10-12: 81
- 2026-10-10: 80
- 2026-10-08: 79
- 2026-10-06: 79

## Common questions

### What is the HasData ChatGPT MCP server?

HasData ChatGPT is an MCP server listed in the public MCP registry as com.hasdata/chatgpt. Send a prompt to ChatGPT anonymously and get the answer with its web sources, as JSON. This page covers its hosted endpoint (https://mcp.hasdata.com/mcp?apis=chatgpt).

### Is the HasData ChatGPT MCP server safe to use?

HasData ChatGPT scores 83 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 HasData ChatGPT MCP server expose?

HasData ChatGPT exposes 1 tool: hasdata_chatgpt_chat_getChatgptAnswer. Their descriptions and schemas cost roughly 319 tokens of context every time the server is loaded.

### Does the HasData ChatGPT MCP server require authentication?

Yes. HasData ChatGPT 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 HasData ChatGPT MCP server still maintained?

HasData ChatGPT is still listed as active in the MCP registry. We last reached this channel on 16 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://mcp.hasdata.com/mcp?apis=chatgpt
- Authorisation metadata: https://mcp.hasdata.com/.well-known/oauth-protected-resource/mcp
- Repository: https://github.com/HasData/chatgpt-mcp
- Website: https://hasdata.com/apis/chatgpt-api
- Changelog RSS feed: https://verifymcp.io/servers/com-hasdata-chatgpt/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-hasdata-chatgpt/mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-hasdata-chatgpt/mcp