Servidor MCP de aiponge

• Nome no registroapp.aiponge/mcpverificado no registro MCP

O nome no registro fica sob aiponge.app. O registro só libera esse espaço de nomes para quem prova controle do domínio por DNS ou HTTP.

• Estadorespondeverificado em 2026-10-24
• Ferramentas23
• O servidor se chamaaiponge
• Versão do servidor1.2.0
• Versão do protocolo2025-06-18

Em 2026-10-24 o servidor respondeu a initialize e tools/list sem login. Primeira resposta em 161 ms.

• As ferramentas fazem todos os casos de uso verificados: turn a single honest sentence into a song; revisit saved songs in a private library.
• Verificado em 3 dos 7 dias necessários para julgar a confiabilidade.

Dito por regras a partir das medições acima. A primeira chamada provável é a escolha de um modelo na lista de ferramentas; leia a descrição antes de confiar nela.

• Nota INITE MCPdepois de uma semanaa nota precisa de 7 verificações diárias: 3 até agora
• O que um agente consegue fazer com ele2 de 2 casos de uso
• Respondeumedindo3 das 7 verificações diárias necessárias para mostrar a porcentagem
• Mediana da primeira resposta195 ms
• Espaço no contexto do agente≈ 7.041 tokensas definições de todas as ferramentas (23), que o agente carrega a cada turno
• Definições das ferramentasA · 93 de 100
• Resultados tipados22 de 23 ferramentasdeclaram outputSchema: o resultado chega tipado e é lido de uma vez

• Parâmetros sem descrição: em 9 de 23

Um programa verifica o servidor uma vez por dia: initialize e tools/list, sem modelo. Os tokens são o tamanho das definições, a cerca de quatro caracteres por token. A nota é a média de seis verificações do nome, da descrição, do esquema e das anotações de cada ferramenta; diz se as ferramentas estão bem descritas, não se funcionam. A nota pesa só o que foi medido: se responde (30%), se faz o trabalho do produto (25%), definições (20%), contexto (10%) e uso (15%). Uma parte não medida fica de fora, e uma instrução oculta limita a nota a 40. O estado dos servidores MCP dos fornecedores: método e números →

• get_capabilities

  Return the canonical aiponge MCP tool map, workflow order, account/role requirements, and UI panel capabilities. Use only to choose tools for supported reflection, journal, music, or book requests. Do not call this or any aiponge tool for…

• get_profile

  Show the user's account profile and saved settings: "what's on my profile?", "what language am I set to?", "my account settings". Returns account details, profile, general preferences, and activity counts, including saved song genre…

• list_audio_preference_profiles

  List the user's saved song sound profiles, including each profile ID and label. Use this before generate_track when the user asks to create a song with a named saved sound. Read-only.

• update_audio_preferences

  Change / set / update the user's saved AUDIO (music) preferences — the defaults generate_track applies automatically to every new song (genre, vocal gender, language, instruments, default audio content type). Supplied fields replace their…

• list_books

  Show / list the user's OWN books — "what books do I have?", "my library", "my books". Returns only the books they own or created, NOT the shared aiponge catalog. To discover or search the wider aiponge book catalog, use browse_books…

• browse_books

  Browse / search / discover / find books in the shared aiponge library catalog (not just the user's own — for those use list_books). "Find me a book about gratitude", "what books are there on sleep?", "browse the library". Optionally…

• read_book

  Read / open a book's text content — its chapters and the prose of each — so you can summarize, quote, or discuss it. "Read me that book", "what does the book say?", "summarize this book". Resolve the bookId via browse_books or list_books…

• play_audiobook

  Play / listen to a book as an audiobook — its chapters narrated as TTS audio, in order, with clickable stream links. "Read this book aloud", "play the audiobook", "I want to listen to a book". Resolve the bookId via browse_books or…

• list_tracks

  Show / list / browse the user's songs — "what songs do I have?", "show me my music", "my tracks", "my library", "my playlist of songs". Returns the user's private music tracks. Each item includes its `title`, `themes` (canonical topic…

• play_track

  Play / listen to / put on ONE specific song the user already has — returns a fresh, clickable stream link for that track by its id. The user normally refers to a track by NAME, not id: when the requested title is approximate, partial, or…

• get_generation_status

  Check on a song/track/music that is still being generated — "is my song ready?", "how is it coming along?". Takes the requestId returned by generate_track. Returns progress while generating, a play link when complete, or the failure…

• generate_track

  Create / make / write / generate a SONG, a TRACK, or a piece of MUSIC for the user from a topic (e.g. "a calm morning walk", "write me a song about my mom", "make me some music about the sea"). This is THE tool for any "create/make/write…

• get_track

  Read the lyrics, source entry ID and context of a saved song. Use a real trackId from list_tracks or generation. Does not start playback.

• get_usage

  Read available account allowances and reset time before planning creation. This is advisory; the server still reserves usage atomically. Unavailable counters are identified explicitly; do not assume their remaining allowance.

• save_entry

  For clients without a journal panel: save the exact reflection the user has reviewed and explicitly confirmed. Never set confirmed from silence or inferred intent. Use compose_entry to prepare a draft; show it to the user, then save only…

• submit_track_feedback

  Record only explicit user feedback on a saved song: understood, partial or missed. Never infer recognition or helpfulness from playback. Replaces the user's previous feedback for this song. Resolve trackId first.

• correct_insight

  Record the user's explicit correction to a specific inferred dimension/value they have seen in aiponge. Do not invent a dimension or value, and do not treat this as a diagnosis. Use only when the user confirms the correction. The backend…

• list_generations

  Find the account's active song generation requests after reconnecting or losing a requestId. Inspect them before retrying generation. Completed songs can be found with list_tracks.

• get_entry

  Open / read the full text of ONE specific journal entry by its id. Resolve the id via list_entries or search_entries first; never invent an entry id.

• compose_entry

  THE DEFAULT WAY TO SAVE A REFLECTION OR JOURNAL ENTRY. Use this — NOT create_entry — for any request like "save this as a journal entry", "journal this", "add a journal entry", "save my reflection", "put this in my diary", "write this…

• search_entries

  Search the user-owned journal by words in any supported language, tag, personal date, or import source. Returns matching entry IDs and short excerpts. Use get_entry for full text. Follow nextCursor with identical filters until hasMore is…

• create_entry

  Persist a journal entry DIRECTLY to the journal, with NO review step. This is the silent/import-only path — for an ordinary chat request like "save this as a journal entry" / "journal this" / "add a journal entry", do NOT use this; use…

• get_insights

  Surface what aiponge has NOTICED about the user: the observations, recurring patterns, and wellness signal drawn from their self-model, inferred from their reflections. Read-only. Use it when the user asks "what has aiponge learned about…