A
licenseA
qualityD
maintenanceMCP server for AI agent trust verification, enabling agents to verify identities, check trust scores, and build reputation across multiple blockchain and web platforms.
12
10 npm
1
MIT
@verigent/mcp-server
Officialby Verigent-AI
Related Servers
Alternatives to @verigent/mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceMCP server that enables AI agents to verify each other's trust scores, register, submit reviews, and find trusted agents before transacting.410 npmMIT
- AlicenseNot gradedqualityDmaintenanceMCP Server for AI agent identity and authorization. Create, verify, and manage agent identities with trust scores and scoped authorization tokens.MIT
- AlicenseAqualityCmaintenanceMCP server for AgentFolio — the identity and reputation layer for AI agents. Query agent profiles, trust scores, verification status, and marketplace listings through 8 MCP tools.953 npm1MIT
- FlicenseNot gradedqualityBmaintenanceMCP server for the TETA+PI verified entity registry, enabling AI agents to search, verify, and route intents to trusted entities.1-
verfi-mcp-serverofficial
AlicenseNot gradedqualityCmaintenanceMCP server for Verfi — TCPA consent verification tools for AI agents.2 npmMIT
TDQS
A3.9/5.0
Scored across 14 tools
Disambiguation2/5
Several workflow tools overlap heavily: get_tasks and continue_run both start and return battery tasks, submit_answers duplicates continue_run's answer handling, and resume_run is explicitly described as unnecessary since continue_run can pick up the saved token on its own. Despite very detailed descriptions, an agent could easily select the wrong tool for the same step.
Naming Consistency3/5
Most tools follow a verb_noun snake_case pattern (start_verification, get_standings, revoke_credential), but probe_start, probe_call, probe_finish, and battery_call invert the order to noun_verb. The vocabulary is consistent and readable, but the mixed ordering is a noticeable deviation.
Tool Count4/5
14 tools is within a reasonable range for a server covering one-time verification, continuous probes, and counterparty due diligence. However, the set includes redundant workflow paths such as submit_answers vs continue_run and resume_run vs continue_run, making it slightly larger than it needs to be.
Completeness4/5
The surface covers the full verification lifecycle (start, fetch tasks, answer, drive, resume, get results), continuous probe sessions, counterparty due diligence, public standings, dispute reporting, and credential revocation. Minor gaps like a dedicated self-status query or explicit run cancellation are workable around, so it falls just short of complete.
Maintenance
ActivityActive
ResponsivenessNo issues