Server Details
ClearPolicy is a document signing and compliance tracking tool for organizations. Once connected, your AI assistant can import documents, send signature requests, track who has and hasn't signed, and manage your contacts — all by prompt.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
See and control every tool call
Available Tools
10 toolscancel-signing-request-toolInspect
Cancel a pending signature or acknowledgment request. This cannot be undone.
| Name | Required | Description | Default |
|---|---|---|---|
| request_id | Yes | The ULID of the signing request to cancel. |
create-person-toolInspect
Add someone new to the organization so they can be sent documents for signature or acknowledgment.
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Full name of the person. | |
| Yes | Email address of the person. Must be unique within the organization. | ||
| phone | No | Phone number in international format (e.g. +12125551234). |
get-document-toolInspect
Get details of a document, including how many people have signed or acknowledged it and how many haven't.
| Name | Required | Description | Default |
|---|---|---|---|
| document_id | Yes | The ULID of the document. |
get-person-toolInspect
Get a person's profile and see which documents they have or haven't signed or acknowledged.
| Name | Required | Description | Default |
|---|---|---|---|
| person_id | Yes | The ULID of the person. |
get-signing-request-toolInspect
Check whether a specific person has signed or acknowledged a document, and when.
| Name | Required | Description | Default |
|---|---|---|---|
| request_id | Yes | The ULID of the signing request. |
list-documents-toolInspect
Find documents available to send for employee signatures or policy acknowledgments. Use this to browse what documents the organization has ready to send.
| Name | Required | Description | Default |
|---|---|---|---|
| name | No | Filter documents by name (partial match, case-insensitive). |
list-people-toolInspect
Find people in the organization who can be sent documents for signature or acknowledgment. Search by name or email.
| Name | Required | Description | Default |
|---|---|---|---|
| name | No | Filter by name (partial match, case-insensitive). | |
| No | Filter by email address (partial match). | ||
| include_archived | No | Include archived people in the results. Defaults to false. |
list-signing-requests-toolInspect
Check who has signed a document and who hasn't. Filter by document, person, or status (pending, signed, expired, etc.) to track compliance.
| Name | Required | Description | Default |
|---|---|---|---|
| status | No | Filter by status: created, sent, viewed, attested, expired, or canceled. | |
| person_id | No | Filter by person ULID. | |
| document_id | No | Filter by document ULID. |
send-reminder-toolInspect
Nudge someone who hasn't signed or acknowledged a document yet by sending them a reminder email.
| Name | Required | Description | Default |
|---|---|---|---|
| request_id | Yes | The ULID of the signing request to send a reminder for. |
send-signing-request-toolInspect
Send a document to one or more people to sign or acknowledge. Use this when a user wants their team or contacts to sign a policy, agreement, or compliance document.
| Name | Required | Description | Default |
|---|---|---|---|
| person_ids | Yes | Array of person ULIDs to send the request to. | |
| document_id | Yes | The ULID of the document to send. | |
| attestation_type | No | Override the attestation type: "acknowledgment" or "signature". Defaults to the document's default. |
Verify Ownership
This connector has been claimed. The /.well-known/glama.json file has been verified and ownership is confirmed.
Glama periodically re-verifies ownership. If the file is removed, the claim will be revoked.
Control your server's listing on Glama, including description and metadata
Receive usage reports showing how your server is being used
Get monitoring and health status updates for your server
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!