Terminal MCP Servers: 12 Implementations Compared

The MCP ecosystem often has several independent packages implementing the same tool — and "Terminal" currently has 12. Every one of them was scanned with the same deterministic engine, so the numbers below are directly comparable: the Trust Score (A–F), the capability blast radius, and how much of the package the scan could actually inspect. They are ranked by score; ties break toward unscoped, longer-established packages.

ImplementationPackageTrustCapabilityCoverageFindingsScanned
Terminalbest by npm terminal-mcp npm A 98/100 Minimal Source 0 2026-09-07
Terminal Source verified by ellery @ellery/terminal-mcp npm A 94/100 High Source 3 2026-09-07
Terminal by dillip285 @dillip285/mcp-terminal npm A 93/100 High Source 3 2026-09-07
Terminal by yourusername terminal-mcp-server npm A 93/100 High Source 2 2026-09-07
Terminal by seepine @seepine/mcp-terminal npm A 93/100 High Source 4 2026-09-07
Terminal by rinardnick @rinardnick/mcp-terminal npm A 93/100 High Source 4 2026-09-07
Terminal by mkpvishnu terminal-mcp PyPI A 93/100 High Source 7 2026-08-25
Terminal by kanniganfan terminal-mcp-server PyPI A 93/100 High Source 7 2026-08-25
Terminal by pavanbhatt @pavanbhatt/terminal-mcp npm A 92/100 High Source 5 2026-09-07
Terminal by aybelatchane mcp-server-terminal npm B 87/100 High Source 2 2026-09-07
Terminal by GeLi2001 mcp-terminal npm B 87/100 High Source 2 2026-09-07
Terminal by npm mcp-terminal-server npm B 87/100 Minimal Metadata 0 2026-09-07

A higher-ranked implementation is not "the official one" — ranking reflects only what the deterministic scan found in each published package. Open an implementation to read its individual findings with evidence, its scan history per version, and to grab an embeddable badge. Scores are automated opinions, recomputed on every rescan.