Small Print
Related Servers
Alternatives to Small Print
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceA read-only MCP server that lets an agent check whether a public MCP server's tool definitions have changed, and whether any locally pinned server has a change waiting for review. It also returns the exact setup steps for protecting servers in Claude Code, Cursor, Codex, VS Code and others, without ever exposing third-party tool text.85 npmMIT
- AlicenseNot gradedqualityBmaintenanceRead-only remote tools let agents search a curated directory of skills, harnesses, MCP servers, tools, protocols and APIs, then fetch full entries plus long-form guides, comparisons, stacks and downloadable Agent Skills. Needs no install, API key or authentication over Streamable HTTP.MIT
- AlicenseAqualityDmaintenanceRead-only MCP tools for coding agents to audit deployment targets, detect fabricated code, review backlog, database schema, analytics, ML models, architecture docs, and decision lenses.115 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to check acceptance evidence against a specification and JUnit results, and to review structured AI proposals for current contract hash, coverage, and in-scope paths. Both tools are read-only, idempotent, content-based, and require no model credentials or filesystem access.MIT
- AlicenseAqualityAmaintenanceLocal-first security scanner for AI agent skills, plugins, hooks and MCP servers. Read-only, offline tools to scan a skill or MCP server before installing it, audit the installed setup and review proxy pins.5507 npmMIT
- AlicenseAqualityCmaintenancePublishes four flat, schema-light tools that let AI agents (including strict providers) search, describe, and invoke any of 139 reverse-engineering capabilities behind a persistent REA server. Enables file fingerprinting, inspection, and evidence-linked investigation of shipped software through plain-English requests, read-only by default.462 npm1MIT
TDQS
Scored across 4 tools
Each tool targets a distinct aspect of the change-tracking domain: lookup_entry for record overview, changed_since_approval for binary approval status, changes_since for detailed diffs, and advisories_for for advisory details. The descriptions explicitly cross-reference each other and clarify when to use one over another, leaving no meaningful ambiguity.
All names use snake_case, but the grammatical patterns are mixed: changes_since (noun_preposition), lookup_entry (verb_noun), changed_since_approval (adjective_preposition_noun), and advisories_for (noun_preposition). The lack of a uniform verb_noun convention makes the set readable but inconsistently named.
Four tools is well-scoped for a read-only change and advisory tracking service. Each tool covers a distinct lifecycle operation—lookup, approval check, diff inspection, and advisory query—with no redundant tools.
The set covers the core monitoring workflow: entry lookup, change since approval, detailed diffs, and advisories. A minor gap is the lack of a discovery/search tool to find entries by name or list recent changes across the catalog, though agents can typically work around this with known entry names.