Ingero

io.github.ingero-ioPublished by GitHub account ingero-iov0.8.2Updated Oct 25, 2026

eBPF-based GPU causal observability with 7 MCP tools for AI-assisted GPU debugging

VerifiedSTDIODesktop onlyDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

Ingero is a local eBPF-based GPU causal observability server exposing seven MCP tools so an assistant can help debug GPU workloads.

What you can do
The manifest lists no individual tools, so capabilities come from the description: it provides seven MCP tools for AI-assisted GPU debugging, built on eBPF-based GPU causal observability. An assistant can use these tools to investigate GPU behavior and trace causes of GPU problems during a debugging session.
When to use it
Worth adding when you are debugging GPU workloads and want an assistant to help investigate GPU behavior and root causes through observability data rather than guesswork.
Requirements
Runs as a local process over stdio, distributed as an OCI container image (ghcr.io/ingero-io/ingero:v0.8.2). Desktop only; no web execution. No authentication, environment variables or headers are declared. eBPF-based tracing typically needs a Linux host with suitable kernel privileges, though the input does not state this explicitly.
Before you install
eBPF-based observability usually requires elevated privileges on the host, so review what the container is granted before running it. The input declares no credentials or secrets, but it also gives no detail on what data the tools collect or where it goes.

Installation

In SourceWeft

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

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.8.2LatestSep 16, 2026

Score

25% 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 days25 pts

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

  • Auth declared10 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.

  • License10 pts

    Declare a license in the repository or the registry entry.