SpiderIQ Media MCP — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to SpiderMedia file and per-tenant catalog tools: Do media mutations remain separate from read-only catalog access and correctly report selected tenant?

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

Best fit

Inspect a tenant media catalog and associated video/file metadata.

What we know

SpiderIQ Media: SpiderMedia files, videos, per-tenant media catalog Exact operational authority remains unverified from first-party package documentation and must not be inferred. Source-derived feature labels are preliminary; obtain official runtime/tool evidence before applying uncertain fields.

Maintenance / activity evidence

@spideriq/mcp-media 1.3.0 published 2026-09-04T12:28:02.171Z

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

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Permissions not yet verified. Complete write authority is not verified.
Authentication not yet verified.
Sensitive access: Tenant media metadata

Authority is not fully established. Do not treat unknown writes/auth as read-only or absent.

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

All limitations / Review context

Do media mutations remain separate from read-only catalog access and correctly report selected tenant?

The bounded review of the publisher's documented SpiderMedia file and per-tenant catalog 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.

Authority is not fully established. Do not treat unknown writes/auth as read-only or absent.
Sensitive access: Tenant media metadata
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.
repositoryIdentity: no confirmed package-to-repository binding
authentication: exact official auth and credential handling
writeActions: exact exposed tool mutation authority
dataHandling: provider destinations, retention and egress
cost: plans, pay-per-call charges, and payment authorization details
transport and actual executable entry point
Tenant scope and service retention require vendor verification
No upload/delete authority is established from the source roster
Do not apply unverified auth, permissions, transport, lifecycle or write actions; preserve any better existing profile values.

Original activity observations

@spideriq/mcp-media 1.3.0 published 2026-09-04T12:28:02.171Z

Technical identity

npm/@spideriq/mcp-media

Exact implementation source: https://www.npmjs.com/package/@spideriq/mcp-media ↗
Reviewed resource type: MCP Server
Package identity: npm:@spideriq/mcp-media

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 ↗
@spideriq/mcp-media
Recorded package identity, distribution or download evidence.
Includes references whose attribution is not established.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Install / connect
Publisher instructions
Private registry (`npm_config_registry=https://npm.spideriq.ai`) and tenant-specific MCP config.
Configure / authenticate
MCP100 setup guide
SpiderMedia shared auth tools include get_auth_status, health_check, logout, list_workspaces. Use health_check/get_auth_status for read-only verification, not media mutations.
Check connection
Suggested check
Publisher tools `health_check`, `get_auth_status`, `list_workspaces`; prefer health/auth status before any publishing or media action.
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.
Publisher documents `logout` among shared tools, and token saved in ~/.spideriq/credentials.json. This is local logout, not confirmed provider token revocation.

Official Documentation & Sources

What it does

SpiderIQ Media: SpiderMedia files, videos, per-tenant media catalog Exact operational authority remains unverified from first-party package documentation and must not be inferred. Source-derived feature labels are preliminary; obtain official runtime/tool evidence before applying uncertain fields.

Capability: Design & Creative
Resource type: MCP Server
Best fit: Inspect a tenant media catalog and associated video/file metadata.

Representative uses

List and inspect tenant media records
Look up stored files and video metadata

Limitations

Tenant scope and service retention require vendor verification
No upload/delete authority is established from the source roster
Do not apply unverified auth, permissions, transport, lifecycle or write actions; preserve any better existing profile values.

Reviewed access

Access & risk

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

Authentication: Not documented in the reviewed sources
Permissions: Not documented in the reviewed sources
Data handling: Not documented in the reviewed sources
Cost: Not documented in the reviewed sources
Risk and cautions: Authority is not fully established. Do not treat unknown writes/auth as read-only or absent.

Access scope and cautions

Write actions: Not verified
Sensitive access: Tenant media metadata

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 available discovery description lists: List and inspect tenant media records; Look up stored files and video metadata. These descriptions do not establish a fully verified tool inventory.

Can it modify data or perform write operations?

Not verified. The available evidence does not establish the complete write authority.

What data-handling boundary should I consider?

Recorded sensitive-access context: Tenant media metadata.

What limitations and risks should I check before use?

Authority is not fully established. Do not treat unknown writes/auth as read-only or absent. Tenant scope and service retention require vendor verification. No upload/delete authority is established from the source roster. 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.