Server name
sanjibani/passare-mcp
Repository
https://github.com/sanjibani/passare-mcp
Description
First MCP server for the Passare Public API - the leading US funeral home management platform used by thousands of independent funeral homes, plus adjacent multi-location deathcare operators. 9 read-only tools covering the full Passare read surface: cases (list / get / acquaintances / new / updated), address, contacts (phone / email). Bearer-token auth via PASSARE_API_KEY + PASSARE_ORGANIZATION_ID (UUID issued by Passare after the public API access form). 30 tests via respx + hypothesis, ruff + mypy --strict clean, isError-compliance per the Blackwell MCP security audit pattern, JSONL audit logging per tool call with secret redaction (PASSARE_API_KEY, PASSARE_ORGANIZATION_ID, Authorization header all auto-redacted in the audit trail), typed exception hierarchy, application-level retry with exponential backoff honoring Retry-After, dispatch table for HTTP status -> exception. Saturation check confirmed: no first-party Passare MCP, no Zapier / Composio / Vinkius wrapper covers Passare specifically, no Tribute/Frazer MCP either. Part of the same vertical-MCP portfolio as hawksoft, open-dental, ezyvet, jobber, practicepanther, cox-automotive, qualia, campspot, cleancloud, playmetrics, foreup, storedge, courtreserve, procare.
Tools exposed
9
Connection info
- Installation: see repo README
- Transport: stdio (default)
- Auth: env vars (PASSARE_API_KEY (required, bearer token from Passare support) + PASSARE_ORGANIZATION_ID (required, UUID of your funeral home) + PASSARE_BASE_URL (optional, defaults to https://api.passare.com) + PASSARE_AUDIT_LOG (optional JSONL audit log file path, defaults to stderr))
Self-check
Server name
sanjibani/passare-mcp
Repository
https://github.com/sanjibani/passare-mcp
Description
First MCP server for the Passare Public API - the leading US funeral home management platform used by thousands of independent funeral homes, plus adjacent multi-location deathcare operators. 9 read-only tools covering the full Passare read surface: cases (list / get / acquaintances / new / updated), address, contacts (phone / email). Bearer-token auth via PASSARE_API_KEY + PASSARE_ORGANIZATION_ID (UUID issued by Passare after the public API access form). 30 tests via respx + hypothesis, ruff + mypy --strict clean, isError-compliance per the Blackwell MCP security audit pattern, JSONL audit logging per tool call with secret redaction (PASSARE_API_KEY, PASSARE_ORGANIZATION_ID, Authorization header all auto-redacted in the audit trail), typed exception hierarchy, application-level retry with exponential backoff honoring Retry-After, dispatch table for HTTP status -> exception. Saturation check confirmed: no first-party Passare MCP, no Zapier / Composio / Vinkius wrapper covers Passare specifically, no Tribute/Frazer MCP either. Part of the same vertical-MCP portfolio as hawksoft, open-dental, ezyvet, jobber, practicepanther, cox-automotive, qualia, campspot, cleancloud, playmetrics, foreup, storedge, courtreserve, procare.
Tools exposed
9
Connection info
Self-check