io.github.aidi1723/omniglyph
Related Servers
Alternatives to io.github.aidi1723/omniglyph
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceA deterministic MCP server that guards AI/agent output by detecting secrets, injection, and PII in ~85µs with zero dependencies. Gives a clear ship/block verdict and runs locally or hosted.2Apache 2.0
- AlicenseAqualityAmaintenanceLocal-first MCP server that gives any AI coding agent per-project memory, workflow intelligence, and always-on, lossless token & context optimization.37184MIT
- AlicenseNot gradedqualityCmaintenanceMCP server enabling AI agents to enforce corrected rules as durable pre-output checks, manage processed memory, and query a temporal knowledge graph.Apache 2.0
- AlicenseNot gradedqualityBmaintenanceA local-first MCP server that lets AI agents use gated APIs without holding keys, enforcing declarative policies, injecting secrets server-side, and auditing access without content.2Apache 2.0
- AlicenseNot gradedqualityCmaintenanceAn MCP server that enforces runtime governance on AI agent actions — file access, command execution, delegation chains, and permission escalation.MIT
- AlicenseBqualityCmaintenanceA local-first MCP server that provides AI agents with safe codebase access through file discovery, hybrid lexical-semantic search, and project introspection. It features durable local memory and semantic indexing while keeping all data and processing entirely on your local machine.74146MIT
TDQS
Scored across 17 tools
Each tool targets a distinct function: explanation, normalization, listing, validation, scanning, enforcement, lookup, and audit. The only potential overlap is the deprecated scan_code_symbols, but its description clarifies it as an alias for scan_unicode_security. All other tools have clearly separated purposes.
All tool names follow a consistent verb_noun pattern with underscores, such as explain_term, scan_unicode_security, lookup_glyph, and enforce_intent. The pattern is uniform across the set, with no mixing of conventions or irregular cases.
With 17 tools, the count is slightly above the typical 3-15 range but still reasonable for the domain. Each tool serves a specific purpose, and none feel redundant. The scope of OmniGlyph justifies the number.
The tool set covers explanation, normalization, validation, scanning (security, input, output), enforcement, lookup, and auditing. While it lacks tools for creating or editing lexicon/policy packs, the focus on validation and scanning is well-covered. No critical gaps are apparent for the stated purpose.