io.capawesome/capacitor-mcp
REMOTE · CAPACITOR-MCP.CAPAWESOME.IO · 2 COMPONENTS · SCANNED SEP 25
Unofficial MCP server for the Capacitor documentation, plugin list and blog.
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 Usability67
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1193 tokens (~298/item across 4 items; 4 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 Management57
- Stability observed for 17 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 (25% 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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/capacitor-mcp server?
io.capawesome/capacitor-mcp is a hosted endpoint at https://capacitor-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 · capacitor-mcp.capawesome.io
claude mcp add --transport http io-capawesome-capacitor-mcp 'https://capacitor-mcp.capawesome.io/mcp'
{
"mcpServers": {
"io-capawesome-capacitor-mcp": {
"url": "https://capacitor-mcp.capawesome.io/mcp"
}
}
} {
"servers": {
"io-capawesome-capacitor-mcp": {
"type": "http",
"url": "https://capacitor-mcp.capawesome.io/mcp"
}
}
} [mcp_servers.io-capawesome-capacitor-mcp] url = "https://capacitor-mcp.capawesome.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-capawesome-capacitor-mcp": {
"type": "remote",
"url": "https://capacitor-mcp.capawesome.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-capawesome-capacitor-mcp --url 'https://capacitor-mcp.capawesome.io/mcp' --transport streamable-http
mcp_servers:
io-capawesome-capacitor-mcp:
url: "https://capacitor-mcp.capawesome.io/mcp" {
"McpServers": {
"io-capawesome-capacitor-mcp": {
"Transport": "http",
"Url": "https://capacitor-mcp.capawesome.io/mcp"
}
}
} assistant mcp add io-capawesome-capacitor-mcp -t streamable-http -u 'https://capacitor-mcp.capawesome.io/mcp'
{
"mcpServers": {
"io-capawesome-capacitor-mcp": {
"type": "http",
"url": "https://capacitor-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.
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 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.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 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.
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 25 Sept 2026 · Probed https://capacitor-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 | 7 Sept 2026 | 6 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | e0aadde56ba539cc132169cd822c8e29 |
| SANs: capawesome.io, capacitor-mcp.capawesome.io, *.capacitor-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 capacitor-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://capacitor-mcp.capawesome.io/mcp | Verified | 200 | |
| http (plaintext) | http://capacitor-mcp.capawesome.io/mcp | HTTPS enforced | 301 | https://capacitor-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 ~256
Read the full markdown of a single page of the official Capacitor documentation. Use this after `search_docs` to read a page end to end before writing code against a plugin API, a CLI command or a native configuration, because search snippets are deliberately short and regularly omit required setup steps. Returns the page title, its URL, the documentation version and the complete page markdown including code samples. Do not use this to find a page: it needs an exact URL or path, so run `search_docs` first. Do not use it for pages outside capacitorjs.com — Capawesome plugins and Capawesome Cloud are covered by the Capawesome MCP server at https://mcp.capawesome.io/mcp, Ionic Framework UI components by the Ionic Framework MCP server at https://ionic-framework-mcp.capawesome.io/mcp.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The page URL or site-relative path, e.g. "https://capacitorjs.com/docs/apis/camera", "apis/camera" or "ios/configuration". An anchor is ignored; the whole page is returned. |
| version | string | – | Optional. Capacitor docs version. Defaults to v8. Match the major version of @capacitor/core in the user's package.json. |
No output schema declared.
No examples provided.
list_blog_posts List recent blog posts ~109
List the 10 most recent posts from the Capacitor tag of the official Ionic blog, newest first. Use this when the question is about what is new — recent releases, announcements or deprecations. The blog covers both Capacitor and Ionic Framework. Returns `title`, `date`, `tags`, `url` and `excerpt` per post. Do not use this to answer a documentation question: the feed only carries the newest posts, so search the documentation with `search_docs` instead.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_plugins List Capacitor plugins ~299
List Capacitor plugins: the official plugins maintained by the Capacitor team and community plugins from the awesome-capacitorjs list maintained by Capawesome. Use this to find a plugin for a native capability before writing custom native code, and to learn which package name and maintainer a capability belongs to. Returns `name`, `description`, `source`, `maintainer` and `url` per plugin, plus `core: true` for a plugin that ships with @capacitor/core and `experimental: true` for an experimental one. Results are ranked by relevance, with official Capacitor plugins ranked first, then plugins maintained by Capawesome, then other community plugins. Do not use this to read a plugin's API: call `get_doc_page` with the `url` of an official plugin, and use the Capawesome MCP server at https://mcp.capawesome.io/mcp for Capawesome plugins.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | The maximum number of items to return, e.g. 5. Defaults to 25, maximum 100. |
| query | string | – | A free-text filter matching the package name or the description, e.g. "camera". Defaults to no filter. Optional. |
| source | string | – | Which plugins to list: "official" for the plugins maintained by the Capacitor team, "community" for the awesome-capacitorjs entries, or "all" for both. Defaults to "all". |
No output schema declared.
No examples provided.
search_docs Search Capacitor documentation ~378
Search the official Capacitor documentation from capacitorjs.com by keyword. Use this first for any question about Capacitor itself — the CLI, the `capacitor.config` file, the native Android and iOS projects, the official plugin APIs, or upgrading to a newer major version — because guessing an API, a configuration option or a CLI flag produces broken code. Returns the best matching page sections with `title`, `url`, `snippet`, `section` and `version`, plus the `parentTitle` and `parentUrl` of the page a section belongs to. The same results are attached as structured content. Do not use this to read a whole page (call `get_doc_page` with a `url` from these results), to look up Capawesome plugins such as @capawesome/capacitor-file-picker or Capawesome Cloud services such as Live Updates, Native Builds and App Store Publishing (use the Capawesome MCP server at https://mcp.capawesome.io/mcp instead), or to look up Ionic Framework UI components (use the Ionic Framework MCP server at https://ionic-framework-mcp.capawesome.io/mcp instead).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | The maximum number of items to return, e.g. 5. Defaults to 10, maximum 25. |
| query | string | yes | The search terms, e.g. "camera permissions android" or "live reload". Plain keywords work best; no search operators are supported. |
| section | string | – | Restrict the search to one part of the documentation, e.g. "apis" for the official plugin references or "ios" for the native iOS guides. Defaults to searching every section. |
| version | string | – | Optional. Capacitor docs version. Defaults to v8. Match the major version of @capacitor/core in the user's package.json. |
| Name | Type | Req | Description |
|---|---|---|---|
| results | array | yes | – |
No examples provided.
What is the io.capawesome/capacitor-mcp server?
io.capawesome/capacitor-mcp is listed in the public MCP registry as io.capawesome/capacitor-mcp. Unofficial MCP server for the Capacitor documentation, plugin list and blog. This page covers its hosted endpoint (https://capacitor-mcp.capawesome.io/mcp).
Is the io.capawesome/capacitor-mcp server safe to use?
io.capawesome/capacitor-mcp scores 78 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/capacitor-mcp server expose?
io.capawesome/capacitor-mcp exposes 4 tools: search_docs, get_doc_page, list_plugins, list_blog_posts. Their descriptions and schemas cost roughly 1,042 tokens of context every time the server is loaded.
Does the io.capawesome/capacitor-mcp server require authentication?
No. We connected to io.capawesome/capacitor-mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.capawesome/capacitor-mcp server still maintained?
io.capawesome/capacitor-mcp is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.