SpiderIQ Gate MCP — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to SpiderGate gateway inspection and model tools: Do pinned skill and server versions agree on client-alias tools without borrowing unrelated gateway slices?

Reviewed Oct 5, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

LLM gateway operations for completions, model catalog, usage and traces inside SpiderIQ tenancy.

What we know

Focused SpiderIQ MCP slice for SpiderGate, the LLM gateway layer. Public package metadata identifies completions/models/usage/traces as its scope, using the same workspace/tenant/auth model as the SpiderIQ suite.

Maintenance / activity evidence

@spideriq/mcp-gate 1.11.0 published 2026-09-04T12:25:50.038Z

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
LLM gateway invocation plus usage/trace read authority; routing/config writes may exist depending live slice. Reported action classes: Run billable model completions. Complete write authority is not verified.
SpiderIQ workspace credential.
Sensitive access: Prompts/responses, Usage/traces, Workspace credentials

Gateway can incur model spend and expose sensitive prompts; verify current tool list before allowing config changes.

Full authority, access and evidence limits are available in Review context and Access & risk.

All limitations / Review context

Do pinned skill and server versions agree on client-alias tools without borrowing unrelated gateway slices?

The bounded review of the publisher's documented SpiderGate gateway inspection and model tools and release notices identified no disclosed material condition preventing an accurately scoped public tracking entry. The resource's operational permissions remain uncertainty; this assessment does not certify installation safety.

Gateway can incur model spend and expose sensitive prompts; verify current tool list before allowing config changes.
LLM gateway invocation plus usage/trace read authority; routing/config writes may exist depending live slice.
SpiderIQ workspace credential.
Prompts/responses/usage/traces pass through SpiderGate.
Reviewed write actions: Run billable model completions
Sensitive access: Prompts/responses, Usage/traces, Workspace credentials
Complete write authority is not verified.
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited.
Documented tool authority and any remote data handling must be checked before installation or use.
Tool inventory, client matrix and permissions completeness were not requirements for this Radar tracking review.
exact current tool inventory/write-config surface
Exact provider-routing/write controls should be read from the live package/tool list.
Workspace selection matters in multi-client/agency setups.
Gateway calls can incur upstream model costs and expose prompts/responses.

Original activity observations

@spideriq/mcp-gate 1.11.0 published 2026-09-04T12:25:50.038Z

Technical identity

npm/@spideriq/mcp-gate

Exact implementation source: https://www.npmjs.com/package/@spideriq/mcp-gate ↗
Reviewed resource type: Gateway
Repository identity: SpiderIQ/SpiderIQ
Package identity: npm:@spideriq/mcp-gate

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 5, 2026 · Latest source observation Oct 8, 2026

Package registry metadata ↗
@spideriq/mcp-gate
Recorded package identity, distribution or download evidence.
Evidence source ↗
www.npmjs.com/~martinshein
Source material retained for this review.
Includes references whose attribution is not established.

Setup · Watchlist

Gateway setup

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Install / connect gateway
Publisher instructions
SpiderIQ private registry `https://npm.spideriq.ai` and tenant credentials; follow publisher supplied client config; global install explicitly warned against.
Configure / authenticate
MCP100 setup guide
SpiderGate publisher forbids global npm install because it can override the pinned client package. Remove stale global `@spideriq/mcp-gate` only if confirmed installed, not as an automatic operation.
Check connection
Suggested check
User-side suggested check (not executed): inspect registered tools/connection and perform publisher-supported read-only status/list operations. Do not send, purchase, publish, delete, sign, trade or alter data as a smoke test.
Remove / uninstall / revoke
MCP100 setup guide
Generic client guidance (not publisher-specific uninstall): unregister MCP entry in the chosen client. If installed globally, remove the npm package separately. Revoke provider access separately through account controls, where supported. This does not erase local data or revoke funds/credentials automatically.
Unregister the named MCP entry from the actual host separately from removing a global npm install; no claim that either revokes remote credentials.
Remove local stored keys/tokens and revoke or rotate corresponding provider authorization using documented provider account controls if available; exact procedure not verified for this package. Wallet private keys cannot be revoked.

Official Documentation & Sources

What it does

Focused SpiderIQ MCP slice for SpiderGate, the LLM gateway layer. Public package metadata identifies completions/models/usage/traces as its scope, using the same workspace/tenant/auth model as the SpiderIQ suite.

Capability: AI & Reasoning
Resource type: Gateway
Best fit: LLM gateway operations for completions, model catalog, usage and traces inside SpiderIQ tenancy.

Representative uses

Run gateway completions
List models
Inspect usage
Inspect traces
Check auth/workspace status

Limitations

Exact provider-routing/write controls should be read from the live package/tool list.
Workspace selection matters in multi-client/agency setups.
Gateway calls can incur upstream model costs and expose prompts/responses.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: SpiderIQ workspace credential.
Permissions: LLM gateway invocation plus usage/trace read authority; routing/config writes may exist depending live slice.
Data handling: Prompts/responses/usage/traces pass through SpiderGate.
Cost: usage_based
Risk and cautions: Gateway can incur model spend and expose sensitive prompts; verify current tool list before allowing config changes.

Access scope and cautions

Write actions: Not verified Run billable model completions
Sensitive access: Prompts/responses Usage/traces Workspace credentials
Risk level: high

The reviewed evidence does not establish the complete write authority of this MCP. Consult the unresolved evidence before granting write access.

FAQ

Based on reviewed evidence as of 2026-10-08. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Run gateway completions; List models; Inspect usage; Inspect traces; Check auth/workspace status.

What setup and authentication are documented?

Recorded installation/entrypoint step: npx -y @spideriq/mcp-gate. Recorded transport: stdio. Recorded environment-variable notes: SPIDERIQ_WORKSPACE; npm_config_registry=https://npm.spideriq.ai (private registry path where required). No configuration values are supplied here. Prerequisites: SpiderIQ account/workspace. These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: SpiderIQ workspace/PAT credential system.

Can it modify data or perform write operations?

Not verified. The available evidence does not establish the complete write authority. The partial inventory lists: Run billable model completions. Recorded permission context: LLM gateway invocation plus usage/trace read authority; routing/config writes may exist depending live slice.

What data-handling boundary should I consider?

Prompts/responses/usage/traces pass through SpiderGate. Recorded sensitive-access context: Prompts/responses; Usage/traces; Workspace credentials.

What limitations and risks should I check before use?

Gateway can incur model spend and expose sensitive prompts; verify current tool list before allowing config changes. Exact provider-routing/write controls should be read from the live package/tool list. Workspace selection matters in multi-client/agency setups. Gateway calls can incur upstream model costs and expose prompts/responses. Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited. Documented tool authority and any remote data handling must be checked before installation or use.

What cost model is recorded?

The reviewed cost model is usage based. This classification does not establish current prices, quotas or the cost of every downstream operation. Check the applicable service terms before authorizing paid actions.