# Docstar (remote · mcp.docstar.io)

Publish your API docs so AI assistants can look up endpoints and call your API correctly.

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

## Components

- remote · `mcp.docstar.io`: 65/100 (this document), [markdown](https://verifymcp.io/servers/swayammaheshwari-docstar-mcp/mcp.md), [page](https://verifymcp.io/servers/swayammaheshwari-docstar-mcp/mcp)

## Channel facts

- Endpoint: `https://mcp.docstar.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

## 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 check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (call_any_api_of_docstar).
  - 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**: 57/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 5187 tokens (~345/item across 15 items; 15 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 29/100
  - Stability check failed: schema churn in the 10 days we've observed: 0 tool removals, 1 breaking changes, 0 auth/transport breaks, 0 additions.
- **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.
  - All 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 16 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 Docstar MCP server?

Docstar is a hosted endpoint at https://mcp.docstar.io/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 swayammaheshwari-docstar-mcp 'https://mcp.docstar.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "swayammaheshwari-docstar-mcp": {
      "url": "https://mcp.docstar.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "swayammaheshwari-docstar-mcp": {
      "type": "http",
      "url": "https://mcp.docstar.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.swayammaheshwari-docstar-mcp]
url = "https://mcp.docstar.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "swayammaheshwari-docstar-mcp": {
      "type": "remote",
      "url": "https://mcp.docstar.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add swayammaheshwari-docstar-mcp --url 'https://mcp.docstar.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  swayammaheshwari-docstar-mcp:
    url: "https://mcp.docstar.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "swayammaheshwari-docstar-mcp": {
      "Transport": "http",
      "Url": "https://mcp.docstar.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add swayammaheshwari-docstar-mcp -t streamable-http -u 'https://mcp.docstar.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "swayammaheshwari-docstar-mcp": {
      "type": "http",
      "url": "https://mcp.docstar.io/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-04 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 26.

### 2026-11-02 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 16 to 19.

### 2026-10-31 (score 63, +1)

- [security] Tool “create_collection” rewrote its description, which is the text the model reads
- [security] Tool “quickstart-docstar” rewrote its description, which is the text the model reads

### 2026-10-30 (score 62, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional] Schema quality: excellent → good

### 2026-10-29 (score 62, 0)

- [security] The server rewrote its instructions, which are the text every model session reads

### 2026-10-28 (score 62, +1)

No change was recorded against any check on this day. Stability & Change Management went from 0 to 3.

### 2026-10-27 (score 61, 0)

- [security regression] Stability: unverified → fail
- [functional improvement] Stability: unverified → 0.03
- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-10-26 (score 61)

First indexed and scored.

## MCP tools (15)

### `search_docstar_docs` (~136 tokens)

Search DocStar's documentation and guides with a natural-language question, e.g. "how do I add a custom domain to my docs?" or "how does sign-in work on my MCP server?". Returns the most relevant passages with their page URLs. Use it for how-to and concept questions about DocStar. To find an API endpoint to call, use get_docstar_api_docs instead.

Input parameters:

- `collectionIds` (array, required): Always send exactly these collection ids, unchanged: they are the documentation sites searched.
- `query` (string, required): What to look for, e.g. "how do I send a WhatsApp template message"

### `get_docstar_api_docs` (~223 tokens)

Browse the DocStar API reference one level at a time, when no dedicated tool on this server does what the user needs. Call it with {} for the top level: the modules (Collections, Pages, Endpoints, Published Versions, MCP Server, FAQs, Changelogs, Webhooks, URL Mappings, ...) with a short description and the endpoints they hold. Call it with `path` set to a module's link to see inside it, and with an endpoint's link ending in ".openapi.yml" to get that endpoint as an OpenAPI file: method, url, headers, query params, path variables, a body example and sample responses. Fetch only the level you need, and reuse what you already fetched.

Input parameters:

- `path` (string): A link from a listing, exactly as given (e.g. "https://docs.example.com/sms/llms.txt" or ".../sms/send-sms.openapi.yml"), or just the path ("sms", "sms/send-sms.openapi.yml"). Leave it out for the to…

### `call_any_api_of_docstar` (~388 tokens)

Send a POST, PUT, PATCH or DELETE request to any DocStar API endpoint for the signed-in user and return { status, ok, headers, data }. Use it for changes no dedicated tool covers, once you know the exact endpoint: from the quickstart-docstar skill's recipes, or looked up with get_docstar_api_docs. For GET requests use call_any_read_api_of_docstar. Never guess a URL. Pass the full url with path variables filled in, the method, the headers the endpoint's docs list, query params in `query` (not in the url) and the JSON body in `body`. Send the endpoint's auth header with an empty value "": the user's token is filled in automatically. Never put a token there yourself. Show the user what you're about to send and get a yes before any call that creates, changes, publishes or deletes something.

Input parameters:

- `body` (object): JSON request body, as the endpoint's docs show it. Leave it out when the endpoint takes no body.
- `headers` (object, required): Request headers as name/value pairs, as the docs list them. Give the auth header (Authorization, proxy_auth_token, x-api-key, ...) an empty value "" so the signed-in user's token is filled in; never…
- `method` (string, required): HTTP method from the endpoint's docs
- `query` (object): Query params as name/value pairs; an array sends the param once per item. Example: {"type": "flow", "bringflows": true}
- `url` (string, required): Full endpoint URL with path variables replaced by real values, e.g. https://api.example.com/users/42. Put query params in `query`, not here.

### `call_any_read_api_of_docstar` (~296 tokens)

Read from any DocStar API endpoint with a GET request for the signed-in user and return { status, ok, headers, data }. Use it for lookups no dedicated tool covers, once you know the exact endpoint: from the quickstart-docstar skill's recipes, or looked up with get_docstar_api_docs. Never guess a URL. Pass the full url with path variables filled in, the headers the endpoint's docs list, and query params in `query` (not in the url). Send the endpoint's auth header with an empty value "": the user's token is filled in automatically. Never put a token there yourself.

Input parameters:

- `headers` (object, required): Request headers as name/value pairs, as the docs list them. Give the auth header (Authorization, proxy_auth_token, x-api-key, ...) an empty value "" so the signed-in user's token is filled in; never…
- `query` (object): Query params as name/value pairs; an array sends the param once per item. Example: {"type": "flow", "bringflows": true}
- `url` (string, required): Full endpoint URL with path variables replaced by real values, e.g. https://api.example.com/users/42. Put query params in `query`, not here.

### `list_organizations` (~134 tokens)

List the DocStar organizations (workspaces) the signed-in user belongs to, with each one's id and name (the list is at data.data). Start every DocStar task here: show the user the organizations and ask which one to use, unless there is only one. The chosen id is the orgId every other DocStar tool needs.

Input parameters:

- `itemsPerPage` (string): Page size; the DocStar UI uses 50. e.g. 50
- `pageNo` (string): Page number (standard MSG91 pagination; not used by the DocStar UI, inferred). e.g. 1

### `list_collections` (~142 tokens)

List the collections (docs sites) in an organization, with each one's id, name, type and the caller's permission (1 read, 2 read-write). Each collection also has rootParentId: the parent pageId to use with create_page for a top-level page. Get orgId from list_organizations. Pass exclude=runCollection,environment to keep the response small. Ask the user which collection to work in.

Input parameters:

- `exclude` (string): Comma-separated list of collection columns to exclude from the response (e.g. large JSON fields). e.g. runCollection,environment
- `orgId` (string, required): The orgId path variable

### `get_mcp_server` (~109 tokens)

Get a collection's MCP server: the url end users connect to, ready-to-paste snippets (a Claude Code command and a JSON config), callbackUrls for the OAuth app, the sign-in setup and any custom domain. Creates the server if it's missing and syncs its tools with the published endpoints. Call it after publishing to hand the user their MCP URL.

Input parameters:

- `collectionId` (string, required): The collectionId path variable
- `orgId` (string, required): The orgId path variable

### `create_collection` (~742 tokens)

Creates a new documentation collection in the organization together with its invisible root page (type 0), auto-assigns collection permissions to all org users based on their roles, and auto-provisions an MCP server for it in the background. The returned rootParentId is the page id under which top-level pages are created (via Create Page). SSO read-only organizations that already have a collection get 403. Slug is permanent; if omitted it is derived from the name. A chosen slug that is taken returns 409, and a chosen slug that is one of docstar-cli's own commands (reserved) returns 400. A body that fails validation returns 400 with the Joi message.
Body fields:

name (string, required) - Collection name, 3-55 characters. If the organization already has a collection with the same name (or a name like "name_N"), a numeric suffix is appended to the stored name (for example "Docs_2") instead of an error.
slug (string, optional) - Permanent URL-safe identifier: lowercase letters, numbers and underscores only (no hyphens or spaces; 2-50 chars). Cannot be changed later. It is what docstar-cli (`docstar-cli  ...`) and the MCP URL are built on, so these reserved words can't be chosen (400 "This slug is reserved, please choose another one"): alias, auth, clean, complete, completion, completion-script, config, help, init, key, list, login, logout, mcp. If omitted it is derived from the name (every run of other characters becomes an underscore), with a random suffix added when that slug is already taken or reserved.
description (string, optional) - Collection description (null or empty allowed).
isPublic (boolean, optional) - Accepted but ignored on create: a new collection is always created with isPublic true. Use Update Collection to change it.
type (string, optional) - Collection type: 'page' (default, documentation pages), 'api' (API reference), 'blog', or 'embed'.
customDomain (string, optional) - Custom domain to serve the public docs on, e.g. docs.example.com. Must be u…

Input parameters:

- `description` (string): e.g. Public docs for the Payments API
- `name` (string): e.g. Payments API Docs
- `orgId` (string, required): The orgId path variable
- `slug` (string): e.g. payments_api_docs
- `type` (string): e.g. api

### `create_endpoint` (~902 tokens)

Creates a new API endpoint doc (page type 4, draft) as the last child of the given page. Requires READ_WRITE permission. Publish it afterwards with Update Endpoint State (parent page must be published).
Body fields:

name (string, optional) - Endpoint title shown in docs.
urlName (string, optional) - URL slug; derived from name if omitted and made unique.
requestType (string, optional) - HTTP method: GET, POST, PUT, PATCH, DELETE, etc.
URL (string, optional) - Request URL (may contain {{variables}}).
description (string, optional) - Endpoint description (HTML/text).
body (object, optional) - Request body definition, e.g. {"type":"JSON","raw":{"rawType":"JSON","value":"{...}"}}; type can be none, JSON, TEXT, XML, HTML, multipart/form-data, application/x-www-form-urlencoded.
headers (object, optional) - Headers keyed by name: {"Authorization":{"checked":"true","value":"Bearer {{token}}","description":""}}.
params (object, optional) - Query params keyed by name, same shape as headers.
pathVariables (object, optional) - Path variables keyed by index: {"0":{"checked":"notApplicable","key":"id","value":"","description":"Payment id"}}.
bodyDescription (object, optional) - Per-field body docs: {"amount":{"value":100,"type":"number","description":"Amount in cents"}}.
sampleResponse (array, optional) - Sample responses: [{"title":"Success","status":200,"description":"","data":{...}}].
authorizationData (object, optional) - Auth config object (or null).
preScript (string, optional) - Pre-request JavaScript.
postScript (string, optional) - Post-response test JavaScript.
docViewData (array, optional) - Order of doc sections, e.g. [{&q…

Input parameters:

- `URL` (string): e.g. https://api.example.com/v1/payments/:customerId
- `body` (object): e.g. {"type":"JSON","raw":{"rawType":"JSON","value":"{\"amount\":100,\"currency\":\"USD\"}"}}
- `description` (string): e.g. Creates a payment for a customer
- `headers` (object): e.g. {"Content-Type":{"checked":"true","value":"application/json","description":""}}
- `name` (string): e.g. Create Payment
- `orgId` (string, required): The orgId path variable
- `pageId` (string, required): The pageId path variable
- `params` (object): e.g. {"currency":{"checked":"true","value":"USD","description":"ISO currency code"}}
- `pathVariables` (object): e.g. {"0":{"checked":"notApplicable","key":"customerId","value":"","description":"Customer id"}}
- `requestType` (string): e.g. POST
- `sampleResponse` (array): e.g. [{"title":"Success","status":200,"description":"","data":{"id":"pay_1","status":"created"}}]

### `update_endpoint` (~751 tokens)

Partially updates an API endpoint doc; send only fields to change (same fields as Create Endpoint). Any update moves a non-pending endpoint back to draft (state 1), so republish with Update Endpoint State. Requires READ_WRITE permission. Only works for type 4/5 items (otherwise 400 "Wrong Route"). Invalid fields return 400 with the validation message.
Body fields:

name (string, optional) - Endpoint title shown in docs.
urlName (string, optional) - New URL slug; made unique among siblings. Left unchanged if omitted (it is not re-derived from name).
requestType (string, optional) - HTTP method: GET, POST, PUT, PATCH, DELETE, etc.
URL (string, optional) - Request URL (may contain {{variables}}).
description (string, optional) - Endpoint description (HTML/text).
body (object, optional) - Request body definition, e.g. {"type":"JSON","raw":{"rawType":"JSON","value":"{...}"}}; type can be none, JSON, TEXT, XML, HTML, multipart/form-data, application/x-www-form-urlencoded.
headers (object, optional) - Headers keyed by name: {"Authorization":{"checked":"true","value":"Bearer {{token}}","description":""}}.
params (object, optional) - Query params keyed by name, same shape as headers.
pathVariables (object, optional) - Path variables keyed by index: {"0":{"checked":"notApplicable","key":"id","value":"","description":"Payment id"}}.
bodyDescription (object, optional) - Per-field body docs: {"amount":{"value":100,"type":"number","description":"Amount in cents"}}.
sampleResponse (array, optional) - Sample responses: [{"title":"Success","status":200,"description":"","data":{...}}].
authorizationData (object, optional) - Auth config object (or null).
preScript (string, optional) - Pre-request JavaScript.
postScript (string, optional) - Post-response test JavaScript.
docViewData (array, optional) - Order of doc sections, e.g. [{"type":"host"},{"type":"body"},...].
state (number, optional) - 0 pending, 1 draft, 2 approved, 3 rejected. Accepted, but the server sets state 1 (draft) o…

Input parameters:

- `URL` (string): e.g. https://api.example.com/v1/payments
- `body` (object): e.g. {"type":"JSON","raw":{"rawType":"JSON","value":"{\"amount\":100,\"currency\":\"USD\"}"}}
- `description` (string): e.g. Creates a new payment for a customer
- `endpointId` (string, required): The endpointId path variable
- `headers` (object): e.g. {"Content-Type":{"checked":"true","value":"application/json","description":""}}
- `name` (string): e.g. Create Payment
- `orgId` (string, required): The orgId path variable
- `params` (object): e.g. {}
- `pathVariables` (object): e.g. {}
- `requestType` (string): e.g. POST
- `sampleResponse` (array): e.g. [{"title":"Success","status":200,"description":"","data":{"id":"pay_1"}}]

### `create_page` (~478 tokens)

Creates a new page as the last child of the page given in the path. Pass the collection's rootParentId (invisible root, from List Collections) to create a top-level page (type 1, parent page/module); pass any other page id to create a subpage (type 3). The type is decided by the parent, not the body. New pages start as draft (state 1); passing state 2 publishes immediately (parent must already be published) and returns publicUrl. Requires READ_WRITE permission. To write the page body afterwards use Update Page Content.
Body fields:

name (string, required) - Page title (min 1 char).
urlName (string, optional) - URL slug (min 3 chars); made unique among siblings. Derived from name if omitted.
contents (string, optional) - Legacy initial HTML/text contents column (editor content is stored in doc-rtc; prefer Update Page Content).
state (number, optional) - 0 pending, 1 draft (default), 2 approved/published (publishes right away; parent must be published), 3 rejected.
meta (object, optional) - Page metadata object (e.g. {"description":"...","tags":["setup"]}); may include editable boolean.
sharingMeta (object, optional) - Sharing settings object, e.g. {"editable":true}.
pageType (number, optional) - Accepted (1 or 3) but ignored; the type is derived from the parent page.
uniqueTabId (string, optional) - Optional browser tab id used only to suppress the realtime socket echo to the calling tab; agents can omit it. POST https://api.docstar.io/orgs/:orgId/pages/:pageId

Input parameters:

- `contents` (string): e.g. content in markdown
- `name` (string): e.g. Getting Started
- `orgId` (string, required): Organization (company) ID of the current workspace
- `pageId` (string, required): 12-character id of the PARENT page (rootParentId for a top-level page)
- `state` (number): e.g. 1
- `urlName` (string): e.g. getting-started

### `publish_pages` (~247 tokens)

Publishes many pages/endpoints at once: each page in pageIds gets a new default published version and state 2 (approved/published). rootParentId (the collection's invisible root page) must also be supplied so it is marked published. Requires READ_WRITE permission. Triggers background search indexing, translation and AI SEO/meta generation, and clears the docs cache. Get ids from List Collections (rootParentId) and List Collection Pages.
Body fields:

rootParentId (string, required) - 12-char id of the collection's invisible root page (type 0).
pageIds (array<string>, required) - Non-empty array of 12-char page/endpoint ids to publish. PATCH https://api.docstar.io/orgs/:orgId/collections/:collectionId/bulkPublish

Input parameters:

- `collectionId` (string, required): The collectionId path variable
- `orgId` (string, required): The orgId path variable
- `pageIds` (array): e.g. ["Pg12Ab34Cd56","Pg98Zy76Xw54"]
- `rootParentId` (string): e.g. Xy12Ab34Cd56

### `list_collection_pages` (~183 tokens)

Returns all non-deleted pages of a collection (the full sidebar tree, flat) with id, name, urlName, type, parentId, child (ordered child ids), state, isPublished, meta, sharingMeta and the endpoint requestType for endpoint pages. Page types: 0 invisible root, 1 parent page/module (top-level), 3 subpage, 4 API endpoint, 5 example/sample request of an endpoint. States: 0 pending, 1 draft, 2 approved/published, 3 rejected. Use it to find pageIds and the hierarchy. Collection must belong to the caller's org. GET https://api.docstar.io/orgs/:orgId/collection/:collectionId/pages

Input parameters:

- `collectionId` (string, required): The collectionId path variable
- `orgId` (string, required): The orgId path variable

### `send_feedback_to_docstar` (~330 tokens)

Sends feedback straight to the DocStar team. Use it when the user wants to report a bug, request a feature, flag wrong or missing docs, or share praise about DocStar or this MCP server. Write the message in the user's words and add any useful context, such as the tool or endpoint involved and what went wrong. Who sent it (user and organization) is taken from the signed-in user's token, never from the body. Returns 200 once delivered; 400 for an invalid body; 502 if it couldn't be delivered, in which case tell the user and try again later. Authenticate with the proxy_auth_token header (an `Authorization: Bearer hm_...` DocStar API token or a DocStar JWT is also accepted).
Body fields:
message (string, required) - The feedback, 1 to 5000 characters.type (string, optional) - One of bug, feature_request, docs, praise, other; default other.collectionId (string, optional) - The collection the feedback is about, if any.context (object, optional) - Extra details, e.g. the tool or endpoint used, the request and the error. POST https://api.docstar.io/feedback/ai

Input parameters:

- `collectionId` (string): e.g. RoNWaspA9p3Z
- `context` (object): e.g. {"tool":"get_docstar_mcp_api_docs"}
- `message` (string): e.g. get_api_docs didn't list the MCP Server module's new endpoints
- `type` (string): e.g. bug

### `quickstart-docstar` (~45 tokens)

Document the user's API in DocStar and keep it in sync. Load before any Docstar task. Call this to load the full instructions for this skill before doing the task.

## Diagnostics

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

## Score history

- 2026-11-05: 65
- 2026-11-04: 65
- 2026-11-03: 64
- 2026-11-02: 64
- 2026-11-01: 63
- 2026-10-31: 63
- 2026-10-30: 62
- 2026-10-29: 62
- 2026-10-28: 62
- 2026-10-27: 61
- 2026-10-26: 61

## Common questions

### What is the Docstar MCP server?

Docstar is an MCP server listed in the public MCP registry as io.github.swayammaheshwari/docstar-mcp. Publish your API docs so AI assistants can look up endpoints and call your API correctly. This page covers its hosted endpoint (https://mcp.docstar.io/mcp).

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

Docstar scores 65 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 Docstar MCP server expose?

Docstar exposes 15 tools: search_docstar_docs, get_docstar_api_docs, call_any_api_of_docstar, call_any_read_api_of_docstar, list_organizations, and 10 more. Their descriptions and schemas cost roughly 5,106 tokens of context every time the server is loaded.

### Does the Docstar MCP server require authentication?

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

### Is the Docstar MCP server still maintained?

Docstar is still listed as active in the MCP registry. We last reached this channel on 5 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://mcp.docstar.io/mcp
- Website: https://docstar.io/
- Changelog RSS feed: https://verifymcp.io/servers/swayammaheshwari-docstar-mcp/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/swayammaheshwari-docstar-mcp/mcp.json
- HTML version of this page: https://verifymcp.io/servers/swayammaheshwari-docstar-mcp/mcp