Developer · Remote MCP server
Alchemist Cloud Tickets
Dispatch and track Alchemist Cloud tickets, watch deploys, read logs, and query your project DB.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
ai.chipp/alchemist-cloud-tickets- Version
- 1.0.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-09-02
- Updated
- 2026-09-02
- Publisher
- ai.chipp · 2 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via the domain chipp.ai · how
- Website
- chipp.ai/docs/guides/alchemist-mcp-server
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://build.chipp.ai/alchemist-api/api/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
How to connect Alchemist Cloud Tickets
Alchemist Cloud Tickets is a remote MCP server: there is nothing to install. Its endpoint is https://build.chipp.ai/alchemist-api/api/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from ai.chipp
| Server | Runs |
|---|---|
| ChippBuild and manage Chipp AI apps: prompts, knowledge, custom actions, and chat with your apps. | Remote · HTTPLive check: sign-in required |
More developer servers
| Server | Runs |
|---|---|
| AIWebSignalsPublic AI web-readiness scanner and machine-facing observability discovery service. | Remote · HTTPLive check: ✓ handshake |
| Akamai CDNRead-only MCP server for Akamai CDN - properties, EdgeWorkers, DNS, network lists. | Local · stdio |
| AkbGit-backed org memory for AI agents - hybrid search, tables, files & a URI graph over MCP. | Local · stdio |
| Akeyless Agentic Runtime AuthoritySecretless database and cloud access via Akeyless RTA. Credentials never enter the model. | Local · stdio |
| AlchemyServes the Alchemy writing ruleset to any agent, so its prose loses the usual LLM tells. | Local · stdio |
| Alertlogic MCPMCP server for Alert Logic MDR - incident response, log search, SOAR, and SOC workflows. | Local · stdio |
| Aletheia Runtime Safety & Scope Creep FilterDeterministic pre-execution filter that blocks known scope-creep and prompt-injection tool calls. | Local · stdio |
| Alex Llm Attack MCP ServerQuery and retrieve information about various adversarial tactics and techniques used in cyber atta… | Remote · HTTPLive check: ✗ no handshake |