MCP HeartbeatTHE MCP OBSERVATORY
Public workspace

Explore

Evidence for your next connection.

Independent measurements of remote MCP servers. Every observation has a timestamp.

Read-only probes

MCP server · Other

Capxule

The context marketplace: expert guided journeys your assistant runs step by step.

Checks passed
14 / 22

2 failed · 6 not measured

Median response
404 ms

Median of successful probes over 7 days

30-day uptime
Not measured

Share of countable probes over 30 days, including daily rollups. Auth challenges are excluded.

Discovered tools
9

Tool definitions returned by this server

Independent monitoring

Health & checks

Status history

Responded

The server completed its last measured handshake. This is an observation, not a guarantee.

Last checked
Check summary by test group
Test areaPassedFailedUnmeasured
ConnectionCan a client connect and discover tools?
500
Reliability & speedDoes it respond consistently and quickly?
103
Access & authenticationWhat is required to use this server?
102
Tool qualityAre the tool definitions usable by an agent?
400
Publisher identityCan the publisher be traced to its source?
321

Unmeasured means there is not enough evidence to decide. How these checks work

Inspect individual checks 22 recorded

Core

  • Pass
    Reachable

    Latest probe returned HTTP 200 in 362 ms.

  • Pass
    Valid handshake

    protocolVersion 2025-11-25, serverInfo.name capxule-agent.

  • Pass
    Lists tools

    tools/list returned 9 tools.

  • Pass
    Current protocol

    Negotiated 2025-11-25. The bar is 2025-06-18 or newer.

  • Pass
    HTTPS

    The endpoint URL is https.

Performance

  • Not measured
    Fast (p50)

    Median latency 404 ms over 2 samples in 7 days. The bar is 1000 ms. Need at least 5 samples.

  • Not measured
    Consistent (p95)

    95th percentile 441 ms over 2 samples in 7 days. The bar is 3000 ms. Need at least 20 samples.

  • Not measured
    Reliable (uptime)

    2 of 2 attempts returned a tool list in 30 days (100%). The bar is 99%. Need at least 30 samples.

  • Pass
    Stable tool list

    No tool was removed and no required parameter was added in the last 30 days.

Access

  • Pass
    Open access

    tools/list succeeded with no credential, and the record declares none.

  • Not measured
    Standard auth

    Auth is not required, so the OAuth metadata check does not apply.

  • Not measured
    Free tier cited

    No publisher quote has been checked.

Tools

  • Pass
    Tools described

    Every tool description is at least 20 characters.

  • Pass
    Valid input schemas

    Every inputSchema is a JSON Schema object.

  • Pass
    Parameters documented

    20 of 22 parameters have a description (91%). The bar is 80%.

  • Pass
    Safety hints

    Every tool sets readOnlyHint or destructiveHint.

Publisher

  • Pass
    Verified namespace

    Listed in the Official MCP Registry.

  • Fail
    Website matches publisher

    The website host does not match the reverse-domain namespace.

  • Pass
    Source repo linked

    A repository URL is on file.

  • Not measured
    Repo owner matches

    This namespace is not an io.github login, so the owner comparison does not apply.

  • Pass
    Recently updated

    Updated 2026-10-14T04:54:47.832517Z, within 180 days.

  • Fail
    Open-source licence

    GitHub does not report an OSI licence.

Start using Capxule

Connect to this server

Choose your client, copy the configuration, then enable the server in your client’s MCP settings.

Run this command in your terminal, then restart Claude Code.

Claude Code

claude mcp add --transport http capxule https://capxule.ai/mcp

Capabilities

Tools 9

browse_journeys

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.

Discovered
create_takeaway

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.

Discovered
find_journey

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.

Discovered
get_journey_progress

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.

Discovered
get_resume_link

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.

Discovered
list_journey_categories

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.

Discovered
open_journey

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.

Discovered
restart_journey

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.

Discovered
take_journey_step

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`.

Discovered

Recent measurements

Probe history

View status
Latest stored probes. Raw probe rows are kept for 14 days.
CheckedResultResponseTools
Connected362 ms9
Connected445 ms9