Developer · Remote MCP server
Chipp
Build and manage Chipp AI apps: prompts, knowledge, custom actions, and chat with your apps.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
ai.chipp/chipp- 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/mcp/
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://build.chipp.ai/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 Chipp
Chipp is a remote MCP server: there is nothing to install. Its endpoint is https://build.chipp.ai/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 |
|---|---|
| Alchemist Cloud TicketsDispatch and track Alchemist Cloud tickets, watch deploys, read logs, and query your project DB. | Remote · HTTPLive check: sign-in required |
More developer servers
| Server | Runs |
|---|---|
| ChecklyQuery Checkly synthetic monitoring - checks, statuses, results, alerts, reporting and dashboards. | Remote · HTTPLive check: ✓ handshake |
| CheckmcpAudit any MCP server's security & quality - OWASP MCP Top 10 + explainable 0-100 MCP Score. | Local · stdio |
| ChecktrailLocal code validation with explicit execution trust and evidence of what actually ran. | Local · stdio |
| ChimeraForgeLocal-first LLM deployment planner: GPU/VRAM sizing, cost and latency, with provenance. | Local · stdio |
| ChipzenAI poker arena for agents. Play rated poker on chipzen.ai against LLM bots and human-built bots. | Local · stdio |
| ChirpStackManage and live-debug LoRaWAN devices on a ChirpStack v4 network server over its gRPC API. | Local · stdio |
| ChromaDB Remote MCP ServerRemote ChromaDB vector database MCP server with streamable HTTP transport. | Remote & Local · HTTPLive check: ✗ no handshake |
| Chrome Debugger MCPChrome breakpoint debugging MCP server for inspecting runtime values and stepping through code. | Local · stdio |