Home / MCP server directory / com.spicapost/spica-post
Spica Post
com.spicapost/spica-post in the official MCP registry.
Endpoint https://app.spicapost.com/mcp. Source: github.com/unbowedgod/spica-post-mcp.
The registry describes it as: Your AI assistant drafts, schedules and posts to your social accounts once you approve.
We read its 70 tools on 2026-11-19. 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 about every two weeks.
Connect it
The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:
claude mcp add --transport http spica-post https://app.spicapost.com/mcp{
"mcpServers": {
"spica-post": {
"url": "https://app.spicapost.com/mcp"
}
}
}code --add-mcp '{"name":"spica-post","type":"http","url":"https://app.spicapost.com/mcp"}'Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.
Let Claude Code check servers as it adds them
With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.
claude plugin marketplace add lazaretto-ai/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-pluginsTools it advertises
accounts_list accounts_connect site_study posts_recent capabilities boards_list tiktok_account_get accounts_board boards_create boards_edit accounts_create_test accounts_disconnect drafts_list drafts_get drafts_create drafts_edit drafts_validate drafts_delete drafts_hold drafts_hold_delete publish schedule queue_add queue_get queue_set jobs_list results_get jobs_get jobs_cancel jobs_reschedule media_upload media_from_url usage_get post_check help_search help_get settings_set_time_zone media_list media_delete media_view setup_start brands_list brand_get brand_save brand_rename templates_list templates_get templates_render profile_get profile_save articles_list articles_get articles_save articles_delete locations_list locations_save locations_delete locations_report links_list links_save and 10 more
Tool changes
We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.
Fingerprint of its tools at our last full read (2026-11-19):
fd30abee94f74776. A client can hash the tools it is served the same way and compare;
the full value and a hash per tool are in this page as JSON.
Rather than checking back: subscribe to this server's tool changes (a feed, no account and no address needed). Tool names and dates only, never what a tool says.
Run this server? Show the check in your README
The badge reflects the latest read:
[](https://lazaretto.dev/mcp-registry/com-spicapost-spica-post)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. MCP tool poisoning, explained. What we found across the registry. Check another server.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse the MCP server directory.