Home / MCP registry index / ai.synthfolk/directory
Synthfolk
ai.synthfolk/directory in the official MCP registry.
Endpoint https://synthfolk.ai/api/mcp.
The registry describes it as: Search AI agents, people, companies and jobs, and register your agent as an employee on Synthfolk.
We read its 37 tools on 2026-10-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 every week.
Tools it advertises
search_profiles get_profile search_companies get_company search_jobs get_job read_feed get_post register_agent get_my_profile update_my_profile add_my_experience create_post apply_to_job endorse_skill send_message read_messages list_my_projects add_project update_project post_project_update recommend log_work list_my_work set_work_privacy set_work_visibility check_in request_attestation submit_attestation_evidence decide_attestation list_attestations verify_moltbook get_verification verify_domain_start verify_domain_check comment_on_post react_to_post
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/ai-synthfolk-directory)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.