Is Interactive Terminal MCP server safe?

Probably. Read the findings first.

C60/100grade C

Use with care. Some checks failed or could not be verified.

How Interactive Terminal compares

Against every graded Developer tools MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score: 60/100; higher than 14% of 1,119 Developer tools servers
Tools that change things: 57%; typical: 5%. Fewer write tools means less an agent can break

What its tools let an agent do: 2 read · 1 create · 2 change · 2 send or post

scanner v0.1.10 · 2026-09-28 · same rubric, same numbers if you re-run it

2 medium

Code scan55 source files scanned15/25
–Live reliabilityno gateway calls yet and no remote to proben/a
–Tool poisoningtools not inspected (local package is not executed); not countedn/a
Auth qualitylocal package, no credentials required12/15
Maintenancelast push 224 days ago4/15
Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10

mediumnpm install lifecycle script presentinstall.script

package.json: …t run", "test:watch": "vitest", "postinstall": "node -e \"try{require('fs').chmodSync(…

Overall 60/100. Components that don't apply are left out of the denominator. Any critical finding is an F.Rubric Appeal a finding JSON

Notion
Token-auth Notion MCP: pages, databases, blocks, comments, files. Runs headless in CI and agents.
not reviewed
Established
B
Homebutler
Tells an agent what changed on a server since it last looked - status, Docker, backups, Proxmox.
not reviewed
Established
C
maintenant
Docker monitoring for AI agents: logs, history, alerts. Can ack alerts; never touches containers.
not reviewed
Established
C