# ideaudit (npm · @inite/ideaudit-tools)

The scoring behind an audit allowed to say no. Twenty deterministic tools, offline, no account.

- Trust score: 73/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-25

## Components

- remote · `api.inite.studio`: 67/100, [markdown](https://verifymcp.io/servers/studio-inite-ideaudit-tools/api.md), [page](https://verifymcp.io/servers/studio-inite-ideaudit-tools/api)
- npm · `@inite/ideaudit-tools`: 73/100 (this document), [markdown](https://verifymcp.io/servers/studio-inite-ideaudit-tools/inite-ideaudit-tools.md), [page](https://verifymcp.io/servers/studio-inite-ideaudit-tools/inite-ideaudit-tools)

## Channel facts

- Registry: `npm`
- Package: `@inite/ideaudit-tools`
- Version: `1.0.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-25.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 31 of 95 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (Apache-2.0).
  - Actively maintained (last published 19 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 65/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 2371 tokens (~118/item across 20 items; 20 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 63/100
  - Stability observed for 19 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 73/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 18% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "derive_kill_criteria" implies "kill" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 20 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the ideaudit MCP server?

ideaudit runs locally as an npm package, launched with npx -y @inite/ideaudit-tools. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add studio-inite-ideaudit-tools -- npx -y @inite/ideaudit-tools
```

### Cursor

```json
{
  "mcpServers": {
    "studio-inite-ideaudit-tools": {
      "command": "npx",
      "args": [
        "-y",
        "@inite/ideaudit-tools"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "studio-inite-ideaudit-tools": {
      "command": "npx",
      "args": [
        "-y",
        "@inite/ideaudit-tools"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add studio-inite-ideaudit-tools -- npx -y @inite/ideaudit-tools
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "studio-inite-ideaudit-tools": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@inite/ideaudit-tools"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add studio-inite-ideaudit-tools --command npx --arg -y --arg @inite/ideaudit-tools
```

### Hermes

```yaml
mcp_servers:
  studio-inite-ideaudit-tools:
    command: "npx"
    args: ["-y", "@inite/ideaudit-tools"]
```

### Netclaw

```json
{
  "McpServers": {
    "studio-inite-ideaudit-tools": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@inite/ideaudit-tools"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add studio-inite-ideaudit-tools -t stdio -c npx -a -y @inite/ideaudit-tools
```

### Other

```json
{
  "mcpServers": {
    "studio-inite-ideaudit-tools": {
      "command": "npx",
      "args": [
        "-y",
        "@inite/ideaudit-tools"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-25 (score 73, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-24 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-22 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-20 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-17 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-15 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-13 (score 68, +4)

- [functional improvement] Stability: unverified → 0.23

### 2026-09-06 (score 64)

First indexed and scored.

## MCP tools (20)

### `compute_barrier` (~70 tokens)

Compute barrier_score (0-24) + label (PRISTINE/OPEN/COMPETITIVE/CROWDED) from competitor counts + SERP noise fraction.

Input parameters:

- `adjacentCompetitorCount` (integer)
- `directCompetitorCount` (integer, required)
- `serpNoise` (number)

### `compute_budget_proof` (~90 tokens)

Compute budget_proof_score (0-10) + label (STRONG/CONFIRMED/WEAK/ABSENT) + purchase_intent_pct from pricing hits + review-site hits + intent mentions.

Input parameters:

- `hasNamedPricing` (boolean)
- `pricingHitsCount` (integer, required)
- `purchaseIntentMentions` (integer)
- `reviewSiteHitsCount` (integer)

### `compute_build_complexity` (~79 tokens)

Compute build_complexity_penalty (0-10, higher = worse) + per-factor breakdown. Hard tags: ml/realtime/blockchain/hardware/compliance/custom-ai/regulated/on-device-ai/iot.

Input parameters:

- `externalApisCount` (integer, required)
- `integrationsCount` (integer)
- `stackComplexityTags` (array)

### `compute_collection_scores` (~61 tokens)

Compute 12 deterministic collection scores (0-100) + badges + death reason for an enriched idea. Pure math. No external calls.

Input parameters:

- `analysisId` (string, required)
- `enrichedData` (object, required): EnrichedData with canonical_idea signals.

### `compute_crossed_matrix` (~184 tokens)

Crossed-product audit explorer. Same input as compute_dealbreakers_v2 — returns substrate verdict (no-observer baseline) + crossed verdict (when observer supplied) + a 5-row matrix of {solo, cofounded_technical, cofounded_business, domain_expert, serial} archetype verdicts. Never persists; meant for the dashboard "view as [archetype]" dropdown and for previewing a verdict before committing to it.

Input parameters:

- `hasMajorContradiction` (boolean)
- `lensScores` (array, required)
- `observer` (object): Founder profile that crosses with the substrate idea to produce an observer-relative verdict. When omitted, only the substrate verdict is returned.
- `sector` (string)
- `stage` (string, required)
- `stageProbabilities` (object)
- `unresolvedContradictions` (integer)

### `compute_dealbreakers_v2` (~200 tokens)

Methodology v2 dealbreakers — stage-aware weights + confidence-weighted lens scoring + risk-asymmetric verdict (GO requires score≥80 AND zero red flags AND avg confidence≥0.6). Optional `observer` triggers the crossed-product pipeline: substrate verdict (no-observer baseline) PLUS crossed verdict (observer-perturbed weights, risk-tolerance shifted thresholds) PLUS 5-row archetype matrix. The KILL gate (≥2 blockers / score<50) is observer-invariant — fatal stays fatal.

Input parameters:

- `hasMajorContradiction` (boolean)
- `lensScores` (array, required)
- `observer` (object): Founder profile that crosses with the substrate idea to produce an observer-relative verdict. When omitted, only the substrate verdict is returned.
- `sector` (string)
- `stage` (string, required)
- `stageProbabilities` (object)
- `unresolvedContradictions` (integer)

### `compute_funding_momentum` (~62 tokens)

Compute funding_momentum_score (0-10) + badge (HOT/WARM/COOL/COLD) from tier-weighted funding-article hit counts.

Input parameters:

- `hitsByTier` (object, required)
- `recent30dHits` (integer)

### `compute_hiring_demand` (~47 tokens)

Compute hiring_demand_score (0-10) from priority-weighted ATS site hit counts (use registries/hiring-sources for priorities).

Input parameters:

- `sites` (array, required)

### `compute_lrs_composite_v2` (~256 tokens)

LRS composite v2 — 6 components (SV, Pain, Barrier, Monet, X-Signal, Budget-Proof). Default Python weights 0.18/0.22/0.18/0.14/0.18/0.10 sum=1.0. Returns BOTH weighted score and equal-weight baseline (per OECD Handbook + Greco 2018 — equal-weight is defensible default when no outcome calibration exists). buildComplexityPenalty 0-10 subtracted from score. sectorProfile (ai_native/creator/crypto) opt-in reshuffles SV→0.16, X→0.20. Labels: THE_ROAR (≥80) / PROMISING (≥60) / EXPERIMENTAL (≥40) / WEAK_SIGNAL (<40).

Input parameters:

- `barrierScore` (number, required)
- `budgetProofScore` (number, required)
- `buildComplexityPenalty` (number)
- `monetizationScore` (number, required)
- `searchVelocityScore` (number, required)
- `sectorProfile` (string): Opt-in sector weight override. Default uses Python canonical weights.
- `socialPainScore` (number, required)
- `xSignalScore` (number, required)

### `compute_lrs_composite` (~113 tokens)

Compose lrs_final_100 (0-100) + label (WEAK/EMERGING/GOOD/STRONG/ELITE) + leaderboard_eligible flag + sub-percent breakdown. Weights: sv 0.25, sp 0.30, barrier 0.25, monetization 0.20.

Input parameters:

- `barrierScore` (number, required)
- `monetizationScore` (number, required)
- `searchVelocityScore` (number, required)
- `socialPainScore` (number, required)

### `compute_monetization` (~83 tokens)

Compute monetization_score (0-21) + label + has_pricing_anchors from pricing anchors + model tags + deal cycle hint.

Input parameters:

- `dealCycle` (string): instant/days/weeks/months/quarters
- `modelTags` (array): e.g. ["subscription","usage","marketplace"]
- `pricingAnchorsCount` (integer, required)

### `compute_multi_source_tam` (~117 tokens)

Multi-source TAM consensus. Pass 2-3 sources of market-size text. Optional `estimateYear` per source — when supplied, the result includes yearRange and a hasStaleData flag (true if the span exceeds 5 years). Outliers are dropped by modified Z-score over the median absolute deviation when n≥4. Returns the extracted dollar amounts + consensus median + an agreement score 0..1, where 1 means every source lands within 20% of the median.

Input parameters:

- `inputs` (array, required)

### `compute_ppc_spend_signal` (~118 tokens)

Wave 5 N.4 — compute ppc_spend_score (0-10) + label (STRONG/CONFIRMED/WEAK/ABSENT) + market_saturation from PPC traffic projection (avgCpcUsd, totalMonthlySpendUsd, optional competitorBidders + competition). Feed numbers from dataforseo_ad_traffic.

Input parameters:

- `avgCpcUsd` (number, required)
- `competition` (number)
- `competitorBidders` (integer)
- `totalMonthlySpendUsd` (number, required)

### `compute_search_velocity_v2` (~270 tokens)

Search velocity (0-25) v2 — canonical 0.40*volume + 0.30*trend + 0.20*intent + 0.10*geo. CRITICAL: externalVolumeNorm MUST come from external sources (Amazon BSR / app store installs / job-board postings) — NOT the Trends timeline (would double-count, since Trends is itself normalized 0-100 within window). trendNorm is derived internally from trendsTimelineValues. Trends peak<50 zeroes the trend component (Yotpo SEO floor). Optional daysSinceLastSignal applies exponential freshness decay (search half-life 90d).

Input parameters:

- `daysSinceLastSignal` (number): Optional: days since most recent confirming signal. Triggers exponential freshness decay (half-life 90d).
- `externalVolumeNorm` (number, required): Normalized 0-1 demand volume from EXTERNAL sources (Amazon, app stores, jobs). Caller normalizes before passing.
- `geoSpreadNorm` (number, required): 0-1 geographic spread (regions with interest > threshold).
- `intentNorm` (number, required): 0-1 commercial/transactional intent ratio.
- `trendsTimelineValues` (array, required): Monthly Trends values 0-100. Used ONLY to derive trendNorm — never as raw volume.

### `compute_search_velocity` (~74 tokens)

Compute search_velocity_score (0-25) from Trends timeline values + rising queries count + geo region count.

Input parameters:

- `geoRegionCount` (integer)
- `risingQueriesCount` (integer)
- `timelineValues` (array, required): Monthly Trends values 0-100 (e.g. last 10-12 months).

### `compute_social_pain` (~70 tokens)

Compute social_pain_score (0-30) + total mentions + dominant perspective (business/consumer/trend/mixed).

Input parameters:

- `categoryCounts` (object)
- `intentMentions` (integer)
- `painMentions` (integer, required)
- `urgencyMentions` (integer)

### `compute_urgency_composite` (~80 tokens)

Compose composite_urgency_score (0-10) + badge (LOW/MEDIUM/HIGH/VERY_HIGH/EXTREME) from 3 sub-scores: news, pain, hiring.

Input parameters:

- `hiringSignalScore` (number, required)
- `newsSignalScore` (number, required)
- `painSignalScore` (number, required)

### `compute_x_signal` (~75 tokens)

Compute x_signal_score (0-20) + recency share + positivity rate from X/Twitter mention counts.

Input parameters:

- `founderMentions` (integer)
- `mentionsCount` (integer, required)
- `recent7dCount` (integer)
- `sentimentNegative` (integer)
- `sentimentPositive` (integer)

### `derive_kill_criteria` (~139 tokens)

Derive a falsifiable, data-driven list of kill criteria from upstream signals — the outputs of validate_unit_economics and compute_dealbreakers_v2, plus an ICP drift count. Returns one row per rule with {rule, threshold, status, evidence?}, where status is tripped_now / monitor / cleared. Replaces prose kill criteria, which are tautologies that can never fire.

Input parameters:

- `dealbreakers` (object): The result of compute_dealbreakers_v2.
- `icpDriftCount` (integer)
- `unitEcon` (object): The result of validate_unit_economics.

### `validate_unit_economics` (~183 tokens)

Sanity-check a unit-economics row before publishing it in a business-model slide. Catches the math-drift class of failures (customers × ARPU ≠ revenue), enforces the LTV/CAC ≥ 1.5 floor, the cohort-positivity check, and CAC payback bounds. Returns {ok, errors[{rule, severity, detail}], derived{ratios}}. Skills MUST regenerate the row when ok=false (block-severity errors); warn-severity errors should be surfaced in the final report but do not gate publication. No LLM calls.

Input parameters:

- `annualRevenue` (number, required)
- `arpu` (number, required)
- `cac` (number)
- `customers` (number, required)
- `grossMargin` (number)
- `ltv` (number)
- `monthlyChurn` (number)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/studio-inite-ideaudit-tools/inite-ideaudit-tools#diagnostics

## Score history

- 2026-09-25: 73
- 2026-09-24: 73
- 2026-09-23: 72
- 2026-09-22: 72
- 2026-09-21: 71
- 2026-09-20: 71
- 2026-09-19: 70
- 2026-09-18: 70
- 2026-09-17: 70
- 2026-09-16: 69
- 2026-09-15: 69
- 2026-09-14: 68
- 2026-09-13: 68
- 2026-09-12: 64
- 2026-09-11: 64
- 2026-09-10: 64
- 2026-09-09: 64
- 2026-09-08: 64
- 2026-09-07: 64
- 2026-09-06: 64

## Common questions

### What is the ideaudit MCP server?

ideaudit is an MCP server listed in the public MCP registry as studio.inite/ideaudit-tools. The scoring behind an audit allowed to say no. Twenty deterministic tools, offline, no account. This page covers its npm package (@inite/ideaudit-tools).

### Is the ideaudit MCP server safe to use?

ideaudit scores 73 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the ideaudit MCP server expose?

ideaudit exposes 20 tools: compute_barrier, compute_budget_proof, compute_build_complexity, compute_collection_scores, compute_crossed_matrix, and 15 more. Their descriptions and schemas cost roughly 2,371 tokens of context every time the server is loaded.

### Is the ideaudit MCP server still maintained?

ideaudit is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the ideaudit MCP server under?

ideaudit declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/@inite/ideaudit-tools
- Socket report: https://socket.dev/npm/package/@inite/ideaudit-tools
- Repository: https://github.com/inite-ai/ideaudit-mcp
- Website: https://inite.studio/
- Changelog RSS feed: https://verifymcp.io/servers/studio-inite-ideaudit-tools/inite-ideaudit-tools.xml
- Changelog JSON feed: https://verifymcp.io/servers/studio-inite-ideaudit-tools/inite-ideaudit-tools.json
- HTML version of this page: https://verifymcp.io/servers/studio-inite-ideaudit-tools/inite-ideaudit-tools