Home / MCP registry index / app.aiponge/mcp
aiponge
app.aiponge/mcp in the official MCP registry.
Endpoint https://mcp.aiponge.com/mcp. Source: github.com/mameziane/aiponge.
The registry describes it as: private by default journaling, self-understanding, reflective songs, books, playlists, insights.
We read its 23 tools on 2026-10-22. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
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
get_capabilities get_profile list_audio_preference_profiles update_audio_preferences list_books browse_books read_book play_audiobook list_tracks play_track get_generation_status generate_track get_track get_usage save_entry submit_track_feedback correct_insight list_generations get_entry compose_entry search_entries create_entry get_insights
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/app-aiponge-mcp)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.