attester-mcp
Related Servers
Alternatives to attester-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceMCP server for Python API verification and projection, enabling AI coding agents to detect non-existent APIs and retrieve exact API surfaces before writing code.3MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that provides tools to fetch live, version-accurate documentation, changelogs, examples, and method signatures for npm and PyPI packages, preventing AI coding agents from hallucinating stale APIs.4 npmISC

phylax-mcpofficial
AlicenseAqualityBmaintenanceMCP server that integrates the Phylax verification API, enabling AI assistants to verify packages, repositories, and other MCP servers before use. It exposes tools for verifying artifacts, checking policies, and fetching attestations.74 npmMIT
@lpm-registry/mcp-serverofficial
AlicenseAqualityCmaintenanceMCP server for the LPM package registry, enabling AI tools to search, browse source code, install packages, check quality, and more.173 npmISC- FlicenseAqualityDmaintenancePackage intelligence MCP server. Stops AI agents from installing hallucinated/malicious packages across 17 ecosystems. 22 tools, free, no auth.221-
- AlicenseNot gradedqualityAmaintenanceMCP server that provides 25 tools for AI agents to query and modify a dependency graph, enabling impact analysis and provenance tracking for AI-assisted development.8MIT
TDQS
Scored across 9 tools
Each tool targets a distinct task: code research, work verification, SLA monitoring, counterparty checks, rubric grading, and package/symbol checks. The oracle_* tools are clearly separated from the attester_* demo tools, and even within each family purposes are unambiguous.
Naming is inconsistent across the set: oracle_* uses a mix of verbs (research, verify_work, judge) and nouns (watchtower_report, spend_check), while attester_* follows a different entity-first pattern (package_exists, symbol_signature, version_diff). No uniform verb_noun convention is maintained.
9 tools is a reasonable count for an attestation server, though it splits into two distinct families (oracle_ paid services and attester_ free demos) which makes the set feel slightly broader than one focused domain. Each tool earns its place, so the count is justified.
The core lifecycle is well covered: research, verification, grading, spend checks, and dependency diffing. Minor gaps exist, such as no direct tool to list watchtower targets or inspect raw package metadata, but these are edge cases that don't break workflows.