Capxule
REMOTE · CAPXULE.AI
The context marketplace: expert guided journeys your assistant runs step by step.
Available components
Last scanned (1 hour ago)
Scores higher than 44% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Education and Research
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (restart_journey). See how to fix → View diagnostics → Fail
- 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 Usability69
- 67% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Partial
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1590 tokens (~144/item across 11 items; 9 tools + 2 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 Management0
- Stability check failed: schema churn in the 22 days we've observed: 10 tool removals, 0 breaking changes, 0 auth/transport breaks, 7 additions. See how to fix → Fail
Tool Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 91% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
- Supports UI / widget rendering.Pass
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.
- 5 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- 4 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- 3 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- 2 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- 1 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- 31 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- 30 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- 29 Oct 26 −5
- Stability: 0.47 → fail ▼ security
- A breaking change shipped without a version bump: still 1.0.0 ▼ security
- Tool “account_bind” was removed ▼ security
- Tool “account_status” was removed ▼ security
- Tool “account_verify” was removed ▼ security
- Tool “browse_catalog” was removed ▼ security
- Tool “find_capsule” was removed ▼ security
- Tool “handoff” was removed ▼ security
- Tool “journey_state” was removed ▼ security
- Tool “list_categories” was removed ▼ security
- Tool “make_artifact” was removed ▼ security
- Tool “turn” was removed ▼ security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “open_journey” rewrote its description, which is the text the model reads security
- Tool “restart_journey” rewrote its description, which is the text the model reads security
- Schema quality: 340 → 144 ▲ functional
- Tool coverage: 86% → 91% ▲ functional
- Schema quality: excellent → good functional
- Destructive annotations: 100 → pass functional
- New tool “browse_journeys” functional
- New tool “create_takeaway” functional
- New tool “find_journey” functional
- New tool “get_journey_progress” functional
- New tool “get_resume_link” functional
- New tool “list_journey_categories” functional
- New tool “take_journey_step” functional
- “open_journey” reworded the description of “capsule_id” cosmetic
- “open_journey” reworded the description of “goal” cosmetic
- “open_journey” reworded the description of “resume” cosmetic
- Tool “open_journey” changed its title: Open or resume a journey → Open a journey cosmetic
- Tool “restart_journey” changed its title: Start a journey over → Restart a journey cosmetic
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 5 Nov 2026 · Probed https://capxule.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=capxulehub.com | CN=Amazon RSA 2048 M04,O=Amazon,C=US | 9 Oct 2026 | 24 Apr 2027 | RSA 2048 | SHA256-RSA | ec9ffb183e4c331934e79659f20579e |
| SANs: capxulehub.com, api.kapsulehub.com, api.capxulehub.com, capxule.ai, www.kapsulehub.com, www.kapsulify.com, kapsulehub.com, www.capxule.ai, kapsulify.com, www.capxulehub.com | ||||||
| CN=Amazon RSA 2048 M04,O=Amazon,C=US (CA) | CN=Amazon Root CA 1,O=Amazon,C=US | 23 Aug 2022 | 23 Aug 2030 | RSA 2048 | SHA256-RSA | 773124f2a952e3ed18a58bdb85d1bc0ce5f27 |
| CN=Amazon Root CA 1,O=Amazon,C=US (CA) | CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US | 25 May 2015 | 31 Dec 2037 | RSA 2048 | SHA256-RSA | 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of capxule.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 1814, 3799 | 8, 8 | Verified |
| capxule.ai. | 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://capxule.ai/mcp | Verified | 200 | |
| http (plaintext) | http://capxule.ai/mcp | HTTPS enforced | 301 | https://capxule.ai:443/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 →
browse_journeys Browse journeys ~116
Use when the user wants to look through the journeys, optionally within one category (a slug from list_journey_categories). Returns a page of the same cards as find_journey, with the total and next_offset.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | A category slug from list_journey_categories (e.g. education). Omit for every category. |
| limit | integer | – | Cards per page, 1 to 25 (default 10). |
| offset | integer | – | Start position; pass next_offset from the previous page. |
No output schema declared.
No examples provided.
create_takeaway Create a takeaway ~98
Use when the user asks for a summary to keep. Composes a markdown takeaway from this journey session: what the user asked, the key points and the stops visited. Available on connected accounts; otherwise returns not_available.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | yes | – |
| session | string | yes | The session handle from open_journey (starts with cxs_). |
| template_id | string | – | Required for kind template: an id from capabilities.templates. |
No output schema declared.
No examples provided.
find_journey Find a guided journey ~169
Use when the user wants a guided, step-by-step journey on a topic, a skill or an exam. Searches the published journeys and returns up to three cards (id, title, summary, shape, languages, number of stops, estimated minutes, who it is for and not for, a premium flag, page_url). `in_progress: true` marks a journey this user already has open. When nothing matches, `alternatives` holds the three nearest journeys.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max results, 1 to 3 (default 3). |
| locale | string | – | The user's locale (en, fr, es, ar). |
| query | string | yes | The topic, skill or exam to search for, in a few words. The topic only, no personal details. |
No output schema declared.
No examples provided.
get_journey_progress Get journey progress ~75
Use when the user asks where they are in a journey, how far they have come or how much is left. Returns the current stop, visited and remaining stops, percent done, practice stats, limits and a resume line.
| Name | Type | Req | Description |
|---|---|---|---|
| session | string | yes | The session handle from open_journey (starts with cxs_). |
No output schema declared.
No examples provided.
get_resume_link Get a resume link ~61
Use when the user wants to continue the journey later, on the website or in another assistant. Returns a resume link and a short resume code for this session.
| Name | Type | Req | Description |
|---|---|---|---|
| session | string | yes | The session handle from open_journey (starts with cxs_). |
No output schema declared.
No examples provided.
list_journey_categories List journey categories ~43
Use when the user asks what kinds of journeys are available. Returns each category slug, a readable label, the number of journeys in it and a few example titles.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
open_journey Open a journey ~179
Use when the user chooses a journey to start or continue. Opens it, or resumes the user's session for it, and returns the session contract: `session`, the stop titles, the capabilities, the limits in turns and the first step. Calling it again for the same journey resumes the same session; it never resets progress.
| Name | Type | Req | Description |
|---|---|---|---|
| capsule_id | string | – | The journey id from find_journey (uuid or short id). `welcome` opens the sandbox tour. |
| goal | string | – | What the user wants from the journey, in a few words, if they said. No personal details. |
| locale | string | – | Preferred locale; the beat echoes the locale actually served. |
| resume | string | – | A resume code from get_resume_link. |
| slug | string | – | The journey slug, when you hold that instead of the id. |
No output schema declared.
No examples provided.
restart_journey Restart a journey ~98
Use only when the user explicitly asks to start a journey over, after confirming with them. Returns to the first step and clears the visited stops; turns already used stay used. Returns the same session contract as open_journey.
| Name | Type | Req | Description |
|---|---|---|---|
| capsule_id | string | – | The journey id (uuid or short id). |
| locale | string | – | Preferred locale. |
| slug | string | – | The journey slug, when you hold that instead of the id. |
No output schema declared.
No examples provided.
take_journey_step Take a journey step ~190
Use for every step after open_journey. Sends the user's choice and returns the next step: `answer`, `statement`, numbered `options` with ids, `media`, `progress` and `limits`. Send `pick` with an option id when the user chose an option or its number; otherwise send `say` with what the user said. `go` jumps to a stop from the contract; `drill` and `simulate` start practice on exam journeys; `exit` leaves practice. Supply a fresh `turn_id` per step; a repeat returns the stored step. If the step carries `wall`, tell the user `wall.for_human`.
| Name | Type | Req | Description |
|---|---|---|---|
| action | – | yes | – |
| session | string | yes | The session handle from open_journey (starts with cxs_). |
| turn_id | string | – | Your idempotency id for this step (fresh per step). |
No output schema declared.
No examples provided.
How do I install the Capxule MCP server?
Capxule is a hosted endpoint at https://capxule.ai/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 · capxule.ai
claude mcp add --transport http ai-capxule-capxule 'https://capxule.ai/mcp'
What is the Capxule MCP server?
Capxule is an MCP server listed in the public MCP registry as ai.capxule/capxule. The context marketplace: expert guided journeys your assistant runs step by step. This page covers its hosted endpoint (https://capxule.ai/mcp).
Is the Capxule MCP server safe to use?
Capxule scores 63 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 Capxule MCP server expose?
Capxule exposes 9 tools: find_journey, list_journey_categories, browse_journeys, open_journey, take_journey_step, and 4 more. Their descriptions and schemas cost roughly 1,029 tokens of context every time the server is loaded.
Does the Capxule MCP server require authentication?
No. We connected to Capxule without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Capxule MCP server still maintained?
Capxule 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.