Home / MCP registry index / ai.thesingulariti/graviti
ai.thesingulariti/graviti
ai.thesingulariti/graviti in the official MCP registry.
Endpoint https://graviti.thesingulariti.ai/api/mcp. Source: github.com/sclaytonmyosin/graviti-engine.
The registry describes it as: Verified brand claims with receipts for agent commerce. Ranking is never paid; the engine is open.
We read its 7 tools on 2026-10-22. Nothing in them matched our tool-poisoning rules.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
match_intent get_verified_claims category_landscape get_accountability_log get_ledger get_gap_report report_conversion
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/ai-thesingulariti-graviti)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.