skills.rest
nicholasglazer
nicholasglazerCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

status

Diagnose gnosis-mcp health via connectivity, schema, and corpus checks.

27|9|Updated Feb 15, 2026
Search Tags:#schema#diagnostics#connectivity#diagnose#health#gnosis-mcp
One-click install
npx skills add https://github.com/nicholasglazer/gnosis-mcp --skill status-nicholasglazer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: status
Source: https://github.com/nicholasglazer/gnosis-mcp/tree/main/skills/status
Command: npx skills add https://github.com/nicholasglazer/gnosis-mcp --skill status-nicholasglazer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verify gnosis-mcp server connectivity, schema integrity, and corpus health. Use when MCP calls fail, return empty, or return unexpected data.

Core Features & Use Cases

  • Connectivity checks to ensure the MCP server is reachable.
  • Schema validation across the database schema and content graph (docs, chunks, embeddings).
  • Diagnostic reporting that surfaces common failure modes and provides actionable guidance.
  • Use Case: When a MCP call fails or returns unexpected data, run this skill to generate a concise health report and recommended next steps.

Quick Start

Run /gnosis:status to perform a full connectivity, schema, and corpus health check.

Frequently Asked Questions about status

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I diagnose MCP server connectivity and corpus health issues?▼

To diagnose MCP server issues, run a full diagnostic workflow that verifies server connectivity, database schema integrity, graph stats, embeddings, and reranker status to output a structured health report.

Why does my MCP call return empty responses or unexpected data patterns?▼

MCP calls return empty responses or unexpected data due to possible schema integrity failures or corpus health issues, which require a full diagnostic check of embeddings, graph stats, and server transport to resolve.

What is the best way to verify gnosis-mcp schema integrity after a failure?▼

The best way to verify gnosis-mcp schema integrity is executing a diagnostic workflow that validates the database schema, content graph, docs, chunks, and embeddings to surface common failure modes.

Can I check MCP server transport and reranker status during connectivity diagnostics?▼

Yes, you can check MCP server transport and reranker status during diagnostics, as the full health workflow enforces steps for connectivity, corpus stats, embeddings, reranker, and transport to generate actionable guidance.

What should I do when MCP calls fail and I need a structured status report?▼

When MCP calls fail, you should run a full diagnostic workflow to generate a concise structured status report, which surfaces common failure modes and provides actionable next steps for troubleshooting.

Related Skills

Explore More Software Engineering Skills→
automateyournetworkautomateyournetwork
627

prometheus-monitoring

Execute PromQL queries and inspect scrape target health in Prometheus.

Community
Intermediate
ZhanlinCuiZhanlinCui
178

mcp-builder

Design MCP servers with TypeScript or Python tool registration and transports.

Community
Advanced
nicholasglazernicholasglazer
27

eval

Evaluate corpus retrieval quality with Hit@5, MRR, and nDCG metrics.

Community
Intermediate
ruskibeatsruskibeats

graph-backfill-script

Reconstruct historical graph edges from health metrics data.

Community
Intermediate