OpsLevel MCPofficial
A
licenseNot graded
qualityF
maintenanceModel Context Protocol (MCP) server for OpsLevel
12
MIT
boldsign
Officialby boldsign
Related Servers
Alternatives to boldsign
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceModel Context Protocol (MCP) Server for the mcp API.2,530 npmMIT
- AlicenseNot gradedqualityCmaintenanceMCP server for the Dropbox Sign API supporting signature requests, templates, teams, accounts, events, documents, signers, reports, bulk operations, and workflows.MIT
- FlicenseNot gradedqualityDmaintenanceA server implementation of the Model Context Protocol (MCP) that provides REST API endpoints for managing and interacting with MCP resources.-
mcp-signwellofficial
AlicenseAqualityBmaintenanceModel Context Protocol server that orchestrates SignWell's e-signature workflows — create, send, track, and manage documents and templates.14229 npm2MIT
Apideck MCPofficial
AlicenseAqualityAmaintenanceModel Context Protocol server for the Apideck Unified API. Connect any MCP-compatible agent framework to 100+ accounting systems, HRIS platforms, file storage providers, and more through one integration. More information https://www.apideck.com/mcp-server4414 npm21MIT
TDQS
A3.7/5.0
Scored across 14 tools
Disambiguation4/5
Most tools are clearly distinct by resource type (e.g., contact, document, template, team, user) and action (get vs. list). However, list_documents and list_team_documents have overlapping purposes that could cause confusion about which to use for team-related document listings, and send_document_from_template lacks a complementary create_document tool, creating a minor gap in the action set.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern with snake_case, such as get_contact, list_contacts, revoke_document, and send_reminder_for_document_sign. The naming is predictable and uniform across all 14 tools, making it easy for agents to understand the pattern.
Tool Count5/5
With 14 tools, the count is well-scoped for a document signing and management server like BoldSign. It covers key resources (contacts, documents, templates, teams, users) with appropriate CRUD-like operations, avoiding both bloat and thin coverage, which is typical for such domains.
Completeness4/5
The tool set provides good coverage for retrieving and listing resources, with specific actions like revoke_document and send_reminder_for_document_sign. However, there are notable gaps: no create_document (only send_document_from_template), no update or delete operations for contacts, templates, teams, or users, and no tools for managing document signatures or status changes beyond revocation, which could limit agent workflows.
Maintenance
ActivityInactive
ResponsivenessLimited data