Home / MCP registry index / ai.betterpost/server
BetterPost
ai.betterpost/server in the official MCP registry.
Endpoint https://betterpost.ai/mcp. Source: github.com/betterpost/betterpost-plugin.
The registry describes it as: Finds timely sources across news, social, and the web and writes posts worth publishing.
We read its 23 tools on 2026-10-21. 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
betterpost_create_project betterpost_generate_content betterpost_derive_content betterpost_list_content betterpost_get_content betterpost_delete_content betterpost_list_projects betterpost_get_project betterpost_update_project betterpost_delete_project betterpost_list_sources betterpost_add_source betterpost_remove_source betterpost_list_stories betterpost_add_story betterpost_hide_story betterpost_unhide_story betterpost_suggest_topics betterpost_get_usage betterpost_get_settings betterpost_update_settings betterpost_expand_coverage betterpost_humanize
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/ai-betterpost-server)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.