Mason Context — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to Mason engineering-decision context and documentation audit tools: Do background updates preserve the installed context contracts and accurately distinguish configuration from observed usage?

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

Best fit

Maintaining codebase concept maps, decisions and change-impact context for coding agents.

What we know

MCP-only context-engineering server for feature-to-file concept maps, decision records, drift verification and optional wiki synchronization.

Maintenance / activity evidence

mason-context 0.20.2 published 2026-09-30T12:10:41.939Z

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.
Repository context and .mason metadata scope. Writes: Initialize/update concept maps; Save decisions; Update snapshot metadata.
Authentication not yet verified.
Sensitive access: Source-code structure, Technical decisions

Main risk is persistent repository knowledge exposure rather than arbitrary code mutation.

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

All limitations / Review context

Do background updates preserve the installed context contracts and accurately distinguish configuration from observed usage?

The bounded review of the publisher's documented Mason engineering-decision context and documentation audit 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.

Main risk is persistent repository knowledge exposure rather than arbitrary code mutation.
Repository context and .mason metadata scope.
Local project context/decision records persist in repository metadata.
Reviewed write actions: Initialize/update concept maps; Save decisions; Update snapshot metadata
Sensitive access: Source-code structure, Technical decisions
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.
Repository identity
Optional sync auth details
Writes project metadata under .mason rather than application code.
Optional external wiki sync adds another data boundary.
Public package info does not establish every auth/retention detail.

Original activity observations

mason-context 0.20.2 published 2026-09-30T12:10:41.939Z

Technical identity

npm/mason-context

Exact implementation source: https://www.npmjs.com/package/mason-context ↗
Reviewed resource type: MCP Server
Package identity: npm:mason-context

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 7, 2026

Package registry ↗
mason-context
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.

Warning

No runtime server process, Docker setup, OAuth or credentials were executed during this research.
Project initialization can create .mason state and modify CLAUDE.md; avoid invoking as a silent connectivity probe.
Install documentation is not a guarantee of current package/runtime compatibility.
Official publisher repository documents a runnable Mason MCP server via npm package binary mason-mcp; Git installer is an alternative, not a prerequisite.
2026-10-13 targeted publisher npm README plus official repository/docs where specified; static research, not runtime test.
Never paste real credentials into a documentation example.
No live install, OAuth, paid calls, third-party mutation or credential revocation executed.
Some host removal commands are MCP100-composed based on chosen registration name, not publisher-authored.

Install / connect
Publisher instructions
Publisher-documented package/connection route; replace placeholders and verify host-specific syntax.
Publisher setup example · Codex only · Publisher instructions
mason setup --host codex
Previously reviewed npm registration alternative; release installer is separate · Claude Code only · Publisher instructions
claude mcp add mason --scope user -- npx -p mason-context mason-mcp
Configure / authenticate
MCP100 setup guide
Install Mason via publisher release installer (macOS/Linux install.sh or Windows install.ps1), then mason setup in repository. Setup creates client config, hooks and instructions.
Use correct transport and published host config. Never paste secrets in chat; server registration is separate from software installation.
Previously reviewed configuration / prerequisites: For Cursor/Codex, use publisher-provided config using npx -p mason-context mason-mcp (client config syntax differs). Project Git repository required.
Check connection
Suggested check
mason status shows installation/configuration, then confirm discovered MCP tools.
Remove / uninstall / revoke
MCP100 setup guide
If registered as `mason-context` in Claude Code, remove its exact client entry with `claude mcp remove mason-context`; for Cursor/Claude Desktop/Codex, remove the matching MCP entry in that host settings. This client removal is MCP100-composed, not a vendor uninstall instruction. Npx does not imply a global install; do not delete user data or revoke credentials implicitly.
Publisher install example registration name(s): mason. The supplied removal example applies only to an existing Claude Code registration named mason-context; it does not remove the differently named install example. Confirm the actual host entry before use.
Conditional host / package cleanup · Claude Code only · MCP100 composed guide · Review before use
```
claude mcp remove mason-context
```

Official Documentation & Sources

What it does

MCP-only context-engineering server for feature-to-file concept maps, decision records, drift verification and optional wiki synchronization.

Capability: Files & Knowledge
Resource type: MCP Server
Best fit: Maintaining codebase concept maps, decisions and change-impact context for coding agents.

Representative uses

Initialize concept map
Save technical decisions
Retrieve task context
Verify snapshots/drift

Limitations

Writes project metadata under .mason rather than application code.
Optional external wiki sync adds another data boundary.
Public package info does not establish every auth/retention detail.

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: Repository context and .mason metadata scope.
Data handling: Local project context/decision records persist in repository metadata.
Cost: free
Risk and cautions: Main risk is persistent repository knowledge exposure rather than arbitrary code mutation.

Access scope and cautions

Write actions: Initialize/update concept maps Save decisions Update snapshot metadata
Sensitive access: Source-code structure Technical decisions
Risk level: moderate

FAQ

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

Which tasks are documented for this implementation?

The reviewed tasks include: Initialize concept map; Save technical decisions; Retrieve task context; Verify snapshots/drift.

What setup information is documented?

Recorded installation/entrypoint step: claude mcp add mason --scope user -- npx -p mason-context mason-mcp. Recorded transport: stdio. Prerequisites: Node/npm. These are the documented setup details, not a claim that installation or client compatibility was independently tested.

Can it modify data or perform write operations?

Documented write actions include: Initialize/update concept maps; Save decisions; Update snapshot metadata. Recorded permission boundary: Repository context and .mason metadata scope.

What data-handling boundary should I consider?

Local project context/decision records persist in repository metadata. Recorded sensitive-access context: Source-code structure; Technical decisions.

What limitations and risks should I check before use?

Main risk is persistent repository knowledge exposure rather than arbitrary code mutation. Writes project metadata under .mason rather than application code. Optional external wiki sync adds another data boundary. Public package info does not establish every auth/retention detail. 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.

Is this an official MCP?

Mason is listed as First-party MCP in MCP100’s current evidence.