Home / MCP server directory / com.carlnotes/carlnotes
CarlNotes
com.carlnotes/carlnotes in the official MCP registry.
Endpoint https://carlnotes.com/mcp. Source: github.com/doubleoevan/carlnotes.
The registry describes it as: Read research findings, search topics, and manage your CarlNotes topics from your AI app.
We read its 45 tools on 2026-11-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 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 carlnotes https://carlnotes.com/mcp{
"mcpServers": {
"carlnotes": {
"url": "https://carlnotes.com/mcp"
}
}
}code --add-mcp '{"name":"carlnotes","type":"http","url":"https://carlnotes.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
list_topics read_topic_feed search_topic_findings search mark_finding_consumed rate_finding read_finding_rating_note bookmark_finding follow_topic edit_topic suggest_sources create_topic set_topic_image add_topic_attachment read_notes save_note delete_note list_teams read_team request_to_join_team send_invite respond_to_invite post_to_team_room read_profile read_activity read_account report_content block_user send_to_topic suggest_topics read_updates start_scan read_scan_status stop_scan read_topic_context read_topic_memories send_finding_feedback save_reaction read_hot_takes post_hot_take delete_hot_take read_news read_topic_posts read_topic_post read_dashboard
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-22):
b4df9bcbacda2e67. 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-carlnotes-carlnotes)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.