Mmcp.market

VIVATLAS MCP server

by bobpanil·io.github.bobpanil/vivatlas·v1.0.1
No reviews yet

Self-hosted catalogue of your skills, agents and MCP servers, searchable by meaning over MCP

C68/100grade C
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
C68/100

full report

Adoption
Growing

3 stars

Reviews

Write one

Nobody has reviewed VIVATLAS yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

VIVATLAS tools

No tool declarations could be read from the package source. They show once the server is installed.

Public scan report

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

no findings
  • –Code scanpackage could not be scannedn/a
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 3 days ago15/15
  • Maintainer identityregistry namespace matches repository owner6/10
Overall 68/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

Install directly

claude mcp add vivatlas -- docker run -i --rm ghcr.io/bobpanil/vivatlas:1.0.1
Add to Cursor

VIVATLAS: common questions

Is VIVATLAS MCP server safe?
With care: it is graded C, so read the findings first (68/100). Read the VIVATLAS safety report
How do I install VIVATLAS?
It runs on your machine. Copy the Claude Code, Claude Desktop or Cursor config from the install section.
Does VIVATLAS need an API key?
Yes. The registry entry asks for SECRET_KEY, GOOGLE_API_KEY.
Is VIVATLAS maintained?
The last commit was 3 days ago (2026-09-17). The latest release is v1.0.1.

More from bobpanil →