Is the Inite Ideaudit Tools MCP server down?

mcp-registry/studio.inite/ideaudit-tools · v0.1.0

As of 2026-10-21 05:31 UTC, the Inite Ideaudit Tools MCP server is up with a Glimind reliability score of 92/100 (grade A). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 3 outages in 90 days, with a median recovery of 2 minutes.

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

claude mcp add --transport http inite-ideaudit-tools-mcp-server https://api.inite.studio/mcp

{
  "mcpServers": {
    "inite-ideaudit-tools-mcp-server": {
      "type": "http",
      "url": "https://api.inite.studio/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: C (71/100)

What to fix (3)

Auto-fix: 5 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 19 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fstudio.inite%2Fideaudit-tools/fixes

{
  "name": "compute_search_velocity",
  "description": "Compute search_velocity_score (0-25) from Trends timeline values + rising queries count + geo region count.",
  "inputSchema": {
    "type": "object",
    "required": [
      "timelineValues"
    ],
    "properties": {
      "geoRegionCount": {
        "type": "integer",
        "minimum": 0
      },
      "timelineValues": {
        "type": "array",
        "items": {
          "type": "number",
          "maximum": 100,
          "minimum": 0
        },
        "description": "Monthly Trends values 0-100 (e.g. last 10-12 months)."
      },
      "risingQueriesCount": {
        "type": "integer",
        "minimum": 0
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

{
  "name": "compute_search_velocity_v2",
  "description": "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",
  "inputSchema": {
    "type": "object",
    "required": [
      "trendsTimelineValues",
      "externalVolumeNorm",
      "intentNorm",
      "geoSpreadNorm"
    ],
    "properties": {
      "intentNorm": {
        "type": "number",
        "maximum": 1,
        "minimum": 0,
        "description": "0-1 commercial/transactional intent ratio."
      },
      "geoSpreadNorm": {
        "type": "number",
        "maximum": 1,
        "minimum": 0,
        "description": "0-1 geographic spread (regions with interest > threshold)."
      },
      "externalVolumeNorm": {
        "type": "number",
        "maximum": 1,
        "minimum": 0,
        "description": "Normalized 0-1 demand volume from EXTERNAL sources (Amazon, app stores, jobs). Caller normalizes before passing."
      },
      "daysSinceLastSignal": {
        "type": "number",
        "minimum": 0,
        "description": "Optional: days since most recent confirming signal. Triggers exponential freshness decay (half-life 90d)."
      },
      "trendsTimelineValues": {
        "type": "array",
        "items": {
          "type": "number",
          "maximum": 100,
          "minimum": 0
        },
        "description": "Monthly Trends values 0-100. Used ONLY to derive trendNorm — never as raw volume."
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

{
  "name": "derive_kill_criteria",
  "description": "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.",
  "inputSchema": {
    "type": "object",
    "required": [],
    "properties": {
      "unitEcon": {
        "type": "object",
        "description": "The result of validate_unit_economics."
      },
      "dealbreakers": {
        "type": "object",
        "description": "The result of compute_dealbreakers_v2."
      },
      "icpDriftCount": {
        "type": "integer",
        "minimum": 0
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": true,
    "idempotentHint": false
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/studio.inite/ideaudit-tools"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/studio.inite/ideaudit-tools"}) over MCP.

Passed

• Every tool has a well-formed, typed input schema.
• No tool-poisoning patterns (hidden characters, instruction overrides, concealment, secret access, tool shadowing).
• Compact tool list (~4,557 tokens).
• Tool names are unique and portable across clients.
• Speaks MCP 2025-06-18.
• 99.93% uptime over 30 days.
• No breaking contract changes in 30 days.

Largest tool definitions

• compute_dealbreakers_v2 ~632 tokens
• compute_crossed_matrix ~612 tokens
• compute_search_velocity_v2 ~414 tokens
• compute_lrs_composite_v2 ~369 tokens
• compute_multi_source_tam ~230 tokens

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fstudio.inite%2Fideaudit-tools.svg)](https://glimind.com/server/mcp-registry%2Fstudio.inite%2Fideaudit-tools?ref=badge)

<a href="https://glimind.com/server/mcp-registry%2Fstudio.inite%2Fideaudit-tools?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fstudio.inite%2Fideaudit-tools.svg" alt="MCP agent-readiness"></a>

.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fstudio.inite%2Fideaudit-tools.svg
   :target: https://glimind.com/server/mcp-registry%2Fstudio.inite%2Fideaudit-tools?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:461669706706e78a…, first seen 2026-10-17, included at leaf 8163 of 37,403. Version history · verify what your client received.

Tools (21)

• compute_barrier
• compute_budget_proof
• compute_build_complexity
• compute_collection_scores
• compute_crossed_matrix
• compute_dealbreakers_v2
• compute_funding_momentum
• compute_hiring_demand
• compute_lrs_composite
• compute_lrs_composite_v2
• compute_monetization
• compute_multi_source_tam
• compute_ppc_spend_signal
• compute_search_velocity
• compute_search_velocity_v2
• compute_social_pain
• compute_urgency_composite
• compute_x_signal
• derive_kill_criteria
• get_started
• validate_unit_economics

Compare: most reliable data servers · most reliable ml servers · most reliable knowledge servers

claude mcp add --transport http glimind https://glimind.com/mcp

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Inite Ideaudit Tools MCP server down right now?

As of 2026-10-21 05:31 UTC, the Inite Ideaudit Tools MCP server is up with a Glimind reliability score of 92/100 (grade A). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 3 outages in 90 days, with a median recovery of 2 minutes.

How many tools does Inite Ideaudit Tools MCP server provide?

Inite Ideaudit Tools MCP server advertises 21 tools, including compute_barrier, compute_budget_proof, compute_build_complexity, compute_collection_scores, compute_crossed_matrix.

How do I install Inite Ideaudit Tools MCP server?

Point your MCP client at this streamable-http endpoint: https://api.inite.studio/mcp

Is the Inite Ideaudit Tools MCP server safe to connect to an AI agent?

Glimind scanned all 21 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Inite Ideaudit Tools MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.