NM Signals: AI crawler audit

io.github.newmediamadmanPublished by GitHub account newmediamadmanv0.1.0Updated Oct 24, 2026

Audit webpage access for AI crawlers. API key and Premium or Partner plan required.

The publisher's own server: SIGNALS Loyalty Agent Platform

VerifiedStreamable HTTPWeb executableWeb Search & Scraping

Overview

AI-generated overview

A remote MCP server that lets an assistant audit how webpages are accessed by AI crawlers, using an NM Signals account.

What you can do
Audit webpage access for AI crawlers, checking how AI crawler requests are handled on a page or site. Results are tied to your NM Signals account and plan. The manifest lists no individual tools, so the exact operations are not documented here.
When to use it
Useful when you want an assistant to check whether a site is reachable and readable by AI crawlers, for example when reviewing crawler access or AI visibility for a page.
Requirements
Remote streamable HTTP endpoint at app.nyman.media, with OAuth authentication. Requires an NM Signals API key from Account settings, sent as an Authorization header in the form Bearer followed by the key. A Premium or Partner plan is required.
Before you install
You must supply your own NM Signals API key as the Authorization header; treat it as a secret. Access is limited to paid Premium or Partner plans, so a subscription is involved. Audit requests are sent to the NM Signals service.

Installation

In SourceWeft

  1. Open NM Signals: AI crawler audit in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.newmediamadman%2Fnm-signals/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "nm-signals-ai-crawler-audit": {
      "type": "http",
      "url": "https://app.nyman.media/api/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.1.0LatestSep 23, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Signals integrations