Skip to content

GitBook MCP by usefulapi

io.usefulapi/gitbookusefulapi.iostreamable-httpv1.40.4Scanned

Read spaces, collections, pages and content; search docs and manage GitBook organization spaces.

14 tools: 2 can delete or cancel things and 12 only read.

Tools: 2 delete, 0 irreversible, 0 write, 12 read.
  • Reads private data · 0
  • Reads text others write · 1
  • Can send data out · 0
  • No findings

The remote endpoint did not answer the last look. Remote posture

Anlyon alternative

2 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the GitBook MCP by usefulapi can do

The GitBook MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 14 tools. It can delete or cancel things (2 tools: gitbook_create_change_request and gitbook_update_change_request). 12 tools only read.

1 tool brings in text other people can write (gitbook_list_comments).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Last scanned Oct 25, 2026, version 1.40.4.

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.

14 tools

Deletes or cancels 2Claude Code: deny
  • gitbook_create_change_requestCreate a new draft change request (branch) in a space.No findings

    Why it is in this group

    • The name "gitbook_create_change_request" says "create": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Create a new draft change request (branch) in a space. Safe: creates a draft; publishes nothing. GitBook REST: POST /spaces/{spaceId}/change-requests.

    Annotations the server declares

    • title: Create change request
    • destructiveHint: true
  • gitbook_update_change_requestUpdate a change request's subject or status.No findings

    Why it is in this group

    • The name "gitbook_update_change_request" says "update": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Update a change request's subject or status. Edits draft metadata only. GitBook REST: PATCH /spaces/{spaceId}/change-requests/{changeRequestId}.

    Annotations the server declares

    • title: Update change request
    • destructiveHint: true
Only reads 12Show 12 read-only tools
  • gitbook_get_collectionGet a collection by its ID.No findings

    Why it is in this group

    • The name "gitbook_get_collection" says "get": a word for reading.
    Description, as the server wrote it
    Get a collection by its ID. GitBook REST: GET /collections/{collectionId}.

    Annotations the server declares

    • title: Get collection
    • readOnlyHint: true
  • gitbook_get_current_userGet the profile of the authenticated GitBook user.No findings

    Why it is in this group

    • The name "gitbook_get_current_user" says "get": a word for reading.
    Description, as the server wrote it
    Get the profile of the authenticated GitBook user. GitBook REST: GET /user.

    Annotations the server declares

    • title: Get current user
    • readOnlyHint: true
  • gitbook_get_pageGet a single page's content from a space by its page ID.No findings

    Why it is in this group

    • The name "gitbook_get_page" says "get": a word for reading.
    Description, as the server wrote it
    Get a single page's content from a space by its page ID. GitBook REST: GET /spaces/{spaceId}/content/page/{pageId}.

    Annotations the server declares

    • title: Get page
    • readOnlyHint: true
  • gitbook_get_spaceGet full details of a space by its ID.No findings

    Why it is in this group

    • The name "gitbook_get_space" says "get": a word for reading.
    Description, as the server wrote it
    Get full details of a space by its ID. GitBook REST: GET /spaces/{spaceId}.

    Annotations the server declares

    • title: Get space
    • readOnlyHint: true
  • gitbook_list_change_requestsList change requests for a space.No findings

    Why it is in this group

    • The name "gitbook_list_change_requests" says "list": a word for reading.
    Description, as the server wrote it
    List change requests for a space. GitBook REST: GET /spaces/{spaceId}/change-requests.

    Annotations the server declares

    • title: List change requests
    • readOnlyHint: true
  • gitbook_list_collectionsList all collections in an organization.No findings

    Why it is in this group

    • The name "gitbook_list_collections" says "list": a word for reading.
    Description, as the server wrote it
    List all collections in an organization. GitBook REST: GET /orgs/{organizationId}/collections.

    Annotations the server declares

    • title: List collections
    • readOnlyHint: true
  • gitbook_list_commentsList top-level comments posted on a space.Reads text others writeNo findings

    Why it is in this group

    • The name "gitbook_list_comments" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe name "gitbook_list_comments" says "list" and "comment": it reads comments, which other people can write.
    • untrusted-inputThe description's first sentence says "list" and "comment": it reads comments, which other people can write.
    Description, as the server wrote it
    List top-level comments posted on a space. GitBook REST: GET /spaces/{spaceId}/comments.

    Annotations the server declares

    • title: List comments
    • readOnlyHint: true
  • gitbook_list_organizationsList the organizations the authenticated user belongs to.No findings

    Why it is in this group

    • The name "gitbook_list_organizations" says "list": a word for reading.
    Description, as the server wrote it
    List the organizations the authenticated user belongs to. GitBook REST: GET /orgs.

    Annotations the server declares

    • title: List organizations
    • readOnlyHint: true
  • gitbook_list_pagesList all pages in a space with their hierarchy and metadata.No findings

    Why it is in this group

    • The name "gitbook_list_pages" says "list": a word for reading.
    Description, as the server wrote it
    List all pages in a space with their hierarchy and metadata. GitBook REST: GET /spaces/{spaceId}/content/pages.

    Annotations the server declares

    • title: List pages
    • readOnlyHint: true
  • gitbook_list_spacesList all spaces in an organization.No findings

    Why it is in this group

    • The name "gitbook_list_spaces" says "list": a word for reading.
    Description, as the server wrote it
    List all spaces in an organization. GitBook REST: GET /orgs/{organizationId}/spaces.

    Annotations the server declares

    • title: List spaces
    • readOnlyHint: true
  • gitbook_search_organizationSearch content across an entire organization.No findings

    Why it is in this group

    • The name "gitbook_search_organization" says "search": a word for reading.
    Description, as the server wrote it
    Search content across an entire organization. GitBook REST: GET /orgs/{organizationId}/search.

    Annotations the server declares

    • title: Search organization
    • readOnlyHint: true
  • gitbook_search_spaceFull-text search across all pages in a space.No findings

    Why it is in this group

    • The name "gitbook_search_space" says "search": a word for reading.
    Description, as the server wrote it
    Full-text search across all pages in a space. GitBook REST: GET /spaces/{spaceId}/search.

    Annotations the server declares

    • title: Search space
    • readOnlyHint: true

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 private-data or outbound.

Reads private data0
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.

The remote endpoint did not answer the last look

Looked at Nov 20, 2026, 19:36 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
no
HTTP status of an anonymous initialize
not observed
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
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

The probe stopped: The server redirected a POST to a different request.

Posture changes

  1. Oct 29, 2026
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 2 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://gitbook.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://gitbook.usefulapi.io to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to 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.

  1. PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 6 more).View diff
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 2 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://gitbook.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://gitbook.usefulapi.io to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed

Install

Pinned to version 1.40.4. Values in angle brackets are yours to fill in.

claude mcp add --transport http gitbook https://gitbook.usefulapi.io/mcp
claude mcp add --transport http gitbook https://gitbook.usefulapi.io/mcp

Run 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.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__gitbook__gitbook_get_current_user",
      "mcp__gitbook__gitbook_list_organizations",
      "mcp__gitbook__gitbook_list_spaces",
      "mcp__gitbook__gitbook_get_space",
      "mcp__gitbook__gitbook_list_pages",
      "mcp__gitbook__gitbook_get_page",
      "mcp__gitbook__gitbook_search_space",
      "mcp__gitbook__gitbook_search_organization",
      "mcp__gitbook__gitbook_list_collections",
      "mcp__gitbook__gitbook_get_collection",
      "mcp__gitbook__gitbook_list_change_requests",
      "mcp__gitbook__gitbook_list_comments"
    ],
    "ask": [],
    "deny": [
      "mcp__gitbook__gitbook_create_change_request",
      "mcp__gitbook__gitbook_update_change_request"
    ]
  }
}

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 gitbook. Review it before you use it.

Capability tags behind 1 rule
  • mcp__gitbook__gitbook_list_comments 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.usefulapi/gitbook/verify?hash=4da52a0eb84dea0afdcbef5484b5fe9f1218be6d2fedeaf8c4e8f490c8c149c0" | jq -e '.changed == false'

Pinned hash 4da52a0eb84d, from Oct 25, 2026, 23:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.usefulapi/gitbook/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.usefulapi/gitbook
[![Anlyon Radar](https://radar.anlyon.com/badge/io.usefulapi/gitbook.svg)](https://radar.anlyon.com/servers/io.usefulapi/gitbook)

Source: MCP Registry · repository. Synced Nov 18, 2026, 11:18 UTC.

GitBook MCP by usefulapi: questions and answers

Answered from the scan above, not from the publisher's description.

Is the GitBook MCP by usefulapi safe?

No scan can promise that. What its definitions show: 14 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the GitBook MCP by usefulapi delete data?

Yes. 2 tools can delete, cancel or revoke something: gitbook_create_change_request and gitbook_update_change_request.

Can the GitBook MCP by usefulapi 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 GitBook MCP by usefulapi have?

14 tools: 2 destructive, 12 read. gitbook_create_change_request, gitbook_update_change_request, gitbook_get_current_user, gitbook_list_organizations, gitbook_list_spaces, gitbook_get_space, gitbook_list_pages, gitbook_get_page and 6 more.

Does the GitBook MCP by usefulapi need sign-in or OAuth?

Its remote endpoint did not answer the last anonymous look.

Does the GitBook MCP by usefulapi send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the GitBook MCP by usefulapi changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Oct 25, 2026.