SpiderIQ Publish MCP — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to SpiderPublish content and domain tools: Do explicit workspace overrides remain visible in each response before content mutations target a tenant?

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

Best fit

CMS/content authoring, templates/components, domains, media and deployment for SpiderPublish.

What we know

Focused SpiderIQ content-platform MCP covering pages/posts/docs/categories/tags/navigation/settings, templates/themes, reusable components, domains, media and deploy/status operations. A curated under-128-tool slice exists for clients with tool-count ceilings.

Maintenance / activity evidence

@spideriq/mcp-publish 1.43.0 published 2026-09-04T12:25:37.257Z

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.
Broad CMS/site/domain/media read-write authority. Writes: Create/update/delete/publish content; Change templates/themes/settings; Add/delete/set-primary domains; Upload media; Deploy site.
SpiderIQ credential.
Sensitive access: Website content, Domains, Media assets, Tenant credentials

Can directly alter public websites and domains; use scoped workspace and review destructive operations.

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

All limitations / Review context

Do explicit workspace overrides remain visible in each response before content mutations target a tenant?

The bounded review of the publisher's documented SpiderPublish content and domain 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.

Can directly alter public websites and domains; use scoped workspace and review destructive operations.
Broad CMS/site/domain/media read-write authority.
SpiderIQ credential.
Site content/media/domain configuration is stored/processed by SpiderIQ.
Reviewed write actions: Create/update/delete/publish content; Change templates/themes/settings; Add/delete/set-primary domains; Upload media; Deploy site
Sensitive access: Website content, Domains, Media assets, Tenant credentials
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.
Broad CRUD/publishing surface can change public websites.
Tool surface is large and may be sliced by environment.
Tenant/workspace must be explicit in multi-client use.
Delete/unpublish/domain changes can be destructive.

Original activity observations

@spideriq/mcp-publish 1.43.0 published 2026-09-04T12:25:37.257Z

Technical identity

npm/@spideriq/mcp-publish

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

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-publish
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 publisher configuration.
Configure / authenticate
MCP100 setup guide
SpiderPublish shared auth tools include get_auth_status, health_check, logout, list_workspaces. Do not publish or change domain settings to check connectivity.
Check connection
Suggested check
Publisher tools `health_check`, `get_auth_status`, `list_workspaces`; avoid publishing and domain mutations in verification.
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` and ~/.spideriq/credentials.json; no verified server-side token revocation control.

Official Documentation & Sources

What it does

Focused SpiderIQ content-platform MCP covering pages/posts/docs/categories/tags/navigation/settings, templates/themes, reusable components, domains, media and deploy/status operations. A curated under-128-tool slice exists for clients with tool-count ceilings.

Capability: Productivity & Collaboration
Resource type: MCP Server
Industry: Media & Marketing
Best fit: CMS/content authoring, templates/components, domains, media and deployment for SpiderPublish.

Representative uses

Create/update/publish/unpublish pages/posts/docs
Manage templates/themes/components
Manage domains
Upload media
Deploy site

Limitations

Broad CRUD/publishing surface can change public websites.
Tool surface is large and may be sliced by environment.
Tenant/workspace must be explicit in multi-client use.
Delete/unpublish/domain changes can be destructive.

Reviewed access

Access & risk

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

Authentication: SpiderIQ credential.
Permissions: Broad CMS/site/domain/media read-write authority.
Data handling: Site content/media/domain configuration is stored/processed by SpiderIQ.
Cost: plan_based
Risk and cautions: Can directly alter public websites and domains; use scoped workspace and review destructive operations.

Access scope and cautions

Write actions: Create/update/delete/publish content Change templates/themes/settings Add/delete/set-primary domains Upload media Deploy site
Sensitive access: Website content Domains Media assets Tenant credentials
Risk level: high

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: Create/update/publish/unpublish pages/posts/docs; Manage templates/themes/components; Manage domains; Upload media; Deploy site.

What setup and authentication are documented?

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

Can it modify data or perform write operations?

Documented write actions include: Create/update/delete/publish content; Change templates/themes/settings; Add/delete/set-primary domains; Upload media; Deploy site. Recorded permission boundary: Broad CMS/site/domain/media read-write authority.

What data-handling boundary should I consider?

Site content/media/domain configuration is stored/processed by SpiderIQ. Recorded sensitive-access context: Website content; Domains; Media assets; Tenant credentials.

What limitations and risks should I check before use?

Can directly alter public websites and domains; use scoped workspace and review destructive operations. Broad CRUD/publishing surface can change public websites. Tool surface is large and may be sliced by environment. Tenant/workspace must be explicit in multi-client use. Delete/unpublish/domain changes can be destructive. 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 plan 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.