DEVELOPER RESOURCES
DateHog MCP connector.
DateHog exposes a public Model Context Protocol endpoint for Claude. Claude reads the document or structured transaction details; DateHog calculates supported Washington deadlines and returns calendar, portal, and account actions.
Connector endpoint
Add this HTTPS endpoint as a custom connector in Claude:
Agents and API clients can inspect DateHog's machine-readable OpenAPI 3.1 specification.
When to use it
Use the connector when Claude has extracted a mutual-acceptance date and transaction milestones from a Washington real estate agreement, or when a user supplies those details directly and wants DateHog to calculate and organize the resulting dates.
Authentication behavior
DateHog uses OAuth 2.1 authorization code flow with PKCE for agent and API access. Saving a deal, opening account data, synchronizing calendars, and creating the client workflow require the user to sign in and approve access. The connector does not bypass account limits or ownership checks. Authorization server metadata is publicly discoverable.
Available tools
- parse_and_sync_contractAccepts structured transaction events and a mutual-acceptance date, applies supported Washington calculation rules, and returns the calculated milestones with appropriate DateHog action links.
- list_active_dealsReturns the signed-in user's DateHog transactions and upcoming milestones. This tool requires authentication.
- get_checkout_urlReturns the DateHog support contact for payment questions. DateHog does not currently provide online checkout.
What the connector does not do
The connector does not replace review of the signed agreement, provide legal advice, or guarantee that Claude extracted every term correctly. The responsible real estate professional must verify all dates and transaction instructions.
Support
For connector setup or behavior questions, email support@datehog.com. Include the tool name and a description of the problem, but do not email private contract documents.