Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

com.mambabuilt/mcp-ai-tooling-detector

NPM · @MAMBALABSDEV/MCP-AI-TOOLING-DETECTOR · SCANNED AUG 7

Detect whether a company declares, deploys, or charges for AI, with evidence.

Available components

npm · @mambalabsdev/mcp-ai-tooling-detector 64
64 Trust /100
Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →

Supply Chain Security87
  • No malware found by supply-chain analysis.Pass
  • Known CVEs were checked across the 95 of 99 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
  • No install/post-install scripts declared.Pass
  • Dependency health was assessed across the 95 of 99 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability69
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 283 tokens (~283/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · @mambalabsdev/mcp-ai-tooling-detector

# add to Claude Code
claude mcp add com-mambabuilt-mcp-ai-tooling-detector -- npx -y @mambalabsdev/mcp-ai-tooling-detector
# add to Codex CLI
codex mcp add com-mambabuilt-mcp-ai-tooling-detector -- npx -y @mambalabsdev/mcp-ai-tooling-detector
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-mambabuilt-mcp-ai-tooling-detector": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@mambalabsdev/mcp-ai-tooling-detector"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-mambabuilt-mcp-ai-tooling-detector --command npx --arg -y --arg @mambalabsdev/mcp-ai-tooling-detector
# ~/.hermes/config.yaml
mcp_servers:
  com-mambabuilt-mcp-ai-tooling-detector:
    command: "npx"
    args: ["-y", "@mambalabsdev/mcp-ai-tooling-detector"]
// mcp.json
{
  "mcpServers": {
    "com-mambabuilt-mcp-ai-tooling-detector": {
      "command": "npx",
      "args": [
        "-y",
        "@mambalabsdev/mcp-ai-tooling-detector"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 6 Aug 26 64

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 7 Aug 2026 · Analysed npm/@mambalabsdev/[email protected]

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm
Dependencies 95 packages
Packages resolved 95
Deprecated 95
Stale 29
Tree resolution Partial

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools · 1 exposed · ~283 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens
detect_ai_tooling ~283

Given a company domain, determine how far that company has actually gone with AI. Returns an ai_maturity tier of none, declared (says AI but nothing observable is running), deployed (AI tooling is live on the site), or commercialized (the pricing page charges for AI via credits, tokens, an add-on, an AI-named plan, or a per-outcome price). Also returns the detected AI vendors and categories, validated llms.txt status, robots.txt AI-crawler policy, and the quotable evidence strings behind the verdict. A domain behind a bot challenge comes back with blocked=true at low confidence rather than as a false negative. Public data only, no login. Returns flat Clay-ready JSON. Read-only; requires an APIFY_TOKEN and consumes Apify credits per domain analyzed.

NameTypeReqDescription
check_pricingboolean–Fetch and score the pricing page. Default true. Setting this false is faster but caps the result at 'deployed', because 'commercialized' can only be proven on a pricing page.
domainstring–A single company domain, e.g. intercom.com. Provide either domain or domains.
domainsarray–Batch mode: several company domains analyzed in one call. Takes precedence over domain.
skipCacheboolean–Force a fresh analysis and ignore the 7 day result cache.

No output schema declared.

No examples provided.