# io.capawesome/mcp (remote · mcp.capawesome.io)

The official MCP server for Capawesome documentation and Capawesome Cloud.

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

## Components

- remote · `mcp.capawesome.io`: 77/100 (this document), [markdown](https://verifymcp.io/servers/io-capawesome-mcp/mcp.md), [page](https://verifymcp.io/servers/io-capawesome-mcp/mcp)
- npm · `@capawesome/mcp`: 50/100, [markdown](https://verifymcp.io/servers/io-capawesome-mcp/capawesome-mcp.md), [page](https://verifymcp.io/servers/io-capawesome-mcp/capawesome-mcp)

## Channel facts

- Endpoint: `https://mcp.capawesome.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.0.2`

## 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-09-24.

- **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**: 68/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 935 tokens (~311/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 53/100
  - Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **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.
  - Structured output schemas are declared (33% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the io.capawesome/mcp server?

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

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "io-capawesome-mcp": {
      "type": "http",
      "url": "https://mcp.capawesome.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-09-23 (score 77, +1)

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

### 2026-09-21 (score 76, +1)

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

### 2026-09-19 (score 75, +1)

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

### 2026-09-16 (score 74, +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-09-14 (score 73, +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-09-12 (score 72, +1)

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

### 2026-09-10 (score 71, +1)

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

### 2026-09-09 (score 70, −1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “get_doc_page” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 214 → 311
- [functional improvement] Stability: unverified → 0.03

## MCP tools (3)

### `search_docs` (~345 tokens)

Search Capawesome documentation

Search the Capawesome documentation, guides and blog by keyword. Use this first for any question about Capawesome SDKs (Capacitor and Cordova plugins such as Live Update, NFC, Biometrics), Capawesome Cloud (live updates, native builds, app store publishing, automations), Capawesome Insiders or the Capawesome CLI — the answer is almost always documented, and guessing plugin APIs or CLI flags produces broken code. Returns the best matching page sections with `title`, `url`, `snippet`, `section` and, for a hit inside a page, the `parentTitle` and `parentUrl` of that page. The same results are attached as structured content. Do not use this to read a full page: call `get_doc_page` with a `url` from these results. Do not use it to browse recent announcements or release notes: use `list_blog_posts`. Do not use it for anything about a concrete app, build, channel or deployment in Capawesome Cloud: those live behind the `cloud_*` tools.

Input parameters:

- `limit` (integer): The maximum number of results to return, e.g. 5. Defaults to 10, maximum 25.
- `query` (string, required): The search terms, e.g. "live update rollback" or "biometrics android setup". Plain keywords work best; no search operators are supported.
- `section` (string): Restrict the search to one part of the documentation: "sdks" (plugin references and guides), "cloud" (Capawesome Cloud), "insiders" (Capawesome Insiders) or "blog" (articles and release notes). Defau…

Output parameters:

- `results` (array)

### `get_doc_page` (~188 tokens)

Read a documentation page

Read the full source markdown of a Capawesome documentation or blog page. Use this after `search_docs` to read a page end to end before writing code against a plugin API, a CLI command or a Capawesome Cloud workflow — snippets from search results are deliberately short and regularly omit required configuration steps. Returns the page title, its URL and the page markdown including code samples, as it is authored but without the build metadata. Do not use this to find a page: it needs the exact URL or path, so run `search_docs` (or `list_blog_posts` for articles) first. Do not use it for pages outside capawesome.io.

Input parameters:

- `url` (string, required): The page URL or site-relative path, e.g. "https://capawesome.io/docs/cloud/live-updates/" or "cloud/live-updates/". Anchors are ignored; the whole page is returned.

### `list_blog_posts` (~122 tokens)

List recent blog posts

List the 20 most recent posts from the Capawesome blog, newest first. Use this when the question is about what is new — recent releases, announcements, monthly updates, deprecations or newly published guides. Returns `title`, `description`, `date`, `categories` and `url` per post; pass a `url` to `get_doc_page` to read the whole article. Do not use this to answer a topic question: the feed only carries the newest posts, so search the documentation and the blog archive with `search_docs` instead.

## Diagnostics

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

## Score history

- 2026-09-24: 77
- 2026-09-23: 77
- 2026-09-22: 76
- 2026-09-21: 76
- 2026-09-20: 75
- 2026-09-19: 75
- 2026-09-18: 74
- 2026-09-17: 74
- 2026-09-16: 74
- 2026-09-15: 73
- 2026-09-14: 73
- 2026-09-13: 72
- 2026-09-12: 72
- 2026-09-11: 71
- 2026-09-10: 71
- 2026-09-09: 70
- 2026-09-08: 71

## Common questions

### What is the io.capawesome/mcp server?

io.capawesome/mcp is listed in the public MCP registry as io.capawesome/mcp. The official MCP server for Capawesome documentation and Capawesome Cloud. This page covers its hosted endpoint (https://mcp.capawesome.io/mcp).

### Is the io.capawesome/mcp server safe to use?

io.capawesome/mcp scores 77 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 io.capawesome/mcp server expose?

io.capawesome/mcp exposes 3 tools: search_docs, get_doc_page, list_blog_posts. Their descriptions and schemas cost roughly 655 tokens of context every time the server is loaded.

### Does the io.capawesome/mcp server require authentication?

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

### Is the io.capawesome/mcp server still maintained?

io.capawesome/mcp is still listed as active in the MCP registry. We last reached this channel on 24 September 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.capawesome.io/mcp
- Repository: https://github.com/capawesome-team/mcp
- Website: https://capawesome.io/
- Changelog RSS feed: https://verifymcp.io/servers/io-capawesome-mcp/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-capawesome-mcp/mcp.json
- HTML version of this page: https://verifymcp.io/servers/io-capawesome-mcp/mcp