# Datacircle (remote · api.datacircle.dev)

Datacircle lists all the GTM APIs

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

> **Dead**: every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically.

## Components

- remote · `api.datacircle.dev`: 0/100 (this document), [markdown](https://verifymcp.io/servers/dev-datacircle-datacircle/api.md), [page](https://verifymcp.io/servers/dev-datacircle-datacircle/api)

## Channel facts

- Endpoint: `https://api.datacircle.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `2.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-20.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - 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**: 63/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 409 tokens (~204/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 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.

**Unverified: 1 category.** A category scored 0 because we could not verify it: 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 Datacircle MCP server?

Datacircle is a hosted endpoint at https://api.datacircle.dev/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 dev-datacircle-datacircle 'https://api.datacircle.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "dev-datacircle-datacircle": {
      "url": "https://api.datacircle.dev/mcp"
    }
  }
}
```

### VS Code

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

### Codex

```toml
[mcp_servers.dev-datacircle-datacircle]
url = "https://api.datacircle.dev/mcp"
```

### opencode

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

### OpenClaw

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

### Hermes

```yaml
mcp_servers:
  dev-datacircle-datacircle:
    url: "https://api.datacircle.dev/mcp"
```

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "dev-datacircle-datacircle": {
      "type": "http",
      "url": "https://api.datacircle.dev/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-20 (score 0, −23)

- [security improvement] Authorization: unverified → partial
- [security improvement] Injection markers: unverified → pass
- [security improvement] Transport: fail → pass
- [security] First check of Judged manipulation: pass
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] MCP protocol: unverified → pass
- [functional] First check of Schema quality: fail
- [functional] First check of Destructive annotations: pass
- [functional] First check of Schema quality: fail
- [functional] First check of Schema quality: good
- [functional] First check of Tool coverage: 100

### 2026-10-14 (score 23, −14)

- [security regression] Transport: unverified → fail
- [security regression] Authorization: pass → unverified
- [security] Tool safety: Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- [functional] Tool coverage: Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- [functional] Capabilities: Capabilities not yet verified: we couldn't read the endpoint's capabilities.
- [functional] Schema quality: Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.

### 2026-10-11 (score 37, +1)

- [security improvement] Authorization: partial → pass

### 2026-10-10 (score 36)

First indexed and scored.

## MCP tools (2)

### `list_apis` (~40 tokens)

List the GTM APIs

The GTM APIs on Datacircle's sheet, each with how many plans and providers it has. Pass an API's name to search_plans.

### `search_plans` (~253 tokens)

Search the API plans

The sheet's rows, one for each plan of each call, each with every key of the sheet's JSON download: its provider, plan, billing, $ per 1,000 (perThousand), score out of 100 (score), rate limits, speed, the fields it returns and the pages we read it from. total counts every row found, plans holds up to limit of them from offset. What each key means: https://datacircle.dev/fields

Input parameters:

- `api` (string): The API, its name as list_apis gives it. Every API when left out.
- `limit` (integer): How many plans to give, 1 to 50. 10 when left out.
- `offset` (integer): How many found plans to skip first. 0 when left out.
- `query` (string): Words that must all appear in the provider's or plan's name, ignoring case and accents.
- `sort` (string): score, the default: best first, as on the sheet at datacircle.dev, each API's plans together, unscored plans last. provider: A to Z. price: $ per 1,000, lowest first.

## Diagnostics

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

## Score history

- 2026-10-20: 0
- 2026-10-19: 23
- 2026-10-18: 23
- 2026-10-17: 23
- 2026-10-16: 23
- 2026-10-15: 23
- 2026-10-14: 23
- 2026-10-13: 37
- 2026-10-12: 37
- 2026-10-11: 37
- 2026-10-10: 36

## Common questions

### What is the Datacircle MCP server?

Datacircle is an MCP server listed in the public MCP registry as dev.datacircle/datacircle. Datacircle lists all the GTM APIs. This page covers its hosted endpoint (https://api.datacircle.dev/mcp).

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

Datacircle scores 0 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 Datacircle MCP server expose?

Datacircle exposes 2 tools: list_apis, search_plans. Their descriptions and schemas cost roughly 293 tokens of context every time the server is loaded.

### Does the Datacircle MCP server require authentication?

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

### Is the Datacircle MCP server still maintained?

Datacircle has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 19 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.datacircle.dev/mcp
- Website: https://datacircle.dev/
- Changelog RSS feed: https://verifymcp.io/servers/dev-datacircle-datacircle/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-datacircle-datacircle/api.json
- HTML version of this page: https://verifymcp.io/servers/dev-datacircle-datacircle/api