# QBCore Community Documentation (remote · qbcore.net)

Independent QBCore API, resource and troubleshooting docs with cited sources.

- Trust score: 75/100 (medium)
- Change this week: +2
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `qbcore.net`: 75/100 (this document), [markdown](https://verifymcp.io/servers/livvux-qbcore-docs/api-mcp.md), [page](https://verifymcp.io/servers/livvux-qbcore-docs/api-mcp)

## Channel facts

- Endpoint: `https://qbcore.net/api/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-11-05.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS not yet verified: we couldn't read the response headers to check for it.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but we couldn't connect to verify it.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- **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 not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

**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 QBCore Community Documentation MCP server?

QBCore Community Documentation is a hosted endpoint at https://qbcore.net/api/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 livvux-qbcore-docs 'https://qbcore.net/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "livvux-qbcore-docs": {
      "url": "https://qbcore.net/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "livvux-qbcore-docs": {
      "type": "http",
      "url": "https://qbcore.net/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.livvux-qbcore-docs]
url = "https://qbcore.net/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "livvux-qbcore-docs": {
      "type": "remote",
      "url": "https://qbcore.net/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add livvux-qbcore-docs --url 'https://qbcore.net/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  livvux-qbcore-docs:
    url: "https://qbcore.net/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "livvux-qbcore-docs": {
      "Transport": "http",
      "Url": "https://qbcore.net/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add livvux-qbcore-docs -t streamable-http -u 'https://qbcore.net/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "livvux-qbcore-docs": {
      "type": "http",
      "url": "https://qbcore.net/api/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-11-05 (score 75, 0)

- [security regression] Endpoint reachability: reachable → unreachable
- [security regression] Stability: 0.53 → unverified
- [security regression] Authorization: partial → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] HSTS header: pass → unverified
- [security regression] Transport: pass → fail
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified

### 2026-11-02 (score 75, +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-10-31 (score 74, +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.

### 2026-10-29 (score 73, +1)

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

### 2026-10-27 (score 72, +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-25 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 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-23 (score 70, +1)

- [security improvement] Authorization: unverified → partial
- [security improvement] Injection markers: unverified → pass
- [security improvement] HSTS header: unverified → pass
- [security improvement] Transport: fail → pass
- [functional improvement] Endpoint reachability: unreachable → reachable
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Stability: unverified → 0.13
- [functional improvement] MCP protocol: unverified → pass

### 2026-10-22 (score 69, 0)

- [security regression] Endpoint reachability: reachable → unreachable
- [security regression] Stability: 0.07 → unverified
- [security regression] Authorization: partial → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] HSTS header: pass → unverified
- [security regression] Transport: pass → fail
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

## MCP tools (3)

### `docs_search` (~63 tokens)

Search QBCore documentation

Find QBCore APIs, qb-* resources, setup and troubleshooting references. Returns bounded excerpts, canonical citations and recorded source-review metadata. Use docs_get for complete code.

Input parameters:

- `limit` (integer)
- `query` (string, required)
- `scope` (string)

Output parameters:

- `query` (string)
- `results` (array)
- `total` (integer)

### `docs_get` (~53 tokens)

Read a QBCore documentation page

Read Markdown at a canonical path returned by docs_search or docs_list. Follow nextOffset until null to obtain the complete article. Does not fetch arbitrary URLs.

Input parameters:

- `offset` (integer)
- `path` (string, required)

Output parameters:

- `content` (string)
- `description` (string)
- `format` (string)
- `nextOffset`
- `offset` (integer)
- `path` (string)
- `provenance` (object)
- `scope` (string)
- `title` (string)
- `totalChars` (integer)
- `url` (string)

### `docs_list` (~46 tokens)

List QBCore documentation pages

Browse the canonical documentation catalog by scope with deterministic pagination. Follow nextOffset until null.

Input parameters:

- `limit` (integer)
- `offset` (integer)
- `scope` (string)

Output parameters:

- `nextOffset`
- `pages` (array)
- `total` (integer)

## Diagnostics

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

## Score history

- 2026-11-05: 75
- 2026-11-04: 75
- 2026-11-03: 75
- 2026-11-02: 75
- 2026-11-01: 74
- 2026-10-31: 74
- 2026-10-30: 73
- 2026-10-29: 73
- 2026-10-28: 72
- 2026-10-27: 72
- 2026-10-26: 71
- 2026-10-25: 71
- 2026-10-24: 70
- 2026-10-23: 70
- 2026-10-22: 69
- 2026-10-21: 69
- 2026-10-20: 68
- 2026-10-19: 68

## Common questions

### What is the QBCore Community Documentation MCP server?

QBCore Community Documentation is an MCP server listed in the public MCP registry as io.github.Livvux/qbcore-docs. Independent QBCore API, resource and troubleshooting docs with cited sources. This page covers its hosted endpoint (https://qbcore.net/api/mcp).

### Is the QBCore Community Documentation MCP server safe to use?

QBCore Community Documentation scores 75 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 QBCore Community Documentation MCP server expose?

QBCore Community Documentation exposes 3 tools: docs_search, docs_get, docs_list. Their descriptions and schemas cost roughly 162 tokens of context every time the server is loaded.

### Does the QBCore Community Documentation MCP server require authentication?

Its publisher declares no required credentials for QBCore Community Documentation. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

### Is the QBCore Community Documentation MCP server still maintained?

QBCore Community Documentation is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 4 November 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://qbcore.net/api/mcp
- Website: https://qbcore.net/developers
- Changelog RSS feed: https://verifymcp.io/servers/livvux-qbcore-docs/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/livvux-qbcore-docs/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/livvux-qbcore-docs/api-mcp