DataHealth-Observer

io.github.EvozimPublished by GitHub account Evozimv1.0.0Updated Oct 25, 2026

Database health auditor monitoring query latencies.

VerifiedSSEWeb executableDatabases

Overview

AI-generated overview

A remote MCP server that audits database health by monitoring query latencies, with premium settlement requiring a signed payment header.

What you can do
Audits database health and reports on query latency monitoring, based on the registry description. No tool list is published, so the exact operations an assistant can call are not documented. Premium settlement is gated behind a payment signature header.
When to use it
Worth considering when you want an assistant to check on database health and query latency without running local tooling. Because no tools are listed and no instructions or README are provided, evaluate it only if you can test the endpoint directly first.
Requirements
A remote SSE endpoint; nothing needs to be installed locally. Premium settlement requires a payment-signature header carrying a Base64-encoded EIP-3009 TransferWithAuthorization signature. No accounts or environment variables are declared.
Before you install
The server asks for a payment-signature header, meaning premium use involves a signed on-chain style payment authorization; understand what you are authorizing before sending it. The tool surface is undocumented, so what it reads or changes in your databases is unknown. Treat the endpoint as third-party and avoid exposing sensitive connection details.

Installation

In SourceWeft

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

Web executable via SSE. 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/io.github.Evozim%2Fdatahealth-observer/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": {
    "datahealth-observer": {
      "type": "sse",
      "url": "https://datahealth-observer-mcp.vercel.app/api/mcp"
    }
  }
}

Tools

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

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

67% 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
  • Auth declaredRequired10 pts
  • Tools listedRequired15 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.