domain_lookup — profullstack-mcp MCP Resource
domain_lookup
is one of 53 resources on the
profullstack-mcp
MCP server. Connect the server and your client can attach it as context.
by client
How to attach domain_lookup from your client
- Claude Code profullstack-mcp Resource/domain_lookup run in your project directory
- Claude Desktop profullstack-mcp Resource/domain_lookup ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor profullstack-mcp Resource/domain_lookup ~/.cursor/mcp.json
- VS Code profullstack-mcp Resource/domain_lookup .vscode/mcp.json
- Zed profullstack-mcp Resource/domain_lookup ~/.config/zed/settings.json
- Windsurf profullstack-mcp Resource/domain_lookup ~/.codeium/windsurf/mcp_config.json
- Cline profullstack-mcp Resource/domain_lookup ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI profullstack-mcp Resource/domain_lookup ~/.gemini/settings.json
- Grok profullstack-mcp Resource/domain_lookup .mcp.json (in your project root)
- ChatGPT profullstack-mcp Resource/domain_lookup Settings → Connectors → Advanced → Developer mode
- Claude.ai profullstack-mcp Resource/domain_lookup Settings → Connectors → Add custom connector
- LangChain profullstack-mcp Resource/domain_lookup pip install langchain-mcp-adapters
Other resources on this server
- template
- template docs
- template examples
- readme-badges
- readme-badges docs
- readme-badges examples
- craigslist
- seo-ranking
- seo-ranking docs
- seo-ranking examples
- wcag
- wcag examples
- scanner
- scanner docs
- scanner examples
- example
- social-poster
- social-poster docs
- social-poster examples
- fake_json
- fake_json docs
- fake_json examples
- tides-currents
- crypto-badge docs
- crypto-badge examples
- link-shortener
- qr-generator
- qr-generator examples
- lighthouse
- lighthouse docs
- lighthouse examples
- test-module
- weather
- weather examples
- health-check
- backlinks
- backlinks docs
- backlinks examples
- email_checker
- email_checker docs
Read from the server itself, by connecting to it and calling resources/list on 11 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.