Skip to content

TechFabric MCP server

com.techfabric/techfabrictechfabric.comstreamable-httpv1.6.0Scanned

Write TechFabric posts from your agent. Walk through posts, compare studies, check readiness.

36 tools: 3 can delete or cancel things, 24 change things and 9 only read.

Tools: 3 delete, 0 irreversible, 24 write, 9 read.
  • Reads private data · 0
  • Reads text others write · 6
  • Can send data out · 7
  • 8 findings

Tools listed without sign-in. Remote posture

With Anlyon

3 tools here can delete or cancel things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the TechFabric MCP server can do

The TechFabric MCP server is published by techfabric.com, a domain the MCP Registry verified. It has 36 tools. It can delete or cancel things (3 tools: update_draft, publish_draft and apply_edits) and create or change data (24 tools: explore_post, assess_databricks_readiness, quiz_me, visualize and 20 more). 9 tools only read.

6 tools bring in text other people can write (search, get_page, list_posts and 3 more); 7 tools can send data out of your system (explore_post, publish_draft, revise_post and 4 more).

The fixed checks matched 8 findings (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed 6 times since Anlyon Radar first saw them.

Last scanned Nov 9, 2026, version 1.6.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

36 tools

Deletes or cancels 3Claude Code: deny
  • apply_editsRequires a TechFabric engineer's Microsoft sign-in (scope blog.write).No findings

    Why it is in this group

    • The name "apply_edits" says "apply": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Requires a TechFabric engineer's Microsoft sign-in (scope blog.write). The engineer's decision on a proposal (propose_edits): the changes they accepted are applied to the saved text and saved (as update_draft saves), the rule-based checks run at once and the full check starts in the background. Only what the engineer accepted, never your own choice. Never publishes.

    Annotations the server declares

    • title: Apply the accepted changes
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: false
  • publish_draftRequires a TechFabric engineer's Microsoft sign-in (scope blog.write).Reads text others writeCan send data outNo findings

    Why it is in this group

    • The name "publish_draft" says "publish": a word for a change that another call does not undo.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe name "publish_draft" says "publish": it sends or publishes something to other people.
    Description, as the server wrote it
    Requires a TechFabric engineer's Microsoft sign-in (scope blog.write). Publish one of your drafts to techfabric.com, only after the engineer confirms, once check_draft with the id has passed on exactly the saved text. The first call publishes nothing: with the draft card showing it waits for the engineer's Publish there; else a form, or a one-time confirmation you send back only after their yes. Never in a scheduled or unattended run. override names wording checks the engineer chooses to publish past (never the hard set, the fact-check, slop, quality, opening or ending). confirm_via "token": always return the one-time confirmation instead of a form, for a UI that asks the engineer itself.

    Annotations the server declares

    • title: Publish your draft
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: true
  • update_draftRequires a TechFabric engineer's Microsoft sign-in (scope blog.write).No findings

    Why it is in this group

    • The name "update_draft" says "update": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Requires a TechFabric engineer's Microsoft sign-in (scope blog.write). Save a new version of your draft (state drafted): the whole Markdown, and base_hash, the hash of the version you edited (draft.base_hash from get_status, or your last update_draft's text_hash). Answers in a second or two; the preview rebuilds in the background. It runs no checks: lint_draft the edit first, then check_draft with the id. Refused if the draft changed since base_hash or is open in the browser editor. The engineer may also edit and save it in the draft app: start each edit from a fresh get_status. Never publishes.

    Annotations the server declares

    • title: Save an edit to your draft
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: false
Changes things 24Claude Code: ask
  • ask_authorRequires a TechFabric engineer's Microsoft sign-in (scope blog.write).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Requires a TechFabric engineer's Microsoft sign-in (scope blog.write). One question only the engineer can answer (what was measured, who it was for, what happened): returned for you to ask in chat (or, with form: true, asked in a form where the client shows one); call again with their answer, word for word. The answer is stored as one of the draft's sources, which the fact-check reads as their own words. Never answer it yourself.

    Annotations the server declares

    • title: Ask you a question
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • assess_databricks_readinessInteractive: a Databricks readiness and migration check: eight multiple-choice questions (where the data runs now, how well the estate is known, access, deployment, failures, cost …No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Interactive: a Databricks readiness and migration check: eight multiple-choice questions (where the data runs now, how well the estate is known, access, deployment, failures, cost visibility, the team, the first use), scored by fixed points into five areas, with a readout: where to start, what to work on first, and links to TechFabric's own service pages, posts and Databricks Field Guide chapters, then the contact page with the matching topic. Call it without answers for the questions; with form: true, a client that shows forms asks them in one; a host with MCP Apps scores them in its view, and otherwise ask the reader in chat and send answers. The answers are scored and never stored or logged. For example: "are we ready for Databricks", "assess our migration readiness", "where should we start with Databricks".

    Annotations the server declares

    • title: Databricks readiness check
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • check_draftRequires a TechFabric engineer's Microsoft sign-in (scope blog.write).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Requires a TechFabric engineer's Microsoft sign-in (scope blog.write). The final verification publish_draft needs. With id: the full checks on your saved draft (judge, slop classifier, fact-check), about a minute; call it after lint_draft passes, never to iterate. Each call waits up to 25 seconds and then reports progress: call it again, never two at once, for the answer (nothing runs twice; a client with the tasks extension gets a task). Right after submit_draft it waits while the draft is filed. Without id it checks markdown and files nothing, which publish_draft doesn't count. On next_action confirm, send first_hand_to_confirm back as first_hand: the engineer confirms, never you.

    Annotations the server declares

    • title: Check a draft
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • check_outlineRequires a TechFabric engineer's Microsoft sign-in (scope blog.write).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Requires a TechFabric engineer's Microsoft sign-in (scope blog.write). A read, about a millisecond, free: an outline (title options, the opening's two sentences, four to six sections with a line each, the diagram, the FAQ questions; a case study's four sections) against the title, opening, heading and FAQ rules, before any prose; the opening's device and first words are held to the last ten published posts (editorial/voices-of-techfabric.md). Fix what it finds and call again until ready; then show the engineer outline_markdown and draft only after their OK.

    Annotations the server declares

    • title: Check an outline
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • explore_postInteractive: walk through a published techfabric.com post or case study: its diagram (the Mermaid flowchart it publishes) as steps in the order it flows, each step tied to the sect…Can send data out1 finding

    Why it is in this group

    • The name "explore_post" says "post": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • outboundThe name "explore_post" says "post": it sends or publishes something to other people.

    Findings

    • Warn

      The server marks "explore_post" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "explore_post" says "post": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Interactive: walk through a published techfabric.com post or case study: its diagram (the Mermaid flowchart it publishes) as steps in the order it flows, each step tied to the section it's about, with that section's opening in the page's own words and a link to it. A page with no diagram steps through its sections. Takes a URL, a slug or a topic (the closest post or case study). In a host that renders MCP Apps it opens as a view to click through; the text is complete without it. For example: "walk me through this post step by step", "show me how this works", "explain the diagram in this case study".

    Annotations the server declares

    • title: Explore a post
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_briefRequires a TechFabric engineer's Microsoft sign-in (scope blog.write).1 finding

    Why it is in this group

    • The name "get_brief" says "get": a word for reading.
    • The server marks it as not read-only (readOnlyHint: false).

    Findings

    • Warn

      The server marks "get_brief" as not read-only (readOnlyHint: false), and its words say it reads.

      Matched text

      annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "get_brief" says "get": a word for reading.

      What this check looks for
    Description, as the server wrote it
    Requires a TechFabric engineer's Microsoft sign-in (scope blog.write). Today's topic for a daily post, claimed for you for 24 hours (asking again returns the same one): the topic, angle, target search, sources, internal links, and the brief_id to pass to submit_draft. Status none, with the reason, when there is nothing today: stop there. No model is called. Ask the engineer for first-hand detail; never invent it.

    Annotations the server declares

    • title: Today's brief
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_statusRequires a TechFabric engineer's Microsoft sign-in (scope blog.write).1 finding

    Why it is in this group

    • The name "get_status" says "get": a word for reading.
    • The server marks it as not read-only (readOnlyHint: false).

    Findings

    • Warn

      The server marks "get_status" as not read-only (readOnlyHint: false), and its words say it reads.

      Matched text

      annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The name "get_status" says "get": a word for reading.

      What this check looks for
    Description, as the server wrote it
    Requires a TechFabric engineer's Microsoft sign-in (scope blog.write). Where one of your drafts stands (by its id; list_drafts lists them), with next_action: the single next step and the call to make. Also its saved Markdown and base_hash (for update_draft; read them again before each edit, as the engineer may have saved one in the draft app), what is failing, the last check, the preview link and, once published, live_url. A fact the blog writer waits on is in the status; form: true asks it as a form. Never the editor link: to edit in the browser, call open_editor. To show the engineer the draft itself ("show me the preview", "show it here"), call preview_draft, never fetch the preview link.

    Annotations the server declares

    • title: Where a draft stands
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • lint_draftRequires a TechFabric engineer's Microsoft sign-in (scope blog.write).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Requires a TechFabric engineer's Microsoft sign-in (scope blog.write). The site's rule-based checks (slop, claims, known errors, voice, opening, title, description, FAQ, diagram, images, links, a case study's rules) on a post's Markdown, frontmatter included: about a second, free, filing nothing. Iterate with this, never with check_draft: rewrite each passage in rewrite_plan as its fix says and lint again until ready, then review the draft against the judge_rubric it returns. With id, it lints a draft of yours: its saved text, or the markdown you send as an edit to it.

    Annotations the server declares

    • title: Lint a draft
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • lint_socialRequires a TechFabric engineer's Microsoft sign-in (scope blog.write).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Requires a TechFabric engineer's Microsoft sign-in (scope blog.write). A read: the site's writing rules and the social rules on a LinkedIn post's text (the AI tells, the slop, claims, announcement openers, engagement bait, hashtags), its length, what shows before "see more", and, with post, whether it links the post. Rewrite each finding and lint again until ready. Posts nothing.

    Annotations the server declares

    • title: Lint a LinkedIn post
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • open_editorRequires a TechFabric engineer's Microsoft sign-in (scope blog.write).No findings

    Why it is in this group

    • The name "open_editor" says "open": a word for a change.
    Description, as the server wrote it
    Requires a TechFabric engineer's Microsoft sign-in (scope blog.write). When the engineer asks to open or edit a draft, or one of their published posts, in the browser: a link to the browser editor that works once and expires in 15 minutes. Show it to them as a link and say so; never open or fetch it yourself. id is one of their drafts; post (or a published draft's id) opens or finds the post's revision, as revise_post does. Only their own drafts and posts (the site owner: any). The editor link in their email is unchanged.

    Annotations the server declares

    • title: Open in the browser editor
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • place_imageRequires a TechFabric engineer's Microsoft sign-in (scope blog.write).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Requires a TechFabric engineer's Microsoft sign-in (scope blog.write). A read: the Markdown for an image already uploaded to your draft, `![alt](name "caption")`, and with markdown the post with it in after the paragraph `after` names (or at the end) and the image rules read on it. Alt text is required (WCAG 2.1): without it, or with one that is the file name, "screenshot", the caption again, under 5 or over 250 characters, it returns the question to ask the engineer and no snippet: never write one yourself. decorative: true, only on the engineer's word, places a decorative image with empty alt. Saves nothing: save the post with update_draft.

    Annotations the server declares

    • title: Put an image in the post
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • post_performanceRequires a TechFabric engineer's Microsoft sign-in (scope blog.write).Reads text others writeCan send data out1 finding

    Why it is in this group

    • The name "post_performance" says "post": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe name "post_performance" says "post": it sends or publishes something to other people.

    Findings

    • Warn

      The server marks "post_performance" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "post_performance" says "post": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Requires a TechFabric engineer's Microsoft sign-in (scope blog.write). A read: how one of your own published posts is doing in Google (the blog's editor: any post). Search Console's clicks, impressions, CTR and average position for the last 28 days against the 28 before, the searches it shows for, whether Google has indexed it, and what to improve, each with the numbers behind it. Without post: all your posts with their last 28 days. Searches from the US only, so totals are lower than Search Console's all-countries view; cached for six hours. No model is called and nothing changes: revise_post changes a live post, only after the engineer agrees.

    Annotations the server declares

    • title: How a post is doing
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • propose_briefRequires a TechFabric engineer's Microsoft sign-in (scope blog.write), and only the site owner's is accepted (the Fabric Agents brief automation runs as him).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Requires a TechFabric engineer's Microsoft sign-in (scope blog.write), and only the site owner's is accepted (the Fabric Agents brief automation runs as him). Adds one brief to the pool get_brief offers engineers, first and matched to their work: topic, why (the evidence), angle, sources, target_query, for_author. Refused with the reason, nothing stored, when a live post or an idea in flight covers it, an open proposal already is it, or today's 3 are used; the same topic again is the same brief. Drafts and publishes nothing; no model.

    Annotations the server declares

    • title: Propose a brief
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • propose_editsRequires a TechFabric engineer's Microsoft sign-in (scope blog.write).No findings

    Why it is in this group

    • The name "propose_edits" says "edit": a word for a change.
    Description, as the server wrote it
    Requires a TechFabric engineer's Microsoft sign-in (scope blog.write). Propose changes to a filed draft as a redline the engineer decides on: each change a passage of the saved markdown (find, exactly as it is), what you propose instead (replace) and why (reason), at most 12 changes and 160 rewritten words each. Saves nothing. Show the engineer redline_text and send what they accept to apply_edits (or ask: true, a form where the client shows one). Use it for every fix to a filed draft, instead of update_draft.

    Annotations the server declares

    • title: Propose a redline
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • quiz_meInteractive: a multiple-choice quiz from a published post's own FAQs: each question is one of its FAQs, the right option is the post's answer, and the others are answers the site g…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Interactive: a multiple-choice quiz from a published post's own FAQs: each question is one of its FAQs, the right option is the post's answer, and the others are answers the site gives to other questions; no model writes them. Each has its answer, the post's explanation and a link. With form: true, a client that shows forms asks the questions in one and scores it; a host with MCP Apps scores it in its view; otherwise the text lists the questions and the key: ask the reader before revealing it, then send their letters as answers to score. A reader who kept a resume code (Keep my progress, in a host without Fabric's view state) picks up with resume alone. For example: "quiz me on this post", "test what I learned", "check my understanding".

    Annotations the server declares

    • title: Quiz me on a post
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • reddit_post_kitRequires a TechFabric engineer's Microsoft sign-in (scope blog.write).Can send data out1 finding

    Why it is in this group

    • The name "reddit_post_kit" says "post": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • outboundThe name "reddit_post_kit" says "post": it sends or publishes something to other people.

    Findings

    • Warn

      The server marks "reddit_post_kit" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "reddit_post_kit" says "post": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Requires a TechFabric engineer's Microsoft sign-in (scope blog.write). A read: what your agent needs to draft a Reddit post or thread answer in your own voice, from a published techfabric.com post or your own notes. The subreddit's rules, the frame (a plain title; first person; the problem, what you tried, what worked, your numbers), the disclosure line, the optional link last, a checklist and the steps to post it yourself. Send draft to check it: the site's writing rules plus Reddit's (no hashtags, no 'check out our', no call to action, substance before any link). No model is called and nothing is posted, voted or commented.

    Annotations the server declares

    • title: Reddit kit for a post
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • request_image_uploadRequires a TechFabric engineer's Microsoft sign-in (scope blog.write).No findings

    Why it is in this group

    • The name "request_image_upload" says "request": a word for a change.
    Description, as the server wrote it
    Requires a TechFabric engineer's Microsoft sign-in (scope blog.write). Adds an image to one of your own drafts without the browser editor: returns a one-time upload URL and its Authorization header (15 minutes, one PNG, JPEG, WebP or GIF file of the type given, up to 10 MB), and the curl command that PUTs the file from the engineer's machine. Run that curl as given: the token goes only in the header, never in the URL. Location and camera metadata are removed. Then place_image gives the snippet to put in the post. Pass alt only as the engineer's own words.

    Annotations the server declares

    • title: Upload an image
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • review_before_publishingRequires a TechFabric engineer's Microsoft sign-in (scope blog.write).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Requires a TechFabric engineer's Microsoft sign-in (scope blog.write). A read: whether one of your drafts may be published now, and if so the question to ask the engineer ("Publish '<title>' now? (yes/no)") with a one-time confirmation for this exact saved text and its checks (used once). Only after they say yes, call publish_draft with the id and that confirmation, and the same override. If it can't be published yet, it says why and what to do.

    Annotations the server declares

    • title: Review before publishing
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • revise_postRequires a TechFabric engineer's Microsoft sign-in (scope blog.write).Can send data outNo findings

    Why it is in this group

    • The name "revise_post" says "post": a word for a change.

    What it can reach

    • outboundThe name "revise_post" says "post": it sends or publishes something to other people.
    Description, as the server wrote it
    Requires a TechFabric engineer's Microsoft sign-in (scope blog.write). Open a revision of a post that is live on techfabric.com, by its URL or slug: only its author or the blog's editor. The revision's draft starts as the live text, with its own preview; then the same loop: get_status for its markdown, lint_draft with the id and your edit, update_draft, check_draft with the id, publish_draft. Publishing replaces the post at the same URL and byline and keeps its date. Asking again returns the revision already open.

    Annotations the server declares

    • title: Change a published post
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • social_post_kitRequires a TechFabric engineer's Microsoft sign-in (scope blog.write).Can send data out1 finding

    Why it is in this group

    • The name "social_post_kit" says "post": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • outboundThe name "social_post_kit" says "post": it sends or publishes something to other people.

    Findings

    • Warn

      The server marks "social_post_kit" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "social_post_kit" says "post": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Requires a TechFabric engineer's Microsoft sign-in (scope blog.write). A read: what your agent needs to draft a LinkedIn post about a published techfabric.com post, any post on the site. Its key points and first-hand sentences, its link with the LinkedIn campaign, the engineer's voice notes, the social rules and LinkedIn's lengths. No model is called and nothing is posted: draft the post from it, check it with lint_social, and show the engineer the text to post themselves.

    Annotations the server declares

    • title: LinkedIn kit for a post
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • start_postRequires a TechFabric engineer's Microsoft sign-in (scope blog.write).Can send data out1 finding

    Why it is in this group

    • The name "start_post" says "start": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • outboundThe name "start_post" says "start" and "post": it writes something other people read.

    Findings

    • Warn

      The server marks "start_post" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "start_post" says "start": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Requires a TechFabric engineer's Microsoft sign-in (scope blog.write). Start here when asked to write, draft or start a blog post or case study for techfabric.com, before writing anything, even inside the techfabric-web repository (never a local file): brainstorm mode (one question about real work first: what happened, what surprised you), then the interview for a post, a case study or an explainer, about seven questions tailored to the topic and to today's brief. First look through the repository, and the site with search and get_page, then send suggested (your answers from what you found) so the engineer only confirms or corrects; it also offers what techfabric.com already published on the topic (published). With form: true, a client that answers forms and shows no apps shows them as one form; otherwise ask them in chat and call again with answers. Returns their answers as sources for submit_draft, then outline and check_outline before any prose. A read: nothing is filed or claimed.

    Annotations the server declares

    • title: Start a post with an interview
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • submit_draftRequires a TechFabric engineer's Microsoft sign-in (scope blog.write).No findings

    Why it is in this group

    • The name "submit_draft" says "submit": a word for a change.
    Description, as the server wrote it
    Requires a TechFabric engineer's Microsoft sign-in (scope blog.write). File a post (or, with kind "case-study", a case study) under the engineer's byline, exactly as written: the site builds its preview and emails it to them. Send the whole Markdown with frontmatter (title and description at least), the engineer's own words as sources, and brief_id when it comes from get_brief, or from_idea when it continues an idea they emailed. Lint it clean first. Returns the draft's id and text_hash; next, check_draft with the id. Never publishes.

    Annotations the server declares

    • title: Submit a draft
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • visualizeInteractive: draw your answer as a card the reader can use: a comparison with a verdict, a plan as steps, a calculator whose chart follows its sliders, a quiz, a table, a diagram.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Interactive: draw your answer as a card the reader can use: a comparison with a verdict, a plan as steps, a calculator whose chart follows its sliders, a quiz, a table, a diagram. Write it as an A2UI v0.9.1 document; the tool checks that it will draw (a document that won't comes back as an error listing what to fix; its facts aren't checked), returns all of it as text (a one-line handoff where the card shows), and labels it as composed by you. Call it whenever the answer has a shape: the reader asks to compare ("compare", "X vs Y", "pros and cons", "trade-offs", "which is better for"), for a plan ("plan", "roadmap", "migration steps", "rollout", "timeline"), to "show me", "draw", "chart" or "visualise" something, or for "a table of" options, rather than answering with a long Markdown table or list; a post, a case-study comparison or a readiness check go to explore_post, compare_case_studies and assess_databricks_readiness first. Get the facts first with search or get_page and pass those URLs as sources: only pages this site publishes are listed. In a host that renders MCP Apps it opens as the card; the text is complete without it. For example: "draw that Databricks comparison as a card", "lay out the migration plan step by step", "show me the cost options side by side", "compare Fabric vs Databricks", "pros and cons of a lakehouse", "a rollout timeline for the migration".

    Annotations the server declares

    • title: Draw an answer
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 9Show 9 read-only tools
  • compare_case_studiesInteractive: two or three of TechFabric's published case studies side by side: each one's challenge, strategy, solution and results, in its own words (the bold statement and the st…No findings

    Why it is in this group

    • The name "compare_case_studies" says "compare": a word for reading.
    Description, as the server wrote it
    Interactive: two or three of TechFabric's published case studies side by side: each one's challenge, strategy, solution and results, in its own words (the bold statement and the start of each section), with its client, sector and stack where the case study states them, and links to each section. Name them by slug or URL, or give a topic for the closest three; with neither, the list to choose from. Nothing is added that the case studies don't publish. For example: "compare your case studies", "how did these two projects differ", "show me your Databricks projects side by side".

    Annotations the server declares

    • title: Compare case studies
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_brief_poolRequires a TechFabric engineer's Microsoft sign-in (scope blog.write), and only the site owner's is accepted (the Fabric Agents brief automation runs as him).No findings

    Why it is in this group

    • The name "get_brief_pool" says "get": a word for reading.
    Description, as the server wrote it
    Requires a TechFabric engineer's Microsoft sign-in (scope blog.write), and only the site owner's is accepted (the Fabric Agents brief automation runs as him). A read: the briefs proposed and not yet taken, the competitor-gap and backlog searches no post or idea covers yet, the 30 most recent posts and the ideas in flight. What the brief automation reads before it proposes. Deterministic, no model; it changes nothing.

    Annotations the server declares

    • title: Brief pool
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_pageOne published page of www.techfabric.com as clean Markdown, with its title, search title (metaTitle), description, date, updated, author, tags, FAQs as question and answer pairs, a…Reads text others writeNo findings

    Why it is in this group

    • The name "get_page" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    One published page of www.techfabric.com as clean Markdown, with its title, search title (metaTitle), description, date, updated, author, tags, FAQs as question and answer pairs, and canonical URL. Takes a URL, a path or a post's slug. Only published, indexable pages. Drafts are private: list_drafts lists a signed-in engineer's drafts; a TechFabric engineer connects with Microsoft (the client's Connect or Authenticate button) to list and write them.

    Annotations the server declares

    • title: Read a page
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_servicesEvery service, solution, Databricks, AI, cloud, software, accelerator and product page on techfabric.com: its name, URL, kind and summary, exactly as the live page states them.Reads text others writeNo findings

    Why it is in this group

    • The name "get_services" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    Every service, solution, Databricks, AI, cloud, software, accelerator and product page on techfabric.com: its name, URL, kind and summary, exactly as the live page states them. Read one in full with get_page.

    Annotations the server declares

    • title: What TechFabric offers
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_draftsRequires a TechFabric engineer's Microsoft sign-in (scope blog.write).No findings

    Why it is in this group

    • The name "list_drafts" says "list": a word for reading.
    Description, as the server wrote it
    Requires a TechFabric engineer's Microsoft sign-in (scope blog.write). Lists your drafts (blog posts, case studies and revisions of live posts), newest first: each one's id, title, kind, state (writing, question_for_you, drafted, checks_failing, ready_to_publish, published and the rest), created and updated dates, preview link and next_action. Filter by state, kind and creation date (created_after, created_before: "yesterday" is the day before the answer's today), and page with cursor. The editor may pass all for everyone's; the site owner, stale: true for his owner queue (drafts stuck over two days). Reads only. Then get_status with an id for one draft in detail.

    Annotations the server declares

    • title: Your drafts
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_postsTechFabric's published blog posts, newest first, optionally only those with a tag, by an author, or dated on or after a day.Reads text others writeNo findings

    Why it is in this group

    • The name "list_posts" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe name "list_posts" says "list" and "post": it reads posts, which other people can write.
    • untrusted-inputThe description's first sentence says "post": it reads posts, which other people can write.
    Description, as the server wrote it
    TechFabric's published blog posts, newest first, optionally only those with a tag, by an author, or dated on or after a day. Drafts are private: list_drafts lists a signed-in engineer's drafts; a TechFabric engineer connects with Microsoft (the client's Connect or Authenticate button) to list and write them.

    Annotations the server declares

    • title: List blog posts
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • preview_diagramRequires a TechFabric engineer's Microsoft sign-in (scope blog.write).No findings

    Why it is in this group

    • The name "preview_diagram" says "preview": a word for reading.
    Description, as the server wrote it
    Requires a TechFabric engineer's Microsoft sign-in (scope blog.write). A read: every ```mermaid block in a post (or one mermaid source), as the site will treat it. For each: its lines in the post, its caption, whether the site's mermaid parses it (with the error and its line in the post when it doesn't), and the diagram rules' findings (a caption that states the point; no fact in a label the section's text doesn't say). In a host that renders MCP Apps it opens the diagrams drawn in the site's theme. Files nothing, calls no model; use it while drafting, then lint_draft the whole post.

    Annotations the server declares

    • title: Preview diagrams
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • preview_draftRequires a TechFabric engineer's Microsoft sign-in (scope blog.write).No findings

    Why it is in this group

    • The name "preview_draft" says "preview": a word for reading.
    Description, as the server wrote it
    Requires a TechFabric engineer's Microsoft sign-in (scope blog.write). Interactive: show one of your drafts here. Call it whenever the engineer asks to show, see or open the preview, to show it here, or what the draft looks like (for example: "show me the preview", "show it here", "can I see the draft", "open the preview", "what does it look like"). A read: the draft as techfabric.com renders it, with its last checks (each marked as one the engineer may publish past or one that must pass) and whether Publish may run, rendered inline as the draft app where the host shows MCP Apps. In any host its text starts with the preview link: show it to the engineer. Never fetch the preview link yourself or rebuild the page as an artifact or HTML: this is the preview.

    Annotations the server declares

    • title: Preview your draft
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write6
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out7
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:48 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
27
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://www.techfabric.com/.well-known/oauth-protected-resource/mcp
Authorization servers
https://www.techfabric.com
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
yes
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 27 tools that change things (3 destructive, 24 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://www.techfabric.com/mcp: tools/list returned 36 tools to an anonymous client, including update_draft (destructive), publish_draft (destructive), apply_edits (destructive), explore_post (write), assess_databricks_readiness (write) and 22 more

    What this check looks for

Posture changes

  1. Oct 29, 2026
    • Tools that change things, listed without credentials: 15 to 27

Findings

Matches of fixed checks, with the text they matched.

8 warn
  • The server marks "explore_post" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "explore_post" says "post": a word for a change.

    What this check looks for
  • The server marks "get_brief" as not read-only (readOnlyHint: false), and its words say it reads.

    Matched text

    annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "get_brief" says "get": a word for reading.

    What this check looks for
  • The server marks "get_status" as not read-only (readOnlyHint: false), and its words say it reads.

    Matched text

    annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The name "get_status" says "get": a word for reading.

    What this check looks for
  • The server marks "start_post" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "start_post" says "start": a word for a change.

    What this check looks for
  • The server marks "social_post_kit" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "social_post_kit" says "post": a word for a change.

    What this check looks for
  • The server marks "reddit_post_kit" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "reddit_post_kit" says "post": a word for a change.

    What this check looks for
Show 2 more findings
  • The server marks "post_performance" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "post_performance" says "post": a word for a change.

    What this check looks for
  • The server marks "suggest_links_and_topics" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "suggest_links_and_topics" says "link": a word for a change.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools2 added, 7 changed.+2 added~7 changedView diff
  2. PostureRemote posture changed. Tools that change things, listed without credentials: 15 -> 27.View diff
    • Tools that change things, listed without credentials: 15 to 27
  3. Tools1 added, 9 changed.+1 added~9 changedView diff
  4. Tools5 changed.~5 changedView diff
  5. Tools4 added, 6 changed.+4 added~6 changedView diff
  6. Tools7 added, 3 changed.+7 added~3 changedView diff
  7. Tools8 added, 13 changed.+8 added~13 changedView diff

Install

Pinned to version 1.6.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http techfabric https://www.techfabric.com/mcp
claude mcp add --transport http techfabric https://www.techfabric.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__techfabric__search",
      "mcp__techfabric__get_page",
      "mcp__techfabric__list_posts",
      "mcp__techfabric__get_services",
      "mcp__techfabric__compare_case_studies",
      "mcp__techfabric__list_drafts",
      "mcp__techfabric__preview_draft",
      "mcp__techfabric__preview_diagram",
      "mcp__techfabric__get_brief_pool"
    ],
    "ask": [
      "mcp__techfabric__explore_post",
      "mcp__techfabric__assess_databricks_readiness",
      "mcp__techfabric__quiz_me",
      "mcp__techfabric__visualize",
      "mcp__techfabric__get_brief",
      "mcp__techfabric__lint_draft",
      "mcp__techfabric__check_draft",
      "mcp__techfabric__submit_draft",
      "mcp__techfabric__get_status",
      "mcp__techfabric__review_before_publishing",
      "mcp__techfabric__revise_post",
      "mcp__techfabric__start_post",
      "mcp__techfabric__check_outline",
      "mcp__techfabric__propose_edits",
      "mcp__techfabric__ask_author",
      "mcp__techfabric__social_post_kit",
      "mcp__techfabric__lint_social",
      "mcp__techfabric__reddit_post_kit",
      "mcp__techfabric__post_performance",
      "mcp__techfabric__suggest_links_and_topics",
      "mcp__techfabric__propose_brief",
      "mcp__techfabric__open_editor",
      "mcp__techfabric__request_image_upload",
      "mcp__techfabric__place_image"
    ],
    "deny": [
      "mcp__techfabric__update_draft",
      "mcp__techfabric__publish_draft",
      "mcp__techfabric__apply_edits"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as techfabric. Review it before you use it.

Capability tags behind 11 rules
  • mcp__techfabric__search untrusted-input
  • mcp__techfabric__get_page untrusted-input
  • mcp__techfabric__list_posts untrusted-input
  • mcp__techfabric__get_services untrusted-input
  • mcp__techfabric__explore_post outbound
  • mcp__techfabric__publish_draft untrusted-input, outbound
  • mcp__techfabric__revise_post outbound
  • mcp__techfabric__start_post outbound
  • mcp__techfabric__social_post_kit outbound
  • mcp__techfabric__reddit_post_kit outbound
  • mcp__techfabric__post_performance untrusted-input, outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.techfabric/techfabric/verify?hash=b8bf11770c4a293171607450c62d2d9aeafd88c564cf3e4cfe0cf317e4196203" | jq -e '.changed == false'

Pinned hash b8bf11770c4a, from Nov 9, 2026, 17:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.techfabric/techfabric/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.techfabric/techfabric
[![Anlyon Radar](https://radar.anlyon.com/badge/com.techfabric/techfabric.svg)](https://radar.anlyon.com/servers/com.techfabric/techfabric)

Source: MCP Registry · repository. Synced Oct 27, 2026, 19:17 UTC.

TechFabric MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the TechFabric MCP server safe?

No scan can promise that. What its definitions show: 36 tools, 27 of which can change, send or delete something, and 8 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the TechFabric MCP server delete data?

Yes. 3 tools can delete, cancel or revoke something: update_draft, publish_draft and apply_edits.

Can the TechFabric MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the TechFabric MCP server have?

36 tools: 3 destructive, 24 write, 9 read. update_draft, publish_draft, apply_edits, explore_post, assess_databricks_readiness, quiz_me, visualize, get_brief and 28 more.

Does the TechFabric MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the TechFabric MCP server send data to outside services?

7 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): explore_post, publish_draft, revise_post, start_post, social_post_kit, reddit_post_kit and 1 more.

Has the TechFabric MCP server changed its tools?

Yes, 6 times since Anlyon Radar started tracking it, most recently on Nov 9, 2026. Every change is on this page and in its Atom feed.