Secure, fast setup—loading your page.
Please wait while this screen opens.
Stop switching tabs. Ask Claude whether your guests have signed — and send waivers to anyone who has not — from the same conversation.
WaiverTrail exposes a small set of MCP tools over HTTPS. You paste your organization's connector URL, then Claude completes OAuth token negotiation using standards-based discovery metadata. Bearer API keys remain a temporary fallback. Legacy URL-key mode is migration-only and should stay disabled by default in production. Each request is authenticated, rate-limited, and tied to your organization — never to a tenant id supplied by the model.
With mcp:read, Claude can list templates and waivers and read non-PII status fields. With mcp:send, Claude may create outbound invites subject to hourly limits and your plan quota.
WaiverTrail uses scoped API keys for the Claude integration. Claude only accesses the data you explicitly authorize — and you can revoke access at any time from your Settings page. Signer personal data (names, emails, dates of birth) is not returned by version 1 MCP tools. All requests are logged in your WaiverTrail MCP audit history.
https://waivertrail.com/api/mcp/claude — no API key or client ID needed.It is a secure connection that lets Claude check waiver status, list templates, and send invites — all from your Claude conversation. You connect once via browser sign-in and Claude handles the rest.
You need access to Claude with custom connectors (for example Claude Pro or team plans, depending on Anthropic’s current offering). WaiverTrail handles your waiver data and permissions.
Claude browser sign-in (OAuth MCP) is available on every plan for eligible team members. Optional REST API keys for machine-to-machine MCP still follow the API access tier on your pricing page.
Not by default. Version 1 tools return waiver metadata and status only — not signer name, email, or date of birth.
In Claude, remove the WaiverTrail connector from Settings → Integrations. Access stops immediately.
Yes. Requests use HTTPS, hashed API keys in our database, per-organization rate limits, and an audit log of MCP tool calls.
Only if you create a key with the send scope. Sending is rate-limited and respects your waiver quota.
New billable sends are blocked until your quota resets or you upgrade, same as other invite flows.
New to WaiverTrail? Start your free trial and connect Claude from Settings → Integrations in minutes. Upgrade when you need API keys or advanced automation.