WaiverFile integration for AI agents.
WaiverFile integration for AI agents with secure authentication and server-side credential injection. Open Connector runs the OAuth, seals the token in an encrypted vault, and serves WaiverFile tools to your agent over MCP or a typed API — credentials injected server-side, every call audited, nothing leaving your infrastructure. Open source (AGPL-3.0) and self-hostable.
Real WaiverFile actions, managed and audited.
Your user connects WaiverFile once; your agent can then waiverFile offers an online waiver form system that allows individuals to sign their release waivers from a computer, tablet, or mobile device — scoped to the OAuth permissions you grant and the tool allowlist you configure. Every action is least-privilege and written to a tamper-evident audit trail.
- 1
Your user grants WaiverFile access once (OAuth) — the token lands in the vault.
- 2
Your agent calls a tool over MCP or the typed API; Open Connector injects the credential server-side.
- 3
Every routed call appends a hash-chained audit record — nothing leaves your infra.
Supported WaiverFile tools.
0 tools are generated from the published WaiverFile catalog. Descriptions are plain text; each action remains subject to its configured authentication and tool allowlist.
Showing 0 tools. All published catalog entries are included in this page's server-rendered HTML.
No tools match “”.
WaiverFile integration, answered
- How do AI agents use WaiverFile through Open Connector?
- Your user connects WaiverFile once with one of its cataloged authentication methods. Open Connector stores the credential in an encrypted vault and exposes WaiverFile tools to your agent over MCP or a typed API, with credentials injected server-side on each call.
- Is this a WaiverFile MCP server?
- Yes. Open Connector can serve WaiverFile as a named MCP server with a scoped allowlist and a per-user connection URL, so any MCP client can call WaiverFile actions with credentials injected server-side.
- Where do WaiverFile credentials live?
- In your own infrastructure. Open Connector keeps credentials in its own vault and injects them at call time, so they never leave your environment.
Give your agents WaiverFile — keep the keys.
Open source, self-hostable, with WaiverFile credentials that never leave your infrastructure. Run it from source today.