_ registry / mcp http-sse · checked 10m ago

capawesome

https://mcp.capawesome.io

Registry code: f7add27a1293e04a

api record

The official MCP server for Capawesome. It serves the Capawesome documentation and blog from capawesome.io — the Capawesome plugins for Capacitor and Cordova, Capawesome Cloud (Live Updates, Native Builds, App Store Publishing), Capawesome Insiders and the Capawesome CLI — through `search_docs`, `get_doc_page` and `list_blog_posts`, and it manages Capawesome Cloud itself through the `cloud_*` tools. The `cloud_*` tools are registered only when the request carries a Capawesome Cloud token in the `Authorization: Bearer <token>` header (create one at…

endpoint
https://mcp.capawesome.io/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is capawesome live?
Yes — it answered the hub's last check (checked 10m ago). It answered 99% of checks over the last 30 days.
Is capawesome free to use?
Yes — the hub reached it with no key and no payment.
What tools does capawesome have?
3 tools: get_doc_page, search_docs, list_blog_posts.
Is capawesome safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.4%

90 days 99.7%· all time 99.7%

latency
566ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 308 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • unknown → live
_ what it is for
used for
  • search mobile app plugin documentation
  • read a documentation page
  • list recent blog posts
takes → gives
text → text
tools
3 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 3 tools
3 never probed 0 of 3 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_doc_page reads unknown 10h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "url"
      ],
      "properties": {
        "url": {
          "type": "string",
          "minLength": 1,
          "description": "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."
        }
      }
    }
    arguments 14 lines
  • search_docs reads unknown 10h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "query"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "maximum": 25,
          "minimum": 1,
          "description": "The maximum number of results to return, e.g. 5. Defaults to 10, maximum 25."
        },
        "query": {
          "type": "string",
          "minLength": 1,
          "description": "The search terms, e.g. \"live update rollback\" or \"biometrics android setup\". Plain keywords work best; no search operators are supported."
        },
        "section": {
          "enum": [
            "sdks",
            "cloud",
            "blog",
            "insiders"
          ],
          "type": "string",
          "description": "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). Defaults to searching everything."
        }
      }
    }
    arguments 30 lines
  • list_blog_posts reads unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {}
    }
    arguments 5 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id f7add27a1293e04a.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/f7add27a1293e04a/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/f7add27a1293e04a/badge.svg)](https://brick.blue/agent/f7add27a1293e04a?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
70%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.

_ also on capawesome.io 2 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.