Hosted MCP server/Marketing

Advisors AI Service Navigator MCP server

Hosted at advisorsai.ai·Streamable HTTP

Advisors AI Service Navigator is listed in the official MCP Registry as ai.advisorsai/service-navigator version 1.1.0. Its registry description says an agent can describe a store's problem and get the matching service, its fixed price, and a request link. The published remote endpoint is https://advisorsai.ai/mcp over Streamable HTTP. The registry entry does not list tools or an authentication requirement, and the provider website is a short Arabic landing page without MCP documentation.

advisorsai.ai Streamable HTTP Not verified Source checked Nov 12, 2026 Server responded when checked Reviewed 2026-11-16
About

Where it fits

Store owners and agencies that want an assistant to route a business problem to an Advisors AI service and prepare a request link.

  • Describe a store problem and get the matching Advisors AI service.
  • Look up the published fixed price for that service.
  • Prepare the ordinary request link without creating an order.

A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.

Setup

Install it in your client

Choose a client, run the command or use the one-click install, then verify the connection. The endpoint uses Streamable HTTP.

All client guides
  1. 01

    Run this command in your terminal

    This adds Advisors AI Service Navigator as a remote Streamable HTTP server in Claude Code.

    Claude Code
    claude mcp add --transport http advisors-ai-service-navigator https://advisorsai.ai/mcp --scope project
  2. 02

    Verify the connection

    Run claude mcp list, or open /mcp in a Claude Code session.

    Learn more about MCP in Claude Code

More clients, including project and global config files, are in the sidebar.

Connection

Endpoint and configuration

Endpoint
https://advisorsai.ai/mcp
Host
advisorsai.ai · /mcp
Transport
Streamable HTTP
Authentication
Not verified
Server name
advisors-ai-service-navigator
Listing type
Community or directory listing

The installer uses the server name advisors-ai-service-navigator. If you add the endpoint by hand, keep the same name so the guide and your config match.

Verification

Check the connection

After you add the server, confirm that the client can see its tools and that one small request returns what the provider describes.

  1. 1
    Open the tool list.

    Restart the client or start a new session. Confirm that advisors-ai-service-navigator appears and that the tools match the provider documentation.

  2. 2
    Run one small request.

    Start with: Describe a store problem and get the matching Advisors AI service. Check the result before you give the server more access.

  3. 3
    Check permissions.

    Review the OAuth scopes or API-key permissions, then remove the server and revoke its token when you no longer need it.

Server responded when checked

We reached advisorsai.ai when we checked. That only means the address answered; it does not prove the MCP connection, sign-in, or tools work. The provider page was available when we checked.

Provider page available on Nov 12, 2026. A response does not guarantee the server is safe or that sign-in and tools will work.

Troubleshooting

Common failure modes

These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.

  • Authentication fails or no tools appear. The listing does not verify the provider's credential flow; check its documentation before retrying.
  • The endpoint responds but rejects tool calls. Confirm the current address and any account, key, or payment requirement with the provider.
  • Your client does not support Streamable HTTP. Use a client that does, and confirm the provider's current endpoint and transport in its docs.
Safety

Before you connect

Remote means provider access
  • The provider can see the requests and data your agent sends through the server.
  • Review OAuth scopes and API-key permissions. Start read-only if the provider offers it.
  • Use project scope for repository-specific servers; use global scope for personal tools.
  • Remove the server and revoke its token when you stop using it.
Review path

Check the connection before a real task

These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.

Reference

Provider documentation

Setup requirements, available tools, and rate limits live with the provider. Use the source link as the authority for this server.

Advisors AI Service Navigator documentationhttps://registry.modelcontextprotocol.io/v0/servers?search=ai.advisorsai