coverage — dealcheck: US property deal-check MCP Resource
coverage
is one of 2 resources on the
dealcheck: US property deal-check
MCP server. Connect the server and your client can attach it as context.
by client
How to attach coverage from your client
- Claude Code dealcheck: US property deal-check Resource/coverage run in your project directory
- Claude Desktop dealcheck: US property deal-check Resource/coverage ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor dealcheck: US property deal-check Resource/coverage ~/.cursor/mcp.json
- VS Code dealcheck: US property deal-check Resource/coverage .vscode/mcp.json
- Zed dealcheck: US property deal-check Resource/coverage ~/.config/zed/settings.json
- Windsurf dealcheck: US property deal-check Resource/coverage ~/.codeium/windsurf/mcp_config.json
- Cline dealcheck: US property deal-check Resource/coverage ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI dealcheck: US property deal-check Resource/coverage ~/.gemini/settings.json
- Grok dealcheck: US property deal-check Resource/coverage .mcp.json (in your project root)
- ChatGPT dealcheck: US property deal-check Resource/coverage Settings → Connectors → Advanced → Developer mode
- Claude.ai dealcheck: US property deal-check Resource/coverage Settings → Connectors → Add custom connector
- LangChain dealcheck: US property deal-check Resource/coverage pip install langchain-mcp-adapters
Other resources on this server
dealcheck: US property deal-check also offers 1 prompt — things you invoke, where a resource is context you attach.
Read from the server itself, by connecting to it and calling resources/list on 14 November 2026.
A listing does not declare its resources, so asking is the only way to know them, and this
is what the server actually offers rather than what its listing claims. Names only are
stored; connect the server for each resource's type and contents.