Quotor
Enables AI agents to get real home & auto insurance quotes and start binding through a network of licensed independent agencies.
README
home-auto-insurance-quotes
Quotor — an agent skill that gets real home & auto insurance quotes, and starts a binding, through a network of licensed independent agencies.
This repository packages a portable Agent Skill that any AI agent or assistant (Claude, ChatGPT, Hermes, OpenClaw, Codex-style agents, and other MCP-capable runtimes) can pull in to quote and help bind home, auto, and bundled insurance. The skill is the front door; a hardened MCP server is the infrastructure behind it.
Coverage: Texas today (home, auto, home+auto bundles; renters & other lines via lead capture), expanding nationally. The skill always checks eligibility per state and product before quoting.
What it does
- Real quotes, not estimates. Returns live multi-carrier rates for the customer's state and product.
- Two integration styles:
- Conversational — an assistant does a quick intake in chat and reads back quotes.
- Agentic — a system connects the MCP server directly and runs the full quote-to-bind flow.
- Quote → bind handoff. When the customer is ready, the skill starts a binding by routing them to a licensed agency with a secure link. A licensed human finalizes the policy — the network orchestrates the shopping; the agency owns the relationship.
How it's structured
home-auto-insurance-quotes/
├── SKILL.md # the skill itself (agentskills.io spec)
├── README.md # this file (for humans browsing the repo)
└── references/
└── mcp-connection.md # endpoint, auth (none required), tool schemas, raw examples
- SKILL.md is what agents load. It documents the two usage pathways, the tool set and call order, intake guidance, worked examples, and the MCP connection details.
- references/mcp-connection.md is the technical reference for the MCP endpoint: URL, authentication, context headers, per-tool schemas, and copy-paste JSON-RPC examples.
Connecting to the MCP
- Endpoint:
https://mcp.quotor.ai(Streamable HTTP, JSON-RPC 2.0). - Auth: none required. All tools work anonymously — connect and quote, no sign-up, no key (anonymous traffic is rate-limited and spend-capped server-side). End customers never need a key.
- Optional partner key (instant, self-serve): integrating at volume?
POST <endpoint>/keyswith{ "partner_label": "...", "email": "..." }→ returns anapi_keyshown once. Send it asAuthorization: Bearer <api_key>to give your integration its own rate/spend caps and attribution instead of sharing the anonymous pool.
Add it to your MCP client (claude.ai custom connectors, Claude Desktop, Cursor, VS Code, or any Streamable-HTTP MCP client) — no headers needed:
{
"mcpServers": {
"quotor": {
"type": "http",
"url": "https://mcp.quotor.ai"
}
}
}
The machine-readable manifest is server.json (official MCP registry schema) — that's
what client tooling and directory crawlers read.
See references/mcp-connection.md for the full handshake.
Security & privacy posture
- Quote-only scope. The MCP cannot reach carrier portal credentials, cannot service or cancel existing policies, and cannot finalize a bind without a licensed human. A bind request is a routed handoff, not an automated purchase.
- Rate- and spend-capped: anonymous traffic draws per-IP and per-quote budgets under a hard daily spend ceiling; optional partner keys carry their own caps — no single caller can run up cost.
- Every call logged; anomalous usage (auth-failure spikes, off-hours surges) is monitored.
- Customer data is protected: quotes create prospect records and never overwrite existing customers; a returning customer's current premium is only ever returned to an authenticated partner, never on an anonymous call.
Status
Live. The MCP is deployed in production — rate and spend caps and full audit logging are in force;
API keys are optional (partner attribution + dedicated caps). Coverage is Texas today (home, auto,
bundles; other lines via lead capture), expanding nationally; always call check_eligibility first.
License
Apache-2.0.
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。