Is the Cambercloud Camber Mcp Camber MCP server down?

mcp-registry/com.cambercloud.camber-mcp/camber-mcp-server · v3.2.3

up · requires sign-in
Last checked 2026-10-27 02:28 UTC · handshake 249ms

As of 2026-10-27 02:28 UTC, the Cambercloud Camber Mcp Camber MCP server is up (it requires sign-in) with a Glimind reliability score of 87/100 (grade B). Over the last 30 days it answered 100% of Glimind's liveness checks.

uptime (30d checks)
100%
checks observed
217
outages (90d)
0
tools
6

Remote data science agents for Snowflake, Databricks & BigQuery in Claude/Cursor via MCP

Point your MCP client at this streamable-http endpoint: https://camber-mcp.cambercloud.com/mcp

Agent-readiness: B (86/100)

B (86/100): 0 error(s), 2 warning(s) across 6 tool(s); ~1,365 tokens of tool definitions.
Scores higher than 51% of 15,771 MCP servers Glimind has audited.
Its tool list costs an agent ~1,365 tokens per session — lighter than 65% of servers.
85 → 86 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions100
Safety hints7
Token cost100
Client compatibility100
Protocol100
Reliability100
Stability100

What to fix (3)

6 of 6 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: agents_chat_start, agents_chat_status, agents_create, agents_list, usage_guide and 1 more

1 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.

Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →

Tools: agents_create

Requires authentication (Bearer); tool definitions could not be read anonymously.

If discovery should be public, allow initialize + tools/list without credentials and gate only tools/call. Directories and routers can then list your tools.

Auto-fix: 5 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.cambercloud.camber-mcp%2Fcamber-mcp-server/fixes

agents_chat_start 1 change
{
  "name": "agents_chat_start",
  "description": "Start a Camber agent chat. This is the tool to use for chatting with an agent.\n\n        Agent runs can take minutes — longer than MCP tool timeouts allow (Claude Desktop\n        cannot extend them). So this tool does NOT wait for the reply: it submits the\n        message and returns immediately with a `conversation_id` and a clickable `chat_url`.\n        The agent keeps working on the server after this returns.\n\n        **You MUST follow up, the reply is NOT in this tool's result:**\n        1. A",
  "inputSchema": {
    "type": "object",
    "properties": {
      "stop": {
        "type": "boolean",
        "default": false,
        "description": "Set true to stop the conversation's currently running response and start this message instead. Only meaningful with conversation_id. Use it when a previous call reported the conversation is still generating a response and the user wants to interrupt it and send a new message."
      },
      "message": {
        "type": "string",
        "default": "",
        "description": "The message to send to the agent."
      },
      "agent_tag": {
        "type": "string",
        "default": null,
        "description": "Tag of the agent you want to chat with. Start with @ to use the agent's tag.agent_tag = `@owner_name.agent_alias`For example, @camber_user.ai-agent-1"
      },
      "conversation_id": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "default": null,
        "description": "Optional UUID of an existing conversation to continue. Pass the conversation_id from a previous agents_chat_start call to keep context across turns."
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}
agents_chat_status 1 change
{
  "name": "agents_chat_status",
  "description": "Check an async agent chat started with agents_chat_start, and return its reply when done.\n\n        This checks the CLI twice over 30 seconds and returns its latest status response.\n        Status values:\n        - `running`: still working — call this tool again with the same conversation_id.\n        - `idle`: finished — `content` holds the agent's reply.\n        - `failed`: the run errored.\n\n        Returns: AgentChatStatus with `status`, `content` (the reply once done), and\n        `output_stas",
  "inputSchema": {
    "type": "object",
    "properties": {
      "conversation_id": {
        "type": "string",
        "default": "",
        "description": "The conversation_id returned by agents_chat_start, identifying the run to check."
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  }
}
agents_create 1 change
{
  "name": "agents_create",
  "description": "Create a Camber agent.\n\n        Creates a personal agent by default. Pass `team_name` to create the agent\n        for a team you belong to. Returns the created agent, including its `tag`.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "name": {
        "type": "string",
        "default": "",
        "description": "Name of the agent to create."
      },
      "alias": {
        "type": "string",
        "default": "",
        "description": "Alias used in the agent tag, for example `my-agent` in `@owner.my-agent`."
      },
      "team_name": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "default": null,
        "description": "Optional team unique name. When omitted, creates a personal agent."
      },
      "description": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "default": null,
        "description": "Optional short description of the agent."
      },
      "instructions": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "default": null,
        "description": "Optional instructions that define the agent behavior."
      },
      "structured_output": {
        "type": "boolean",
        "default": false,
        "description": "Whether the agent should return structured output."
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.cambercloud.camber-mcp/camber-mcp-server"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/com.cambercloud.camber-mcp/camber-mcp-server"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.cambercloud.camber-mcp%2Fcamber-mcp-server.svg)](https://glimind.com/server/mcp-registry%2Fcom.cambercloud.camber-mcp%2Fcamber-mcp-server?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fcom.cambercloud.camber-mcp%2Fcamber-mcp-server?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.cambercloud.camber-mcp%2Fcamber-mcp-server.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.cambercloud.camber-mcp%2Fcamber-mcp-server.svg
   :target: https://glimind.com/server/mcp-registry%2Fcom.cambercloud.camber-mcp%2Fcamber-mcp-server?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:ac8d32b0c5d2de8a…, first seen 2026-10-17, included at leaf 10079 of 76,847. Version history · verify what your client received.

Tools (6)

Compare: most reliable communication servers · most reliable other servers · most reliable data servers · most reliable knowledge servers · most reliable security servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Cambercloud Camber Mcp Camber MCP server down right now?

As of 2026-10-27 02:28 UTC, the Cambercloud Camber Mcp Camber MCP server is up (it requires sign-in) with a Glimind reliability score of 87/100 (grade B). Over the last 30 days it answered 100% of Glimind's liveness checks.

How many tools does Cambercloud Camber Mcp Camber MCP server provide?

Cambercloud Camber Mcp Camber MCP server advertises 6 tools, including agents_chat_start, agents_chat_status, agents_create, agents_list, usage_guide.

How do I install Cambercloud Camber Mcp Camber MCP server?

Point your MCP client at this streamable-http endpoint: https://camber-mcp.cambercloud.com/mcp

Is the Cambercloud Camber Mcp Camber MCP server safe to connect to an AI agent?

Glimind scanned all 6 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Cambercloud Camber Mcp Camber MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve