Home / MCP registry index / com.mewboard/mewboard
Mewboard
com.mewboard/mewboard in the official MCP registry.
Endpoint https://app.mewboard.com/mcp. Source: github.com/allidevelop/mewboard-mcp.
The registry describes it as: Projects, issues, comments, files, clients and project money in Mewboard, a board shared with AI.
We read its 66 tools on 2026-11-16. 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 mewboard https://app.mewboard.com/mcp{
"mcpServers": {
"mewboard": {
"url": "https://app.mewboard.com/mcp"
}
}
}code --add-mcp '{"name":"mewboard","type":"http","url":"https://app.mewboard.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
get_mewboard_guide list_projects get_project create_project update_project list_issues get_issue create_issue update_issue delete_issue add_checklist add_checklist_item update_checklist_item delete_checklist set_project_statuses list_notifications mark_notifications_read follow_issue unfollow_issue list_following set_project_notifications list_templates save_project_as_template get_template create_template update_template list_trash restore_issue list_fields create_field update_field try_formula delete_field list_milestones list_members get_project_totals get_client_totals import_issues get_money_report list_clients create_client update_client delete_client create_milestone update_milestone delete_milestone list_comments add_comment update_comment delete_comment create_form update_form list_forms list_form_responses attach_file read_issue read_project read_attachment list_attachments delete_attachment and 6 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-16):
f856f59466ba18fb. 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-mewboard-mewboard)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. How tool poisoning works. 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 every server in the index.