status_resource — X1-BaaS Scraping API MCP Resource

status_resource is one of 2 resources on the X1-BaaS Scraping API MCP server. Connect the server and your client can attach it as context.

by client

How to attach status_resource from your client

• Claude Code X1-BaaS Scraping API Resource/status_resource run in your project directory
• Claude Desktop X1-BaaS Scraping API Resource/status_resource ~/Library/Application Support/Claude/claude_desktop_config.json
• Cursor X1-BaaS Scraping API Resource/status_resource ~/.cursor/mcp.json
• VS Code X1-BaaS Scraping API Resource/status_resource .vscode/mcp.json
• Zed X1-BaaS Scraping API Resource/status_resource ~/.config/zed/settings.json
• Windsurf X1-BaaS Scraping API Resource/status_resource ~/.codeium/windsurf/mcp_config.json
• Cline X1-BaaS Scraping API Resource/status_resource ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
• Gemini CLI X1-BaaS Scraping API Resource/status_resource ~/.gemini/settings.json
• Grok X1-BaaS Scraping API Resource/status_resource .mcp.json (in your project root)
• ChatGPT X1-BaaS Scraping API Resource/status_resource Settings → Connectors → Advanced → Developer mode
• Claude.ai X1-BaaS Scraping API Resource/status_resource Settings → Connectors → Add custom connector
• LangChain X1-BaaS Scraping API Resource/status_resource pip install langchain-mcp-adapters

Other resources on this server

• pricing_resource

Read from the server itself, by connecting to it and calling resources/list on 24 September 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.