QBCore Community Documentation MCP server
io.github.Livvux/qbcore-docsLivvuxstreamable-httpv1.0.0Scanned
Independent QBCore API, resource and troubleshooting docs with cited sources.
3 tools: 3 only read.
- Reads private data · 3
- Reads text others write · 1
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
Decide which of this server's tools your agent can use.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the QBCore Community Documentation MCP server can do
The QBCore Community Documentation MCP server is published by the GitHub account Livvux. It has 3 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.
3 tools read private data (docs_search, docs_get and docs_list); 1 tool brings in text other people can write (docs_list).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 16, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
3 tools
Only reads 3Show 3 read-only tools
docs_getRead Markdown at a canonical path returned by docs_search or docs_list.Reads private dataNo findings
Why it is in this group
- The name "docs_get" says "get": a word for reading.
What it can reach
- private-dataThe name "docs_get" says "get" and "doc": it reads documents.
- private-dataThe description's first sentence says "read" and "doc": it reads documents.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
docs_listBrowse the canonical documentation catalog by scope with deterministic pagination.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "docs_list" says "list": a word for reading.
What it can reach
- private-dataThe name "docs_list" says "list" and "doc": it reads documents.
- untrusted-inputThe description's first sentence says "browse": it reads web pages, which anyone can write.
Description, as the server wrote it Browse the canonical documentation catalog by scope with deterministic pagination. Follow nextOffset until null.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
docs_searchFind QBCore APIs, qb-* resources, setup and troubleshooting references.Reads private dataNo findings
Why it is in this group
- The name "docs_search" says "search": a word for reading.
What it can reach
- private-dataThe name "docs_search" says "search" and "doc": it reads documents.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.
- Reads private data3
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:59 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 0
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http qbcore-docs https://qbcore.net/api/mcpclaude mcp add --transport http qbcore-docs https://qbcore.net/api/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__qbcore-docs__docs_search",
"mcp__qbcore-docs__docs_get",
"mcp__qbcore-docs__docs_list"
],
"ask": [],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as qbcore-docs. Review it before you use it.
Capability tags behind 3 rules
- mcp__qbcore-docs__docs_search private-data
- mcp__qbcore-docs__docs_get private-data
- mcp__qbcore-docs__docs_list private-data, untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.Livvux/qbcore-docs/verify?hash=96e2978d769d3689a2a959b9ab379df60ef2bbf05e97eaa1b91ea018ad37ee21" | jq -e '.changed == false'Pinned hash 96e2978d769d, from Nov 16, 2026, 18:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.Livvux/qbcore-docs/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.Livvux/qbcore-docs)Source: MCP Registry. Synced Oct 21, 2026, 18:17 UTC.
QBCore Community Documentation MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the QBCore Community Documentation MCP server safe?
- No scan can promise that. What its definitions show: 3 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.
Can the QBCore Community Documentation MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the QBCore Community Documentation MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the QBCore Community Documentation MCP server have?
- 3 tools: 3 read. docs_search, docs_get and docs_list.
Does the QBCore Community Documentation MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the QBCore Community Documentation MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the QBCore Community Documentation MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 16, 2026.