blume — Watchlist | MCP100 Index

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Recheck a specific changing behavior of npm/blume: Does the documentation MCP integration remain built-in and deployed with clear endpoint/auth boundaries?

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

Best fit

AI-ready documentation websites

What we know

Blume is a docs framework and describes an optional server mode for AI assistant/MCP access.

Maintenance / activity evidence

Blume package release blume@2.0.3 published 2026-09-25.

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

Activity source · releases ↗

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Documentation framework with opt-in read-only docs MCP; requires server-capable adapter; static export cannot host MCP. Reported action classes: Generate documentation and write framework project files when used as a framework; MCP docs endpoint is read-oriented. Complete write authority is not verified.
Authentication not yet verified.
Documentation framework with opt-in read-only docs MCP; requires server-capable adapter; static export cannot host MCP.

Documentation framework with opt-in read-only docs MCP; requires server-capable adapter; static export cannot host MCP.
Advisory/security review not completed; no safety badge.
Write action classes summarize access risk; tool-level completeness and exact operation names are not independently verified. Do not mark them as confirmed documented write inventory.
Unknown vulnerabilities and provider data handling are not certified by this public tracking review.

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

Popularity

· 414.8k package downloads / 30 days

Downloads observed Oct 9, 2026.

Exact npm package blume; provider interval 2026-09-08–2026-10-07 (inclusive); observed 2026-10-09.

All limitations / Review context

Does the documentation MCP integration remain built-in and deployed with clear endpoint/auth boundaries?

No identified material blocker to an accurately qualified public tracking entry in the limited cited evidence. This is not an installation safety certification; product-specific cautions must remain visible.

Documentation framework with opt-in read-only docs MCP; requires server-capable adapter; static export cannot host MCP.
Advisory/security review not completed; no safety badge.
Write action classes summarize access risk; tool-level completeness and exact operation names are not independently verified. Do not mark them as confirmed documented write inventory.
Reviewed write actions: Generate documentation and write framework project files when used as a framework; MCP docs endpoint is read-oriented
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.
Published documentation/agent endpoints can expose hosted content; this is primarily a docs framework with optional MCP functionality.
Unknown vulnerabilities and provider data handling are not certified by this public tracking review.
Release evidence proves attributable activity, not entire installation or tool-level safety.
Current Discovery source binding and atomic apply must be generated using MCP100 existing pipeline.
exact authentication contract
first-party data processing and retention
data retention and permission scope
repository ownership unverified; keep null
Write actions/tool inventory not confirmed against exact tool documentation; listed action classes remain illustrative or context-dependent. Empty inventory does not establish read-only.
MCP server is an optional feature; verify protocol tool identity before claiming MCP-core relevance.
This is not a standalone general-purpose MCP server; use the resource-type-specific setup and expectations.
Radar public tracking editorial review completed in limited scope; not a security or installation certification. Verify setup according to deployment mode and do not invent unresolved facts.

Original activity observations

Blume package release blume@2.0.3 published 2026-09-25.

Technical identity

npm/blume

Exact implementation source: https://www.npmjs.com/package/blume ↗
Reviewed resource type: Framework
Package identity: npm:blume

Evidence & Sources

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

Reviewed Oct 9, 2026 · Latest source observation Oct 9, 2026

GitHub repository ↗
haydenbleasel/blume
Recorded repository material and project history.
Evidence source ↗
useblume.dev/guides/mcp-server-for-documentation
Source material retained for this review.
Includes references whose attribution is not established.
Package registry ↗
blume
Recorded package identity, distribution or download evidence.
Includes references whose attribution is not established.

Setup · Watchlist

Framework setup

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Warning

Not runtime tested, no third-party installation, network authorization, paid calls, or mutation executed.
Do not claim production service is available based on README alone.
Documentation site generator/framework, not independently documented MCP stdio server
Targeted 2026-10-13 re-research: Documentation framework/CLI, not an independent MCP server; npx blume init sets up a project.
Documentation framework/CLI, not an independent MCP server; npx blume init sets up a project.
Official npm publisher package page README inspected for this exact npm identity; static research only. Some setup statements are conservatively summarized; no source code or live client execution checked. V2 review did not run any live client.
Avoid write, payment, token transfer, publishing, sending, booking and remote account changes as tests.
Blume documentation site framework; npx blume init scaffolds a project, not an MCP server registration.
Replace credential, action and registration placeholders; follow the matching publisher/client prerequisites. No execution performed.

Install framework / project integration
Publisher instructions
Documentation site generator/framework, not independently documented MCP stdio server | Publisher npm README revisited on 2026-10-14; exact identity retained.
Reviewed setup example · Publisher instructions
npx blume init
Configure / authenticate
MCP100 setup guide
Blume docs-site framework. Run `npm run dev` after scaffolding; it is not itself an MCP server.
Check connection
Suggested check
`npx blume doctor` checks docs project; there is no default standalone MCP connection.
Remove / uninstall / revoke
MCP100 setup guide
Remove the framework/library from the consuming application using its package manager and undo its generated integration configuration. This is NOT a client-registered standalone MCP server.

Official Documentation & Sources

What it does

Blume is a docs framework and describes an optional server mode for AI assistant/MCP access.

Capability: Developer Tools
Resource type: Framework
Best fit: AI-ready documentation websites

Representative uses

Static documentation framework
optional deployment adapter for MCP

Limitations

MCP server is an optional feature; verify protocol tool identity before claiming MCP-core relevance.
This is not a standalone general-purpose MCP server; use the resource-type-specific setup and expectations.
Radar public tracking editorial review completed in limited scope; not a security or installation certification. Verify setup according to deployment mode and do not invent unresolved facts.

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: Documentation framework with opt-in read-only docs MCP; requires server-capable adapter; static export cannot host MCP.
Data handling: Not documented in the reviewed sources
Cost: unknown
Risk and cautions: Documentation framework with opt-in read-only docs MCP; requires server-capable adapter; static export cannot host MCP.

Access scope and cautions

Write actions: Not verified Generate documentation and write framework project files when used as a framework; MCP docs endpoint is read-oriented
Risk level: moderate
Security notes: Advisory/security review not completed; no safety badge. Write action classes summarize access risk; tool-level completeness and exact operation names are not independently verified. Do not mark them as confirmed documented write inventory.

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-09. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Static documentation framework; optional deployment adapter for MCP.

What setup and authentication are documented?

A complete connection procedure is not verified. Client notes: Connect MCP client to deployed /mcp and confirm four read-only doc tools. These facts do not supply missing installation commands, credentials or a verified authentication procedure. Authentication: Deployment/framework dependent; cannot assume hosted auth.

Can it modify data or perform write operations?

Not verified. The available evidence does not establish the complete write authority. The partial inventory lists: Generate documentation and write framework project files when used as a framework; MCP docs endpoint is read-oriented. Recorded permission context: Documentation framework with opt-in read-only docs MCP; requires server-capable adapter; static export cannot host MCP.

What limitations and risks should I check before use?

Documentation framework with opt-in read-only docs MCP; requires server-capable adapter; static export cannot host MCP. MCP server is an optional feature; protocol tool identity requires verification. This is not a standalone general-purpose MCP server; use the resource-type-specific setup and expectations. Radar public tracking editorial review completed in limited scope; not a security or installation certification. Verify setup according to deployment mode. Advisory/security review not completed; no safety badge. Write action classes summarize access risk; tool-level completeness and exact operation names are not independently verified. Published documentation/agent endpoints can expose hosted content; this is primarily a docs framework with optional MCP functionality. Unknown vulnerabilities and provider data handling are not certified by this public tracking review.