Skip to main content
Glama

Server Details

Your agent already broke this three times. ChangeBook tells it before the fourth.

The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.

If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.

Status
Unhealthy
Uptime
0.0% over 60 days
OAuth
Works in Glama
Last Tested
Transport
Streamable HTTP
URL

Related MCP Connectors

Related MCP Servers

  • A
    license
    A
    quality
    C
    maintenance
    Every agent action is recorded in a SHA-256 hash chain. Prove to clients that your agent did what it said it did. Record, query, verify, and export agent activity.
    3
    27 npm
    2
    MIT
  • A
    license
    A
    quality
    A
    maintenance
    Enables AI agents to ask what changed in a time window and get back a short, ranked answer across metrics, logs and traces, with the service where a failure started identified and its echoes in other services labelled as such. Read-only and deterministic, it scores changes against a baseline and trims results to a token budget, so agents avoid paging through raw queries and blaming the loudest symptom.
    4
    Apache 2.0
  • A
    license
    Not graded
    quality
    C
    maintenance
    A human-in-the-loop governance interlock for AI agents. Agents propose changes, a human countersigns the exact plan, and then it executes stage by stage with precondition checks, verification, and auditing.
    Apache 2.0
Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources