Anima MCP Serverofficial
A
licenseNot graded
qualityA
maintenanceEnables AI assistants to connect over streamable HTTP with bearer authentication to tools for agent lifecycle, email, phone, platform, vault, and browser extension management.
2
MIT
Praxicraft Assess MCP
OfficialRelated Servers
Alternatives to Praxicraft Assess MCP
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityAmaintenanceEnables users to retrieve and manage tickets and comments, analyze tickets and draft responses, and access Help Center articles as a knowledge base through per-operator OAuth-authenticated access.-
- AlicenseNot gradedqualityCmaintenanceConnects MCP-capable assistants to support tickets and Agent Tasks through OAuth, exposing read tools for tickets, bots, task runs, and report templates. It also provides scoped write actions such as ticket replies, status and tag updates, draft approvals, task creation, and run decisions.MIT
- AlicenseAqualityBmaintenanceEnables agents to manage social media publishing, media uploads, and content queues through the Postifys API.1717 npmMIT
- FlicenseNot gradedqualityAmaintenanceEnables users to retrieve and manage tickets and comments, analyze tickets, draft responses, and access Help Center articles as a knowledge base, with OAuth-based per-operator permissions.-
- FlicenseNot gradedqualityAmaintenanceEnables AI assistants to retrieve and manage support tickets, comments, and attachments, and to search help center articles as a knowledge base, with each request carrying the operator's own OAuth-authenticated permissions.-
TDQS
C2.7/5.0
Scored across 59 tools
Disambiguation4/5
Tools are organized by resource (assessments, cases, invites, interviews, webhooks, etc.) with clear action verbs. A few pairs like list_org_team vs list_squad_members and list_cases vs list_platform_cases vs list_interview_org_cases could cause mild confusion, but descriptions disambiguate effectively.
Naming Consistency5/5
All 59 tools follow a consistent snake_case verb_noun pattern (list_*, get_*, create_*, update_*, delete_*, etc.). No camelCase or mixed conventions, making the set highly predictable.
Tool Count1/5
With 59 tools, this server is far beyond the typical well-scoped 3-15 tool range. Even for a broad platform, the size feels excessive and would be better split into focused sub-servers (assessments, interviews, webhooks, etc.).
Completeness4/5
The surface covers core CRUD and lifecycle operations for assessments, invites, interviews, cases, and webhooks, including bulk actions and analytics. Minor gaps exist (e.g., no delete_assessment, no update_pipeline), but agents can work around them without major failures.