Praxicraft Assess MCP
OfficialRelated Servers
Alternatives to Praxicraft Assess MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables agents to manage social media publishing, media uploads, and content queues through the Postifys API.1717 npmMIT
- FlicenseNot gradedqualityBmaintenanceEnables access to all DocuSign product APIs through curated tools and raw API calls, with OAuth support for hosted MCP clients.-
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to securely access and manage CRM pipeline, relationships, tasks, notes, files, and deal context through authenticated Streamable HTTP/OAuth, inheriting the signed-in user's permissions and business-unit isolation.1MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to securely connect to a vybeflow tenant for multi-channel messaging operations such as reading inbox tickets, looking up contacts, checking campaign progress, and sending messages under scoped permissions.MIT
- AlicenseNot gradedqualityDmaintenanceEnables agents to invoke any REST or SOAP service by sending a normalized payload, with support for API key, Basic, Bearer, and OAuth2 auth. Connectors can be registered once and reused by name.Apache 2.0
- AlicenseNot gradedqualityCmaintenanceA hosted, OAuth-authenticated MCP endpoint exposing 176 tools that let AI assistants read and write jobs, candidates, applications, interviews, scorecards, prospects, talent pools, and imports within an organization's own applicant tracking data, scoped to the signed-in user's existing permissions.MIT
TDQS
Scored across 59 tools
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.
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.
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.).
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.