Documentation

Docs MCP

Remote MCP server for Tandem docs, install guides, SDKs, workflows, and agent setup help.

Deep ReviewMCP Rank ReviewedMedium confidencemedium riskclaudecursorcodex

Score breakdown

Install + docs80

Maintenance76

Auth handling69

Client compatibility78

Real usefulness81

Safety signals68

Evidence history

Review snapshots show why the current score, confidence, and risk labels changed over time.

seed review

Date	Change	Score	Confidence	Risk
May 20, 2026	Initial MCP Rank review captured from the curated seed dataset. MCP Rank completed a deep review on 2026-05-20 using registry metadata, repository/API metadata, package or container provenance where available, capability-surface analysis, and rollout-risk notes. seed snapshot · reviewed	76	medium	medium

Date

Change

Score

Confidence

Risk

May 20, 2026

Initial MCP Rank review captured from the curated seed dataset.

MCP Rank completed a deep review on 2026-05-20 using registry metadata, repository/API metadata, package or container provenance where available, capability-surface analysis, and rollout-risk notes.

seed snapshot · reviewed

medium

Evidence notes

MCP Rank completed a deep review on 2026-05-20 using registry metadata, repository/API metadata, package or container provenance where available, capability-surface analysis, and rollout-risk notes.

GitHub repository frumu-ai/tandem was reachable during review with recent activity on 2026-05-20.

The repository describes a local-first AI coworker for folders, so MCP Rank treats this as folder/workspace automation rather than a simple documentation-only server.

Repository provenance is directly linkable for follow-up maintainer and activity checks.

A concrete provider endpoint or docs URL is available for rollout validation.

Best-fit use cases

Promising for developers who want assistant setup help or folder-aware project guidance with public source available.

Better evaluated as a supervised local-workspace tool than as a low-risk hosted documentation lookup.

Risk analysis

Medium risk is appropriate because folder-aware automation can expose project files, even when the product positioning emphasizes local-first behavior.

High open issue count is a maintenance signal to watch before recommending broad team rollout.

A production recommendation would need install testing, exact tool-list review, and file-scope confirmation.

Use-case examples

Evaluate Docs MCP source links before install.

Compare Docs MCP risk and confidence against reviewed alternatives.

Use Docs MCP only after validating its install path and permissions.

Review status

Deep Review with medium confidence.

Leaderboards include only Deep Review entries or listings with explicit maintainer confirmation evidence. Source Reviewed and Install Tested pages remain visible for evaluation but are not ranked recommendations.

Install test

Command

Review provider documentation before install

Risk review

Deep Review means MCP Rank performed a stronger manual evidence and risk assessment; it is still not maintainer verification, legal advice, or a full security audit.

Repository issue volume is high enough to require maintainer triage before a deeper recommendation.

Do not treat the docs/category label as a safety guarantee; verify what folder or workspace context the server can access.

Verify install behavior and requested permissions in a sandbox before team rollout.

Maintainer verification is still recommended before treating this as a default-safe tool.

Sources

GitHub repohttps://github.com/frumu-ai/tandem Provider MCP endpoint or docshttps://tandem.ac/mcp Official MCP registryhttps://registry.modelcontextprotocol.io/

Source trail: Official MCP registry, public repository, package, or provider endpoint review

Badges

Maintainers can share reviewed listing status for Docs MCP.

Weekly MCP trust report

Reviewed servers, risk notes, new indexed tools, and maintainer verification asks.