io.capawesome/mcp
REMOTE · MCP.CAPAWESOME.IO · 2 COMPONENTS · SCANNED SEP 25
The official MCP server for Capawesome documentation and Capawesome Cloud.
Available components
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. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability68
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management53
- Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (33% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
remote · mcp.capawesome.io
claude mcp add --transport http io-capawesome-mcp 'https://mcp.capawesome.io/mcp'
{
"mcpServers": {
"io-capawesome-mcp": {
"url": "https://mcp.capawesome.io/mcp"
}
}
} {
"servers": {
"io-capawesome-mcp": {
"type": "http",
"url": "https://mcp.capawesome.io/mcp"
}
}
} [mcp_servers.io-capawesome-mcp] url = "https://mcp.capawesome.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-capawesome-mcp": {
"type": "remote",
"url": "https://mcp.capawesome.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-capawesome-mcp --url 'https://mcp.capawesome.io/mcp' --transport streamable-http
mcp_servers:
io-capawesome-mcp:
url: "https://mcp.capawesome.io/mcp" {
"McpServers": {
"io-capawesome-mcp": {
"Transport": "http",
"Url": "https://mcp.capawesome.io/mcp"
}
}
} assistant mcp add io-capawesome-mcp -t streamable-http -u 'https://mcp.capawesome.io/mcp'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 23 Sept 26 +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.
- 21 Sept 26 +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.
- 19 Sept 26 +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.
- 16 Sept 26 +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.
- 14 Sept 26 +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.
- 12 Sept 26 +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.
- 10 Sept 26 +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.
- 9 Sept 26 −1
- 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 security
- Schema quality: 214 → 311 ▼ functional
- Stability: unverified → 0.03 ▲ functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 24 Sept 2026 · Probed https://mcp.capawesome.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=capawesome.io | CN=WE1,O=Google Trust Services,C=US | 17 Aug 2026 | 15 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 564f018d52fdd39d13f8ab7a4ecfcc1f |
| SANs: capawesome.io, mcp.capawesome.io, *.mcp.capawesome.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.capawesome.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| capawesome.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.capawesome.io/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.capawesome.io/mcp | HTTPS enforced | 301 | https://mcp.capawesome.io/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_doc_page Read a documentation page ~188
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.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | 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. |
No output schema declared.
No examples provided.
list_blog_posts List recent blog posts ~122
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_docs Search Capawesome documentation ~345
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | The maximum number of results to return, e.g. 5. Defaults to 10, maximum 25. |
| query | string | yes | 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… |
| Name | Type | Req | Description |
|---|---|---|---|
| results | array | yes | – |
No examples provided.
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.