NM Signals MCP MCP server

The NM Signals MCP server allows AI agents to perform AI visibility audits on web URLs. It exposes tools to run full readiness engines, check crawl access, and retrieve quota status, enabling developers to verify and improve how their websites are perceived by AI crawlers.

Endpoint and access

OAuth sign-in: the first time you connect, your client opens the vendor's own authorization prompt in a browser.

OAuth sign-inEndpoint checked 2026-10-05Operated by Nyman Media

MCP endpoint (Streamable HTTP)

https://app.nyman.media/api/mcp

Vendor documentation

What you can do with it

Run AI visibility audits on specific URLs
Check API key quota and tier status
Verify crawl access for AI agents

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

claude mcp add --transport http nm-signals-mcp https://app.nyman.media/api/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Codex configuration

codex mcp add nm-signals-mcp --url https://app.nyman.media/api/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable nm-signals-mcp in your MCP settings.

Cursor configuration

{
  "mcpServers": {
    "nm-signals-mcp": {
      "url": "https://app.nyman.media/api/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.

Cline configuration

{
  "mcpServers": {
    "nm-signals-mcp": {
      "type": "streamableHttp",
      "url": "https://app.nyman.media/api/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start nm-signals-mcp and inspect its tools.

VS Code configuration

{
  "servers": {
    "nm-signals-mcp": {
      "type": "http",
      "url": "https://app.nyman.media/api/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.

Gemini CLI configuration

gemini mcp add --transport http nm-signals-mcp https://app.nyman.media/api/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.

Claude Desktop configuration

{
  "mcpServers": {
    "nm-signals-mcp": {
      "url": "https://app.nyman.media/api/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

{
  "mcpServers": {
    "nm-signals-mcp": {
      "serverUrl": "https://app.nyman.media/api/mcp"
    }
  }
}

See all 957

Do you run NM Signals MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing