Mcp Observability

io.github.infoinlet-marketplacePublished by GitHub account infoinlet-marketplacev0.1.1Updated Oct 30, 2026

Observability for incident agents — query Loki (LogQL), Prometheus (PromQL), Elasticsearch.

VerifiedSTDIODesktop onlySecurity & Monitoring

Server details

Identifier: io.github.infoinlet-marketplace/mcp-observability
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account infoinlet-marketplace for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.infoinlet-marketplace%2Fmcp-observability.svg)](https://sourceweft.com/mcp/io.github.infoinlet-marketplace%2Fmcp-observability?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Local MCP server that lets an assistant query Loki with LogQL, Prometheus with PromQL, and Elasticsearch for incident investigation.

What you can do: Query Loki logs using LogQL
Query Prometheus metrics using PromQL
Query Elasticsearch for related log and event data
Support incident investigation by pulling observability data into the assistant's context
When to use it: Useful when an assistant needs to look at logs, metrics or search-indexed events while diagnosing an incident or answering questions about system behavior, and you already run Loki, Prometheus or Elasticsearch.
Requirements: Runs as a local process over stdio, installed from the npm package @infoinlet/mcp-observability, so Node.js and npm are needed. Desktop client only. No authentication, environment variables or headers are declared, so connection details for the Loki, Prometheus and Elasticsearch endpoints are not specified in the listing.

Before you install

The server queries live observability backends, so results may expose sensitive log and metric data to the assistant and its model provider. No credentials are declared, which may mean unauthenticated access to those backends or that configuration is undocumented; check before pointing it at production systems.

Installation

In SourceWeft

Open Mcp Observability in the dashboard and add it to a workspace.
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

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

Version history

v0.1.1LatestSep 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.