AI price server URL is not applicable

If your AI price server URL is not applicable, it usually indicates a misconfiguration in the client setup, an outdated client version, or network access restrictions.Common CausesIncorrect URL or JSON Schema AI clients often require a valid URL in the configuration schema. If the URL is missing, malformed, or placed incorrectly in the JSON/YAML file, the client cannot connect. For example, OpenAI plugin configurations require the servers field to contain a properly formatted URL, and indentation errors in YAML can prevent recognition of the server URL .Client Version Compatibility Some AI clients, like Claude Desktop, require a recent version to support remote MCP server URLs. Older versions may not recognize the url field and fail to connect .Network or Access Restrictions If the server is hosted on a private network or behind a firewall, requests may be blocked. For instance, Azure AI Search can return 403 errors if public access is disabled or RBAC permissions are not correctly configured . Similarly, Cursor AI may fail to route requests correctly if API keys or model selections conflict with overridden OpenAPI URLs .Recommended SolutionsVerify URL Format: Ensure the server URL is complete and accessible. For ATOM MCP Server, the production URL is https://atom-mcp-server-production.up.railway.app/mcp .Update Client: Use the latest version of your AI client to ensure remote URL support.Use Proxy or NPX Method: If direct URL access fails, some clients support a proxy command, e.g., "command": "npx", "args": ["mcp-remote", ""] .Check Network Access: Confirm that firewalls, private endpoints, or RBAC settings allow your client to reach the server.Validate JSON/YAML Schema: Ensure the servers field is correctly indented and contains a valid URL. Avoid placing it inside unrelated objects like info in OpenAPI 3.0/3.1 schemas .API Key and Model Conflicts: Make sure the API key matches the server and model configuration. Conflicts can cause requests to fail or route to the wrong endpoint .Additional TipsTest the server URL in a browser or with curl to confirm accessibility.If using a subdomain for hosting, ensure the plugin JSON or OpenAPI spec is hosted on the same domain as the API endpoint .For temporary issues, using a local proxy or tunneling service like ngrok can help bypass network restrictions . By following these steps, you can identify whether the "not applicable" error is due to configuration, client version, network restrictions, or schema issues, and apply the appropriate fix.