@asitis/mcp
Related Servers
Alternatives to @asitis/mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceRead-only MCP server that audits AI agent skills in a workspace: lockfile drift, duplicate copies, broken symlinks, harness coverage and static security scans. Writes are refused unless explicitly enabled181,895 npmMIT
- AlicenseNot gradedqualityBmaintenanceA read-only MCP server that lets an agent audit its own environment by discovering local MCP configurations and skill folders on Windows, macOS, and Linux and running offline static checks for prompt injection, hidden instructions, hardcoded secrets, dangerous commands, unpinned packages, and excessive filesystem or transport permissions. It exposes tools to scan everything discovered, list configurations, vet a single skill, or analyze supplied text, returning text, JSON, SARIF, or HTML findings with CI-friendly severity levels.14 npmMIT
- AlicenseCqualityCmaintenanceRead-only MCP server for querying a running Obsidian vault from agentic runtimes, exposing safe Obsidian CLI commands.551MIT
- AlicenseNot gradedqualityBmaintenanceRead-only MCP server that lets coding agents ask about your developer machine: search its repositories, runtimes, packages, tools and MCP servers, see what breaks if one is removed, find what's listening on a port, and track live agent sessions and per-agent token cost. Runs locally and never writes, installs or deletes anything.1Apache 2.0
- FlicenseNot gradedqualityDmaintenanceLocal MCP server that extracts text and structure from PDF, DOCX, PPTX, SVG, and PNG files, along with directory and metadata listing, for read-only document analysis by LLM hosts.-
- AlicenseNot gradedqualityBmaintenanceA read-only MCP server that lets agents scan a project's AI agent setup — Claude Code, Codex, Cursor, MCP servers and instruction files — and surface security findings such as the lethal trifecta, broad permissions, exposed secrets and unpinned packages.57 npmMIT
TDQS
Scored across 7 tools
Each tool has a largely distinct role: discovery (find_steering_files), reading (read_markdown), structure (outline), validation (lint_steering), remediation (suggest_fixes), and load analysis (context_budget/load_plan). The main risk is between context_budget and load_plan, which both report token totals and session-loading behavior; the descriptions differentiate them (per-file estimate vs ordered per-agent simulation), but an agent could still hesitate between the two.
All names are lowercase snake_case, which is consistent at the casing level. However, verb style is mixed: find_steering_files, read_markdown, lint_steering, and suggest_fixes are verb_noun, while context_budget, load_plan, and outline are bare nouns. Readable and predictable overall, with minor deviation from a strict verb_noun pattern.
Seven tools is well within a healthy range and each maps to a distinct step in the workflow: discover, read, outline, lint, fix, budget, and plan loads. No tool appears redundant or vestigial, and the surface is not so thin that agents would be forced into dead ends.
The surface covers the full lifecycle for steering-file hygiene: discovery, exact reading, structural outlining, linting, diff-based fix suggestions, and load/token analysis across five agent platforms. Minor gaps exist, such as no cross-file search/grep over steering content and no post-edit re-verification helper, but the intentional no-write design (apply via Edit) is a reasonable workaround rather than a blocker.