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.

BIGHUB

NPM · @BIGHUB/BIGHUB-MCP · SCANNED SEP 25

Decision learning for AI agent actions. Evaluate, score, decide, and learn from outcomes.

Available components

0 this week 75 Trust /100
Trust breakdown (7 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 → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability54
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 5931 tokens (~47/item across 125 items; 125 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
  • Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage75
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 11% of tool parameters carry a description.Partial
  • Structured output schemas are declared (64% of tools); any adoption earns full credit.Pass
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 8 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "bighub_constraints_delete" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 125 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the BIGHUB MCP server?

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

npm · @bighub/bighub-mcp

# add to Claude Code
claude mcp add io-bighub-mcp -- npx -y @bighub/bighub-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "io-bighub-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@bighub/bighub-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "io-bighub-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@bighub/bighub-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add io-bighub-mcp -- npx -y @bighub/bighub-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-bighub-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@bighub/bighub-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add io-bighub-mcp --command npx --arg -y --arg @bighub/bighub-mcp
# ~/.hermes/config.yaml
mcp_servers:
  io-bighub-mcp:
    command: "npx"
    args: ["-y", "@bighub/bighub-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "io-bighub-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@bighub/bighub-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add io-bighub-mcp -t stdio -c npx -a -y @bighub/bighub-mcp
// mcp.json
{
  "mcpServers": {
    "io-bighub-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@bighub/bighub-mcp"
      ]
    }
  }
}
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.

  • 25 Sept 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 23 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 22 Sept 26 +1
    • Stability: 0.97 → pass security
  • 20 Sept 26 +1

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

  • 18 Sept 26 +1

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

  • 16 Sept 26 −3
    • Security disclosure: unverified → fail ▼ functional
    • Stability: pass → 0.80 functional
  • 15 Sept 26 +1
    • Stability: 0.97 → pass security
  • 14 Sept 26 0
    • Security disclosure: fail → unverified ▼ functional
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 25 Sept 2026 · Analysed npm/@bighub/bighub-mcp@0.2.1

Provenance No attestation

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

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 95 packages
Packages resolved 95
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 125 exposed · ~5,931 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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
bighub_precedents_signals ~66

Get aggregated precedent signals for an action.

NameTypeReqDescription
actionstringyes–
actor_typestring––
axesobject––
domainstringyes–
risk_scorenumber––
toolstring––

Structured output declared, but exposes no named fields.

No examples provided.

bighub_precedents_stats ~18

Get precedent engine statistics.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

bighub_retrieval_compare ~120

Compare two retrieval strategies on the same query. Returns scored results, risk level, confidence, and stability for each strategy.

NameTypeReqDescription
actionstring––
actor_typestring––
axesobject–Risk axes as {axis_name: score}
domainstring––
intentstring––
risk_scorenumber––
strategy_astring–First strategy to compare
strategy_bstring–Second strategy to compare
toolstring––

Structured output declared, but exposes no named fields.

No examples provided.

bighub_retrieval_index_case ~90

Index a decision case into the retrieval engine.

NameTypeReqDescription
actionstringyes–
actor_typestring––
axesobject––
case_idstringyes–
domainstringyes–
org_idstringyes–
risk_scorenumber––
toolstringyes–
verdictstring––

Structured output declared, but exposes no named fields.

No examples provided.

bighub_retrieval_query ~87

Multi-signal decision retrieval: find relevant past cases for an upcoming action.

NameTypeReqDescription
actionstringyes–
actor_typestring––
axesobject––
domainstringyes–
risk_scorenumber––
strategystring––
strategy_namestring––
toolstring––

Structured output declared, but exposes no named fields.

No examples provided.

bighub_retrieval_query_explained ~82

Retrieval query with full scoring explanation.

NameTypeReqDescription
actionstringyes–
actor_typestring––
axesobject––
domainstringyes–
risk_scorenumber––
strategystring––
strategy_namestring––
toolstring––

Structured output declared, but exposes no named fields.

No examples provided.

bighub_retrieval_stats ~18

Get retrieval engine statistics.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

bighub_retrieval_strategies ~20

List available retrieval strategies.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

bighub_retrieval_strategy ~29

Get details of a retrieval strategy by name.

NameTypeReqDescription
namestringyes–

Structured output declared, but exposes no named fields.

No examples provided.

bighub_simulations_accuracy ~30

Simulation accuracy metrics.

NameTypeReqDescription
domainstring––
toolstring––

Structured output declared, but exposes no named fields.

No examples provided.

bighub_simulations_by_request ~30

Get simulation snapshot for a given request_id.

NameTypeReqDescription
request_idstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

bighub_simulations_compare ~30

Compare simulation prediction vs real outcome for a request.

NameTypeReqDescription
request_idstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

bighub_simulations_get ~27

Get a simulation snapshot by ID.

NameTypeReqDescription
snapshot_idstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

bighub_simulations_list ~47

List persisted simulation snapshots.

NameTypeReqDescription
domainstring––
limitinteger––
toolstring––
with_outcomeboolean––

Structured output declared, but exposes no named fields.

No examples provided.

bighub_simulations_stats ~17

Get simulation vault statistics.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

bighub_webhooks_create ~24

Create a webhook endpoint.

NameTypeReqDescription
payloadobjectyes–

No output schema declared.

No examples provided.

bighub_webhooks_delete ~24

Delete a webhook.

NameTypeReqDescription
webhook_idstringyes–

No output schema declared.

No examples provided.

bighub_webhooks_deliveries ~34

List webhook delivery logs.

NameTypeReqDescription
limitinteger––
webhook_idstringyes–

No output schema declared.

No examples provided.

bighub_webhooks_get ~27

Get a webhook by webhook_id.

NameTypeReqDescription
webhook_idstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

bighub_webhooks_list ~25

List webhooks.

NameTypeReqDescription
include_inactiveboolean––

Structured output declared, but exposes no named fields.

No examples provided.

bighub_webhooks_list_events ~19

List supported webhook event types.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

bighub_webhooks_replay_failed_delivery ~37

Replay a failed webhook delivery.

NameTypeReqDescription
delivery_idintegeryes–
webhook_idstringyes–

No output schema declared.

No examples provided.

bighub_webhooks_test ~34

Send a test webhook delivery.

NameTypeReqDescription
event_typestring––
webhook_idstringyes–

No output schema declared.

No examples provided.

bighub_webhooks_update ~33

Update webhook by webhook_id.

NameTypeReqDescription
payloadobjectyes–
webhook_idstringyes–

No output schema declared.

No examples provided.

bighub_webhooks_verify_signature ~46

Verify webhook signature payload.

NameTypeReqDescription
payloadstringyes–
secretstringyes–
signaturestringyes–
timestampintegeryes–

No output schema declared.

No examples provided.

Common questions

What is the BIGHUB MCP server?

BIGHUB is an MCP server listed in the public MCP registry as io.bighub/mcp. Decision learning for AI agent actions. Evaluate, score, decide, and learn from outcomes. This page covers its npm package (@bighub/bighub-mcp).

Is the BIGHUB MCP server safe to use?

BIGHUB scores 75 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 BIGHUB MCP server expose?

BIGHUB exposes 125 tools: bighub_http_request, bighub_actions_evaluate, bighub_actions_evaluate_payload, bighub_actions_dry_run, bighub_actions_live_connect, and 120 more. Their descriptions and schemas cost roughly 5,931 tokens of context every time the server is loaded.

Is the BIGHUB MCP server still maintained?

BIGHUB 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 BIGHUB MCP server under?

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