Home / MCP registry index / com.techfabric/techfabric
TechFabric
com.techfabric/techfabric in the official MCP registry.
Endpoint https://www.techfabric.com/mcp. Source: github.com/Fabric-Pro/techfabric-mcp.
The registry describes it as: For TechFabric engineers to write posts and case studies from their coding agent; anyone can read
We read its 33 tools on 2026-10-27. 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 get_page list_posts get_services explore_post compare_case_studies assess_databricks_readiness quiz_me visualize get_brief lint_draft check_draft submit_draft update_draft list_drafts get_status review_before_publishing publish_draft preview_draft revise_post start_post check_outline propose_edits apply_edits ask_author social_post_kit lint_social reddit_post_kit post_performance suggest_links_and_topics preview_diagram get_brief_pool propose_brief
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-techfabric-techfabric)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.