ClearPolicy

Created By
ClearPolicy2 months ago
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.
Overview

ClearPolicy lets you send document signature and acknowledgment requests directly from your AI workflow. Connect once with OAuth and your AI assistant can manage your entire policy compliance process — import documents from a URL (PDF or Word .docx), find people in your organization, send signing requests individually or in bulk, track who has and hasn't signed, and check the status of any outstanding request.

Every signature is recorded with a full audit trail — timestamp, IP address, and a signed receipt — giving your organization legally defensible proof of acknowledgment when it matters.

Tools included: list-people · get-person · list-signing-requests · get-signing-request · send-signing-request · cancel-signing-request · create-person

Example prompts:

  • "Who hasn't signed the staff handbook yet?"
  • "Send our volunteer policy to Garak McKenzie for signature"
  • "Cancel the pending request for Roy McKenzie on the parking policy"

Auth: OAuth 2.0 — connect at claude.com/connectors or use https://api.clearpolicy.app/mcp directly.

Server Config

{
  "mcpServers": {
    "clearpolicy": {
      "url": "https://api.clearpolicy.app/mcp"
    }
  }
}
Project Info
Created At
2 months ago
Updated At
2 months ago
Author Name
ClearPolicy
Star
-
Language
-
License
-
Category
Homepage

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago