ai.spideriq/gate
NPM · @SPIDERIQ/MCP-GATE · SCANNED SEP 25
SpiderIQ Gate: SpiderGate LLM gateway (completions, models, usage, traces)
Available components
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
- 32 of 101 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 20 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability74
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1380 tokens (~72/item across 19 items; 19 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
- Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "logout" implies "remove" 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 19 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
How do I install the ai.spideriq/gate MCP server?
ai.spideriq/gate runs locally as an npm package, launched with npx -y @spideriq/mcp-gate. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @spideriq/mcp-gate
claude mcp add ai-spideriq-gate -- npx -y @spideriq/mcp-gate
{
"mcpServers": {
"ai-spideriq-gate": {
"command": "npx",
"args": [
"-y",
"@spideriq/mcp-gate"
]
}
}
} {
"servers": {
"ai-spideriq-gate": {
"command": "npx",
"args": [
"-y",
"@spideriq/mcp-gate"
]
}
}
} codex mcp add ai-spideriq-gate -- npx -y @spideriq/mcp-gate
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-spideriq-gate": {
"type": "local",
"command": [
"npx",
"-y",
"@spideriq/mcp-gate"
],
"enabled": true
}
}
} openclaw mcp add ai-spideriq-gate --command npx --arg -y --arg @spideriq/mcp-gate
mcp_servers:
ai-spideriq-gate:
command: "npx"
args: ["-y", "@spideriq/mcp-gate"] {
"McpServers": {
"ai-spideriq-gate": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@spideriq/mcp-gate"
]
}
}
} assistant mcp add ai-spideriq-gate -t stdio -c npx -a -y @spideriq/mcp-gate
{
"mcpServers": {
"ai-spideriq-gate": {
"command": "npx",
"args": [
"-y",
"@spideriq/mcp-gate"
]
}
}
} 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 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Sept 26 −3
- Stability: pass → 0.80 functional
- 21 Sept 26 0
- Stability: 0.97 → pass security
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 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 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −2
- Stability: pass → 0.83 functional
- 15 Sept 26 0
- Stability: 0.97 → pass security
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/@spideriq/mcp-gate@1.3.0
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 101 packages
| Packages resolved | 101 |
|---|---|
| Stale | 31 |
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
check_access_status ~152
Check the status of a PAT access request. Returns 'pending', 'active', 'denied', 'expired', or 'revoked' (matches the backend PATRequestStatus enum). Once status==='active', the token is saved to ~/.spideriq/credentials.json automatically. Multi-brand approvals save one entry per workspace under client_id, with the first aliased as 'default' so existing tools (upload_local_file, etc.) keep working without --workspace.
| Name | Type | Req | Description |
|---|---|---|---|
| api_url | string | – | API URL (default: https://spideriq.ai) |
| poll_token | string | yes | Poll token from request_access |
| request_id | string | yes | Request ID from request_access |
No output schema declared.
No examples provided.
gate_agents ~43
List your brand's agent tokens with budgets, rate limits, and model access.
| Name | Type | Req | Description |
|---|---|---|---|
| brand_id | string | yes | Brand ID |
| workspace | string | – | Workspace name |
No output schema declared.
No examples provided.
gate_aliases ~42
List SpiderGate task aliases (spideriq/fast, spideriq/coding, etc.) with their model chains.
| Name | Type | Req | Description |
|---|---|---|---|
| workspace | string | – | Workspace name |
No output schema declared.
No examples provided.
gate_chat ~411
Send a chat completion via SpiderGate LLM gateway (OpenAI-compatible). Use task aliases like "spideriq/fast", "spideriq/coding", "spideriq/research" or specific model IDs. Supports JSON mode (response_format), tool/function calling (tools/tool_choice), and SpiderGate extras via spidergate_options — { max_cost_usd } caps the per-request spend, { cache_enabled } caches identical prompts, { fallback_models } extends the alias chain. The response carries spidergate_metadata.cost_usd (the real per-call dollar cost) and provider_model (what actually served). NEVER send client PII on a free-tier alias (spideriq/fast,/free,/extraction) — use spideriq/lead-analysis.
| Name | Type | Req | Description |
|---|---|---|---|
| max_tokens | number | – | Max tokens to generate. |
| messages | array | yes | Chat messages |
| model | string | yes | Model or task alias (e.g., "spideriq/fast", "spideriq/coding") |
| response_format | object | – | Structured output: {"type":"json_object"} or {"type":"json_schema","json_schema":{...}}. |
| seed | number | – | Random seed for reproducibility. |
| spidergate_options | object | – | SpiderGate extras: { max_cost_usd, cache_enabled, cache_ttl_seconds, fallback_models, preferred_providers, excluded_providers, timeout_ms, retry_count }. |
| stop | – | – | Stop sequence(s) — a string or array of strings. |
| temperature | number | – | Sampling temperature 0.0–2.0 (default 1.0). |
| tool_choice | – | – | "none" | "auto" | "required" | {type:"function",function:{name}}. |
| tools | array | – | OpenAI tool/function definitions for tool calling. |
| top_p | number | – | Nucleus sampling 0.0–1.0. |
| workspace | string | – | Workspace name |
No output schema declared.
No examples provided.
gate_health ~25
Check SpiderGate LLM gateway health.
| Name | Type | Req | Description |
|---|---|---|---|
| workspace | string | – | Workspace name |
No output schema declared.
No examples provided.
gate_models ~30
List all available LLM models on SpiderGate with usage stats.
| Name | Type | Req | Description |
|---|---|---|---|
| workspace | string | – | Workspace name |
No output schema declared.
No examples provided.
gate_providers ~38
List available LLM providers with logos and descriptions.
| Name | Type | Req | Description |
|---|---|---|---|
| brand_id | string | yes | Brand ID |
| workspace | string | – | Workspace name |
No output schema declared.
No examples provided.
gate_stats ~43
Get your brand's SpiderGate overview — active agents, total requests, spend.
| Name | Type | Req | Description |
|---|---|---|---|
| brand_id | string | yes | Brand ID |
| workspace | string | – | Workspace name |
No output schema declared.
No examples provided.
gate_trace_detail ~52
Get full trace detail with spans, input/output messages, and timing.
| Name | Type | Req | Description |
|---|---|---|---|
| brand_id | string | yes | Brand ID |
| trace_id | string | yes | Trace ID |
| workspace | string | – | Workspace name |
No output schema declared.
No examples provided.
gate_trace_stats ~46
Get aggregated trace statistics — total traces, success/error counts, p95 latency, cost.
| Name | Type | Req | Description |
|---|---|---|---|
| brand_id | string | yes | Brand ID |
| workspace | string | – | Workspace name |
No output schema declared.
No examples provided.
gate_traces ~104
List LLM request traces for your brand — filter by agent, model, status, date.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | – | Filter by agent ID |
| brand_id | string | yes | Brand ID |
| limit | number | – | Max results (default: 20) |
| model | string | – | Filter by model name |
| offset | number | – | Offset for pagination |
| status | string | – | Filter by status |
| workspace | string | – | Workspace name |
No output schema declared.
No examples provided.
gate_usage ~65
Get your brand's usage analytics — requests, tokens, cost by model/provider/day.
| Name | Type | Req | Description |
|---|---|---|---|
| brand_id | string | yes | Brand ID |
| days | number | – | Time window in days (default: 7, max: 90) |
| workspace | string | – | Workspace name |
No output schema declared.
No examples provided.
get_api_info ~33
Get information about the SpiderIQ API and your connection.
| Name | Type | Req | Description |
|---|---|---|---|
| workspace | string | – | Workspace name (default: default) |
No output schema declared.
No examples provided.
get_auth_status ~33
Check if you are authenticated and get current user info.
| Name | Type | Req | Description |
|---|---|---|---|
| workspace | string | – | Workspace name (default: default) |
No output schema declared.
No examples provided.
get_queue_stats ~48
Get statistics about job queues (pending jobs, consumers, etc.).
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | Response format (default: json) |
| workspace | string | – | Workspace name (default: default) |
No output schema declared.
No examples provided.
health_check ~51
Check if the SpiderIQ API is healthy and responsive.
| Name | Type | Req | Description |
|---|---|---|---|
| api_url | string | – | API URL (default: https://spideriq.ai) |
| workspace | string | – | Workspace name (default: default) |
No output schema declared.
No examples provided.
list_workspaces ~19
List all configured workspaces and their authentication status.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
logout ~25
Remove stored authentication credentials.
| Name | Type | Req | Description |
|---|---|---|---|
| workspace | string | – | Workspace name (default: default) |
No output schema declared.
No examples provided.
request_access ~120
Request access to SpiderIQ API. This sends an approval email to the admin. After calling this, use check_access_status to poll for approval. Once approved, the token is automatically saved for subsequent API calls.
| Name | Type | Req | Description |
|---|---|---|---|
| api_url | string | – | API URL (default: https://spideriq.ai) |
| string | yes | Admin email address (the person who will approve access) | |
| project | string | – | Project name (shown in approval email) |
| scopes | array | – | Requested permission scopes (default: jobs:submit, jobs:read) |
No output schema declared.
No examples provided.
What is the ai.spideriq/gate MCP server?
ai.spideriq/gate is an MCP server listed in the public MCP registry as ai.spideriq/gate. SpiderIQ Gate: SpiderGate LLM gateway (completions, models, usage, traces). This page covers its npm package (@spideriq/mcp-gate).
Is the ai.spideriq/gate MCP server safe to use?
ai.spideriq/gate scores 76 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 ai.spideriq/gate MCP server expose?
ai.spideriq/gate exposes 19 tools: request_access, check_access_status, get_auth_status, logout, list_workspaces, and 14 more. Their descriptions and schemas cost roughly 1,380 tokens of context every time the server is loaded.
Is the ai.spideriq/gate MCP server still maintained?
ai.spideriq/gate 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 ai.spideriq/gate MCP server under?
ai.spideriq/gate declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.