attest-mcp-server
Related Servers
Alternatives to attest-mcp-server
- AlicenseNot gradedqualityCmaintenanceThe Stripe Model Context Protocol server allows you to integrate with Stripe APIs through function calling. This protocol supports various tools to interact with different Stripe services.13,246 npm1,827-
- AlicenseNot gradedqualityDmaintenanceThis read-only MCP Server allows you to connect to Zendesk data from Claude Desktop through CData JDBC Drivers. For full CRUD support, check out the first managed MCP platform: CData Connect AI (https://www.cdata.com/ai/).1MIT
Related Servers
- AlicenseNot gradedqualityAmaintenanceAn MCP server exposing scoped, read-only enterprise operations tools with fail-closed credential handling. It returns opaque approval IDs for mutations and requires a separate operator approval command to release one-time capabilities.MIT
- AlicenseNot gradedqualityBmaintenanceAn MCP server for agent authorization that tests the full effect surface and enforces control over consequential actions before dispatch, emitting verifiable execution evidence.2Apache 2.0
- FlicenseNot gradedqualityCmaintenanceMCP server that evaluates agent actions against a Policy State Machine, emits a tamper-evident audit trail, and dispatches approved transitions to internal or federated handlers.-
- AlicenseNot gradedqualityDmaintenanceMCP Server for AI agent identity and authorization. Create, verify, and manage agent identities with trust scores and scoped authorization tokens.MIT
- AlicenseNot gradedqualityAmaintenanceMCP server for permissioned, structured agent-to-agent communications, enabling agents to coordinate and negotiate through scoped, typed messages with authentication and audit logging.1,004 PyPIMIT
- AlicenseBqualityBmaintenanceAn MCP server that enforces deterministic authorization boundaries for AgentTeams workflows by verifying evidence and policy, returning ALLOW, BLOCK, or REQUIRE_APPROVAL decisions before actions are executed.6Apache 2.0
TDQS
Scored across 14 tools
Every tool targets a distinct action or resource: credential issuance vs delegation, verification vs revocation-only checks, audit trail vs evidence retrieval, and action logging vs status reporting are all clearly separated, often with explicit cross-references in the descriptions.
All tools use a consistent verb_noun convention (issue_credential, list_tasks, grant_approval), with straightforward nouns and predictable prefixes.
14 tools is a well-scoped surface for the attestation domain: credential lifecycle, audit/evidence, reporting, and approval workflows are all represented without redundancy.
Coverage is complete for the stated purpose: issuing and delegating credentials, revocation, verification, task discovery, audit/evidence retrieval, reporting, and the full approval lifecycle are all present with no apparent dead ends.