Home / MCP registry index / ai.pingaura/pingaura
PingAura
ai.pingaura/pingaura in the official MCP registry.
Endpoint https://www.pingaura.ai/api/mcp.
The registry describes it as: AI visibility for your brand: scores, competitors, prompts, site health and articles.
On 2026-10-27 this server asked for credentials before it would list its tools, so we could not read them. Nothing was checked: this is not a clean result.
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/ai-pingaura-pingaura)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.
Related
| Good Turn Studio (all tools) io.github.GoodTurnStudio/all | 162 tools, nothing matched 2026-10-27 |
| com.medigami/mcp com.medigami/mcp | 87 tools, nothing matched 2026-10-27 |
| ch.swisslivingindex/swiss-living-index ch.swisslivingindex/swiss-living-index | 72 tools, nothing matched 2026-10-26 |
| Fda Devices io.github.pipeworx-io/fda-devices | 53 tools, nothing matched 2026-10-27 |
| Framezone app.framezone/framezone | 50 tools, nothing matched 2026-10-22 |
| Hsa Singapore io.github.pipeworx-io/hsa-singapore | 48 tools, nothing matched 2026-10-27 |