Mafdet MCP — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to Mafdet read-only account and documentation helpers: Does tool expansion preserve the explicit distinction from model inference and credential provisioning?

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

Best fit

Read-only account visibility and documentation search for Mafdet AI.

What we know

Read-only MCP exposing model catalog, docs search and authenticated account balance/usage/subscription information. It does not call models or expose key-management/write operations.

Maintenance / activity evidence

@mafdet/mcp 1.4.32 published 2026-09-03T07:04:11.549Z

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.
Read-only account and docs/model visibility.
Scoped account:read key.
Sensitive access: Account balance, Usage/subscription metadata, API key

Official docs state all MCP tools are read-only.

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

All limitations / Review context

Does tool expansion preserve the explicit distinction from model inference and credential provisioning?

The bounded review of the publisher's documented Mafdet read-only account and documentation helpers 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.

Official docs state all MCP tools are read-only.
Read-only account and docs/model visibility.
Scoped account:read key.
Key is sent over HTTPS to Mafdet only for account tools.
Sensitive access: Account balance, Usage/subscription metadata, API key
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.
public repository identity
Account tools need a key with account:read scope.
No model inference occurs through this MCP.
Package/repository identity was not independently bound in this pass.

Original activity observations

@mafdet/mcp 1.4.32 published 2026-09-03T07:04:11.549Z

Technical identity

npm/@mafdet/mcp

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

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 metadata ↗
@mafdet/mcp
Recorded package identity, distribution or download evidence.
Evidence source ↗
docs.mafdet.ai/zh-CN/integrations/mcp/
Source material retained for this review.
Includes references whose attribution is not established.
Evidence source ↗
www.npmjs.com/search?q=keywords%3Amafdet
Source material retained for this review.
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
Public list_models and search_docs work without key; account tools need MAFDET_API_KEY with account:read scope.
publisher install or stdio launch · Publisher instructions
npx -y @mafdet/mcp
Configure / authenticate
MCP100 setup guide
Mafdet list_models is keyless, but account usage requires MAFDET_API_KEY with account:read scope.
claude desktop or cursor mcpServers json · MCP100 composed guide
{ "mcpServers": { "mafdet": { "args": [ "-y", "@mafdet/mcp" ], "command": "npx", "env": { "MAFDET_API_KEY": "sk-mafdet-live-REPLACE" } } } }
Check connection
Suggested check
Call publisher list_models without MAFDET_API_KEY for public catalog; account get_usage_summary requires account:read scoped key and must be verified separately.
Remove / uninstall / revoke
MCP100 setup guide
If you added this integration to Claude Code under the registration name `mafdet`, run `claude mcp remove mafdet` to unregister that client entry. In Claude Desktop, Cursor, VS Code or another host, delete/disable the corresponding named MCP registration in that host's settings and restart/reconnect. If you installed an npm package globally or operate a separate HTTP server, uninstall/stop it with its original deployment method. This does not delete user data or revoke service credentials.
MCP client unregister, stopping hosted processes, package uninstall, OAuth disconnect and token revocation are distinct actions.
A claude mcp remove command is only valid for Claude Code when the local registration actually has that name. Other MCP hosts require their own UI/config cleanup.
Separate provider credential revocation · publisher documented: Mafdet official Key Lifecycle guide: open platform API Keys page; Disable temporarily blocks requests (can be re-enabled); Delete permanently revokes key, cannot be undone. Create new and replace MAFDET_API_KEY afterward.
Remove client registration · Claude Code only · MCP100 composed guide
claude mcp remove mafdet

Official Documentation & Sources

What it does

Read-only MCP exposing model catalog, docs search and authenticated account balance/usage/subscription information. It does not call models or expose key-management/write operations.

Capability: AI & Reasoning
Resource type: MCP Server
Best fit: Read-only account visibility and documentation search for Mafdet AI.

Representative uses

List available models/pricing/access tier
Search Mafdet docs
Read wallet balance
Read recent usage
Read subscription status

Limitations

Account tools need a key with account:read scope.
No model inference occurs through this MCP.
Package/repository identity was not independently bound in this pass.

Reviewed access

Access & risk

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

Authentication: Scoped account:read key.
Permissions: Read-only account and docs/model visibility.
Data handling: Key is sent over HTTPS to Mafdet only for account tools.
Cost: service_plan
Risk and cautions: Official docs state all MCP tools are read-only.

Access scope and cautions

Write actions: None in the reviewed inventory
Sensitive access: Account balance Usage/subscription metadata API key
Risk level: low

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: List available models/pricing/access tier; Search Mafdet docs; Read wallet balance; Read recent usage; Read subscription status.

What setup and authentication are documented?

Recorded installation/entrypoint step: npx -y @mafdet/mcp. Recorded transport: stdio. Recorded environment-variable notes: MAFDET_API_KEY (optional for public tools; required for account tools). No configuration values are supplied here. Prerequisites: Node.js 20+; MCP client. These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: Optional account:read API key.

Can it modify data or perform write operations?

The reviewed inventory lists no write actions. An empty inventory alone does not establish read-only authority. Recorded permission boundary: Read-only account and docs/model visibility.

What data-handling boundary should I consider?

Key is sent over HTTPS to Mafdet only for account tools. Recorded sensitive-access context: Account balance; Usage/subscription metadata; API key.

What limitations and risks should I check before use?

Official docs state all MCP tools are read-only. Account tools need a key with account:read scope. No model inference occurs through this MCP. Package/repository identity was not independently bound in this pass. 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 service plan. This classification does not establish current prices, quotas or the cost of every downstream operation. Check the applicable service terms before authorizing paid actions.