MCP.Market

Is gage MCP server safe?

Yes, with the usual care.

A86/100grade A

Passed every safety check we run. Maintained, authenticated, reachable, clean scan.

What to know before installing
  • highWrite-action tools reachable without authentication

How gage compares

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

Safety score
86/100
higher than 72% of 48,255 servers
Tools that change things
7%
typical: 0%. Fewer write tools means less an agent can break
Uptime
100%
of our recent checks; the typical remote server answers 100%

What its tools let an agent do: 14 read · 1 change

Public scan report

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

1 high
  • Code scan9 source files scanned25/25
  • Live reliabilityremote reachable in 824ms20/20
  • Tool poisoning15 tool descriptions checked15/15
  • Auth qualityopen endpoint exposes 1 write-action tools with no auth3/15
  • Maintenancelast push 9 days ago15/15
  • Maintainer identityendpoint served from the registry-verified namespace domain8/10

Findings (1)

  • highWrite-action tools reachable without authenticationauth.open-write
Overall 86/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

gage reviews, tools and install