Chipp Observability

ai.chippPublished by chipp.aiOfficial publisherv1.0.0Updated Oct 29, 2026

Chipp: a deployed project's database (read), logs, errors, analytics, CI status, custom actions.

The publisher's own server: Alchemist Cloud Tickets

VerifiedStreamable HTTPWeb executableDatabasesSecurity & MonitoringData & Analytics

Overview

AI-generated overview

Chipp Observability is a remote MCP endpoint that lets an assistant inspect a deployed Chipp project's database, logs, errors, analytics and CI status.

What you can do
  • Read a deployed project's database
  • Inspect logs and errors
  • Review analytics
  • Check CI status
  • Run or trigger custom actions
When to use it
Useful when you are debugging or monitoring a project deployed on Chipp and want an assistant to look at its logs, errors, analytics, CI status or read-only database without switching dashboards.
Requirements
A remote streamable HTTP endpoint at mcp.chipp.ai; no packages, environment variables or headers are declared. It applies to a deployed Chipp project, so a Chipp account and project are implied. No authentication is declared in the manifest.
Before you install
The server can reach a deployed project's database, logs, errors and CI, and the description mentions custom actions, which may change state; confirm what those actions do before use. No authentication is declared, so verify how access to your project is controlled before connecting.

Installation

In SourceWeft

  1. Open Chipp Observability in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/ai.chipp%2Fchipp-observability/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "chipp-observability": {
      "type": "http",
      "url": "https://mcp.chipp.ai/mcp/observability"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestOct 29, 2026

Score

28% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Chipp integrations