MCP servers › com.techfabric › techfabric

MCP server · registry snapshot 2026-10-24 · last tested 2026-10-24

com.techfabric/techfabric

For TechFabric engineers to write posts and case studies from their coding agent; anyone can read — the publisher's description

4 of 5 record checks metRead-only · tools listed 2026-10-24Topic: developer-tools · AI-classifiedversion 1.4.0streamable HTTP33 tools

Summary

com.techfabric/techfabric is a remote MCP server listed in the official MCP registry at version 1.4.0. On 2026-10-24 ProtocolProbe connected to it in read-only mode and read its inventory: 33 tools, 353 resources and 16 prompts.

Record checks

4 of 5 record checks met · 4 do not apply

met: Registry entry is active and says how to run it
met: Source repository link opens
met: Repository is not archived
met: Code pushed to the repository in the 90 days before our check
not met: Repository publishes a security policy (SECURITY.md)
not applicable: Package names its licence with a standard (SPDX) identifier
not applicable: The version the registry lists can be installed and is not withdrawn
not applicable: npm package carries build provenance (attestation)
not applicable: No known critical or high advisory in the package or its dependencies

Not ranked by downloads: a remote server publishes no download figure
Not ranked by stars: 0 stars (ranked from 10)

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Key facts

Runs: remote (hosted by the publisher)
Transport: streamable HTTP
Sign-in: none needed to open a session
Repository: public
Tools: 33
Topic: developer-toolsAI-classified
Last tested: 2026-10-24

Add to your client

Observed fact

This server accepted a session without any credential and lists 4 tools whose name or declaration suggests they change data (update_draft, publish_draft, revise_post, apply_edits). That is our reading of the names; we did not call them. Source: our connection, 2026-10-24.

How fresh this is

Live-tested

yes, a real session (not a text-only review)

Last tested

2026-10-24

Mode

read-only (no tool calls)

Latest version

1.4.0, published 2026-10-23 (registry, as of the 2026-10-24 snapshot)

First listed version

2026-10-19 (earliest version still in the registry; older removed versions would be earlier)

Version history

6 versions listed, 2026-10-19 to 2026-10-23; 6 in the 90 days before the 2026-10-24 snapshot.

Most recent 6 versions

1.4.0 · 2026-10-23
1.3.1 · 2026-10-22
1.3.0 · 2026-10-20
1.2.0 · 2026-10-19
1.1.0 · 2026-10-19
1.0.0 · 2026-10-19

(versions still listed in the registry only)

Registry data

snapshot 2026-10-24

Package and repository

checked 2026-10-24

Engine

mcp-runtime-engine@0.1.0 · sdk@1.32.0

Changes since the last refresh

Version 1.3.1 (published 2026-10-22) → 1.4.0 (published 2026-10-23), between the registry lists of 2026-10-23 and 2026-10-24.

The publisher published no GitHub release note for this version: its repository publishes no GitHub releases.

Source: the official MCP Registry list on 2026-10-23 and on 2026-10-24; release notes from the GitHub Releases API, checked 2026-10-24.

What it is

What does this server offer?

Observed inventory

33tools

353resources

16prompts

None of its 33 tools are described as changing anything. For 33 the reading was uncertain, so no mark is shown.

searchon 763 other servers
“Search TechFabric's published site: blog posts, service and solution pages, case studies, city pages and events.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
3 inputs, 1 required
- querystringrequired“What to look for, in plain words”
- typestring“Only this kind of page: post, service, solution, case_study, city, event or page”
- limitinteger“How many results (default 10)”
get_pageon 100 other servers
“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.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input, 1 required
- url_or_slugstringrequired“A techfabric.com URL, a path such as /services/databricks, or a post's slug”
list_postson 36 other servers
“TechFabric's published blog posts, newest first, optionally only those with a tag, by an author, or dated on or after a day.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
4 inputs
- tagstring“Only posts with this tag (its name or slug, e.g.”
- authorstring“Only posts by this author (name or slug, e.g.”
- sincestring“Only posts dated on or after this day, YYYY-MM-DD”
- limitinteger“How many posts (default 20)”
get_serviceson 42 other servers
“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.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
Takes no inputs.
explore_post
“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, wit…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs, 1 required
- poststringrequired“A post or case study: its URL, path or slug (case studies as case-studies/<slug>), or the topic to find one on”
- diagraminteger“Which of its diagrams, when it has more than one (default 1)”
compare_case_studies
“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…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs
- case_studiesarray“Two or three case studies: each a slug (funko, canvass), a URL, or words of its title.”
- topicstring“Instead of case_studies: the closest case studies to this, up to three”
assess_databricks_readiness
“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 tea…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
3 inputs
- answersobject“The reader's answers, { question id: option value } (the first call lists both).”
- contactboolean“The reader asked to talk to TechFabric about the readout: a client that can opens /contact for them to confirm (a URL elicitation)”
- formboolean“false: never ask in a form; return the questions as text”
quiz_meon 1 other server
“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 quest…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
3 inputs, 1 required
- poststringrequired“A post with FAQs: its URL or slug, or the topic to find one on”
- answersarray“The reader's answers, one per question in order: a letter (A to D) or a 0-based index.”
- formboolean“false: never ask in a form; return the questions as text”
visualizeon 1 other server
“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.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
3 inputs, 1 required
- documentstring or arrayrequired“The answer as A2UI v0.9.1 messages: JSONL (one JSON message a line) or a JSON array.”
- titlestring“The card's title (default: the document's first heading)”
- sourcesarray“The techfabric.com URLs whose facts the answer uses (from search or get_page); only this site's pages are cited”
get_briefon 20 other servers
“Requires a TechFabric engineer's Microsoft sign-in (scope blog.write).”
Publisher declares: read-only no · destructive no · idempotent yes · open-world no
Takes no inputs.
lint_drafton 1 other server
“Requires a TechFabric engineer's Microsoft sign-in (scope blog.write).”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
7 inputs
- markdownstring“The whole post: frontmatter (title, description at least) and body”
- idstring“A draft of yours (the id submit_draft returned).”
- rubricboolean“Also return judge_rubric while checks still fail (it comes anyway once they pass)”
- imagesarray“The images the post refers to by name (names only; no data needed)”
- kindstring“What the draft is: "post" (the default, a blog post) or "case-study" (content/case-studies, at /case-studies/<slug>).”
- sourcesstring“The engineer's own words the draft's claims come from, as text.”
- slugstring“The draft's slug, when it has one already (get_status draft.slug); otherwise it comes from the title”
check_drafton 5 other servers
“Requires a TechFabric engineer's Microsoft sign-in (scope blog.write).”
Publisher declares: read-only no · destructive no · idempotent yes · open-world no
11 inputs
- markdownstring“The whole post: frontmatter (title, description at least) and body.”
- idstring“A draft of yours (the idea id from submit_draft): checks its saved text, the final verification publish_draft needs”
- imagesarray
- kindstring“What the draft is: "post" (the default, a blog post) or "case-study" (content/case-studies, at /case-studies/<slug>).”
- sourcesstring“The engineer's own words the draft's claims come from, as text.”
- client_confirmedboolean“Only when the engineer tells you they have the client's confirmation to name the client this draft names (its client:, or a client in its text the register doe…”
- first_handarray“First-hand claims only the engineer can source, which the fact-check flagged first_hand (first_hand_to_confirm): each the sentence exactly as quoted, with what…”
- first_hand_allboolean“Confirm all listed: true asks the engineer to confirm, in one go, every first-hand claim the last check of this text listed (first_hand_to_confirm), instead of…”
- first_hand_confirmationstring“Only after asking the engineer and hearing yes: the confirmation an earlier answer gave for exactly this first_hand (first_hand.confirmation).”
- confirm_viastring“With first_hand or first_hand_all: how the engineer is asked.”
- wait_secondsinteger“Without the tasks extension: how long to wait for the result before answering with progress (default and most 25; a larger value, accepted for older agents, wa…”

Show 21 more tools

submit_drafton 1 other server
“Requires a TechFabric engineer's Microsoft sign-in (scope blog.write).”
Publisher declares: read-only no · destructive no · idempotent yes · open-world no
10 inputs, 2 required
- titlestringrequired“The post's working title”
- markdownstringrequired“The whole post, with its frontmatter (title, description at least): it becomes the draft as sent”
- imagesarray
- kindstring“What the draft is: "post" (the default, a blog post) or "case-study" (content/case-studies, at /case-studies/<slug>).”
- sourcesstring“The engineer's own words the draft's claims come from, as text.”
- client_confirmedboolean“Only when the engineer tells you they have the client's confirmation to name the client this draft names (its client:, or a client in its text the register doe…”
- first_handarray“First-hand claims only the engineer can source, which the fact-check flagged first_hand (first_hand_to_confirm): each the sentence exactly as quoted, with what…”
- brief_idstring“The brief_id get_brief returned, when the post is from today's brief: it marks the brief done”
- from_ideastring“The id of an idea the engineer emailed that is waiting for their own agent (get_status says so): the post continues it, and that idea is closed in its favour”
- from_idea_notesstring“With from_idea: the author_notes_hash get_status returned for it, so an email they sent since is never closed unread”
update_drafton 12 other servers
“Requires a TechFabric engineer's Microsoft sign-in (scope blog.write).”
Publisher declares: read-only no · destructive yes · idempotent no · open-world no
9 inputs, 2 required
- idstringrequired“The idea id”
- markdownstringrequired“The whole post, with its frontmatter”
- base_hashstring“The hash of the version your edit started from: draft.base_hash from the get_status you edited from, or the text_hash your last update_draft returned.”
- app_instancestring“The draft app only, never an agent: the view whose own unsaved edits this save is”
- base_shastring“Instead of base_hash: draft.base_sha from get_status, the commit your edit started from”
- kindstring“Optional: the draft's kind, which is fixed when it is submitted.”
- sourcesstring“New sources, replacing the ones sent before: the engineer's own words, which the fact-check reads a post's claims against, or a case study's numbers are checke…”
- client_confirmedboolean“Only when the engineer tells you they have the client's confirmation to name the client this draft names (its client:, or a client in its text the register doe…”
- first_handarray“First-hand claims only the engineer can source, which the fact-check flagged first_hand (first_hand_to_confirm): each the sentence exactly as quoted, with what…”
list_draftson 11 other servers
“Requires a TechFabric engineer's Microsoft sign-in (scope blog.write).”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
8 inputs
- statestring“Only drafts in this state: writing, preview_building, question_for_you, drafted, checking, checks_failing, ready_to_publish, publishing, published, stuck, clos…”
- kindstring“Only this kind: post, case-study, or revision (of a live post).”
- created_afterstring“Only drafts created at or after this: a date (YYYY-MM-DD, midnight UTC) or an ISO 8601 time with its offset.”
- created_beforestring“Only drafts created before this (not at it): a date (YYYY-MM-DD, midnight UTC) or an ISO 8601 time”
- allboolean“The blog's editor only: everyone's drafts, not just yours.”
- staleboolean“The site owner only, his owner queue: everyone's drafts with nothing from their author for more than two days (stuck, a question for them, held, drafted or fai…”
- limitinteger“How many to return, newest first (default 20)”
- cursorstring“The next_cursor from the previous page, with the same filters”
get_statuson 93 other servers
“Requires a TechFabric engineer's Microsoft sign-in (scope blog.write).”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
1 input, 1 required
- idstringrequired“The idea id”
review_before_publishing
“Requires a TechFabric engineer's Microsoft sign-in (scope blog.write).”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs, 1 required
- idstringrequired“The idea id of your own draft”
- overridearray“Publish anyway: the failing check ids the engineer chooses to publish past (only wording and style checks).”
publish_drafton 2 other servers
“Requires a TechFabric engineer's Microsoft sign-in (scope blog.write).”
Publisher declares: read-only no · destructive yes · idempotent no · open-world yes
4 inputs, 1 required
- idstringrequired“The idea id of your own draft”
- confirmationstring“Only on the second call: the confirmation the first call returned, sent back after the engineer said yes”
- overridearray“Publish anyway: the failing check ids (as check_draft reports them, such as gate:buyer) the engineer chooses to publish past.”
- confirm_viastring“How the engineer is asked.”
preview_drafton 2 other servers
“Requires a TechFabric engineer's Microsoft sign-in (scope blog.write).”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
3 inputs, 1 required
- idstringrequired“The idea id”
- instancestring“The draft app only: its view's own id, with editing”
- editingboolean“The draft app only, never an agent: true while the engineer has unsaved edits in its Edit tab (takes or renews the app's edit hold), false when they save, disc…”
revise_post
“Requires a TechFabric engineer's Microsoft sign-in (scope blog.write).”
Publisher declares: read-only no · destructive no · idempotent yes · open-world no
1 input, 1 required
- poststringrequired“The live post to change: its URL (https://www.techfabric.com/blog/<slug>) or its slug”
start_post
“Requires a TechFabric engineer's Microsoft sign-in (scope blog.write).”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
6 inputs
- kindstring“What the engineer is writing: "post" (the default), "case-study", or "explainer" (a post on news or a feature; submit it as kind "post").”
- topicstring“What it is about, in the engineer's words.”
- briefboolean“Tailor the questions to the brief the engineer holds today (get_brief claims one; this only reads it).”
- suggestedobject“Your suggested answer to each question, by its id, from the repository and the engineer's notes: shown to them to confirm or correct, never sent as their words.”
- answersobject“The engineer's own answers, by question id, word for word, once they've given them in chat: returned as sources for submit_draft.”
- formboolean“false: never show the form; return the questions to ask in chat.”
check_outline
“Requires a TechFabric engineer's Microsoft sign-in (scope blog.write).”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
9 inputs, 2 required
- kindstring
- titlesarrayrequired“Two or three title options, each one clause naming the subject.”
- meta_titlestring“A search title of 60 characters or fewer, only when a title runs longer.”
- openingstring“The opening's first two sentences: the way this story opens (a device the last ten posts left free: editorial/voices-of-techfabric.md), with one concrete detai…”
- sectionsarrayrequired“Four to six for a post; Challenge, Strategy, Solution and Results for a case study.”
- diagramstring“What the diagram draws, step by step, and its point.”
- faqsarray“Three or more questions a reader would search for.”
- readerstring“Who the post is for.”
- unattendedboolean“true in a scheduled run with nobody to approve the outline: a passing outline goes straight to drafting.”
propose_edits
“Requires a TechFabric engineer's Microsoft sign-in (scope blog.write).”
Publisher declares: read-only no · destructive no · idempotent yes · open-world no
4 inputs, 3 required
- idstringrequired“The draft's id”
- base_hashstringrequired“The saved text's hash the changes are against: draft.base_hash from get_status, or your last save's text_hash”
- changesarrayrequired
- askboolean“true: ask the engineer about each change in a form, where the client shows one (when no draft app is showing)”
apply_editson 6 other servers
“Requires a TechFabric engineer's Microsoft sign-in (scope blog.write).”
Publisher declares: read-only no · destructive yes · idempotent no · open-world no
4 inputs, 3 required
- idstringrequired“The draft's id”
- proposal_idstringrequired“The proposal's id, from propose_edits”
- acceptarrayrequired“The ids of the changes the engineer accepted”
- rejectarray“The ids of the changes the engineer rejected”
ask_author
“Requires a TechFabric engineer's Microsoft sign-in (scope blog.write).”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
4 inputs, 2 required
- idstringrequired“The draft's id”
- questionstringrequired“One question only the engineer can answer, in plain words”
- passagestring“The sentence or section it is about, when there is one”
- answerstring“The engineer's answer, word for word, when you asked them in chat”
social_post_kit
“Requires a TechFabric engineer's Microsoft sign-in (scope blog.write).”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input, 1 required
- poststringrequired“A published post on techfabric.com: its URL (https://www.techfabric.com/blog/<slug>) or its slug”
lint_social
“Requires a TechFabric engineer's Microsoft sign-in (scope blog.write).”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs, 1 required
- textstringrequired“The LinkedIn post's text, as the engineer would post it (at most 10000 characters)”
- poststring“The published post it shares (its URL or slug): the text is checked for its link”
reddit_post_kit
“Requires a TechFabric engineer's Microsoft sign-in (scope blog.write).”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
5 inputs, 1 required
- subredditstringrequired“The subreddit the post or answer is for”
- poststring“A published post on techfabric.com the Reddit post draws on: its URL or its slug.”
- notesstring“The engineer's own notes about the problem, what they tried, what worked and their numbers (at most 8000 characters).”
- threadstring“The Reddit thread being answered, if this is an answer: its URL.”
- draftobject“The draft to check: the result then carries lint.”
post_performanceon 2 other servers
“Requires a TechFabric engineer's Microsoft sign-in (scope blog.write).”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
1 input
- poststring“One of your published posts: its URL (https://www.techfabric.com/blog/<slug>) or its slug.”
suggest_links_and_topics
“Requires a TechFabric engineer's Microsoft sign-in (scope blog.write).”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
3 inputs
- markdownstring“The post's text, frontmatter included.”
- idstring“One of your drafts (the id submit_draft returned): its saved text”
- poststring“One of your published posts: its URL (https://www.techfabric.com/blog/<slug>) or its slug”
preview_diagramon 1 other server
“Requires a TechFabric engineer's Microsoft sign-in (scope blog.write).”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input, 1 required
- markdownstringrequired“The whole post, frontmatter included, or one mermaid source.”
get_brief_pool
“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).”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
Takes no inputs.
propose_briefon 1 other server
“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).”
Publisher declares: read-only no · destructive no · idempotent yes · open-world no
6 inputs, 3 required
- topicstringrequired“The post's subject in a few words (8 to 140 characters)”
- whystringrequired“The evidence: the TechFabric work it comes from (a repository, a project, a published post), or the search data (query, monthly volume, who ranks).”
- anglestringrequired“What the post argues or shows, and for which reader”
- sourcesarray
- target_querystring“The search the post should answer, when there is one”
- for_authorstring“An engineer from the author registry, when the work is theirs; leave out to offer it to whoever's work fits”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-24.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

No AI reading was available for this server's tools (the two runs did not agree, or the listing was not reviewed).

Counted from the listing

Parameters with a description: 96% of 123
Tools with a description: 100% of 33
Typical description length: 551 characters

The tool set

Counted from the listing

Tools: 33
Size of the list: about 30,811 tokens for an agent to load (characters ÷ 4)
Naming: 31 of 33 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 0 of 33 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

We connected to this URL on 2026-10-24 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai

Settings → Connectors → Add custom connector, then paste:
https://www.techfabric.com/mcp

Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "techfabric": {
      "url": "https://www.techfabric.com/mcp"
    }
  }
}

VS Code · .vscode/mcp.json

{
  "servers": {
    "techfabric": {
      "type": "http",
      "url": "https://www.techfabric.com/mcp"
    }
  }
}

VS Code (command line) · Bash or zsh terminal (macOS, Linux)

code --add-mcp '{"name":"techfabric","type":"http","url":"https://www.techfabric.com/mcp"}'

Claude Code

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

Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+

npx @modelcontextprotocol/inspector@2.11.0 --server-url https://www.techfabric.com/mcp --transport http

The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Does the registry listing match what we found?

Feature #6

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.

Registry says	We found	Result	Source · date
Remote endpoint www.techfabric.com/mcp	Session opened	matches	our test · 2026-10-24
No credential declared as required	Opened a session without any credential	matches	our test · 2026-10-24
Repository github.com/Fabric-Pro/techfabric-mcp	Opens publicly	matches	api.github.com · 2026-10-24

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace: com.techfabric
GitHub owner: an organization (Fabric-Pro)

Repository: github.com/Fabric-Pro/techfabric-mcp
Stars: 0
Repository age: 0–30 days
Last push: 0–30 days ago
Archived: no
Security policy: none found (we looked for SECURITY.md in the repository and in its owner’s .github repository)

Source: the registry entry and api.github.com · 2026-10-24; security policy read from GitHub · 2026-10-23.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Choosing

Record checks

Public records · not a safety rating

4 of 5 record checks met · 4 do not apply

Not ranked by downloads: a remote server publishes no download figure
Not ranked by stars: 0 stars (ranked from 10)

MetRegistry entry is active and says how to run itActive, with a package or a remote address.
MetSource repository link opensThe linked GitHub repository is public.
MetRepository is not archivedNot archived.
MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
Not metRepository publishes a security policy (SECURITY.md)No SECURITY.md in the places GitHub reads it from.
Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-24. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating. How each check works · Leaderboards

Common questions about com.techfabric/techfabric

Answered from the data above

Is com.techfabric/techfabric safe to install?

We do not rate servers as safe or unsafe. 4 of its 5 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Does com.techfabric/techfabric need an API key or sign-in?

It opened a session without any credential on 2026-10-24. The registry entry declares no required credential; no declaration is not a guarantee.

Has com.techfabric/techfabric been security tested?

Partly. 5 of the 16 checks that apply to it were exercised. It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security verdict is published before verification.

Does com.techfabric/techfabric publish a security policy?

We found no SECURITY.md in its repository (root, .github/ or docs/) or in its owner's .github repository.

Where is the source code of com.techfabric/techfabric?

In github.com/Fabric-Pro/techfabric-mcp, which opens publicly.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Similar servers

Same topic · AI-read

io.github.morluto/reaREAcompare with this one
io.github.ruvnet/claude-flowcompare with this one
io.github.thedaviddias/front-end-checklistFront-End Checklistcompare with this one
io.github.ChromeDevTools/chrome-devtools-mcpChrome DevTools MCPcompare with this one
io.github.secforge/chrome-devtools-mcpChrome DevTools MCPcompare with this one
io.github.DeusData/codebase-memory-mcpCodebase Memorycompare with this one

Active servers whose topic is also “developer-tools”, most GitHub stars first. The topic and the tool kinds are an AI model's reading of the publishers' descriptions, not checked by hand. Similar is not a recommendation.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Open without sign-in

It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-10-24

Inventory: exercised
Hidden instructions: exercised
Real execution: not run · our policy
Secret leak: not run · nothing to check it against
Internal addresses: not run · our policy
Unconfirmed changes: not run · our policy
Bad input: not run · our policy
Model requests: not run · nothing to check it against
Sensitive questions: not run · nothing to check it against
Folder boundary: not run · our policy
Log leaks: not run · nothing to check it against
Hidden content: exercised
Fake assistant turns: exercised
Token passthrough: not applicable
Token audience: not applicable
Sign-in redirect: not run · our policy
Consent handling: not testable from outside
Sign-in metadata: exercised

5 exercised11 not run (reason given)2 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 5 of the 16 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.

Exercised · 5

1Inventory
tool-listReads the declared tools, resources and prompts.exercised
2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised
12Hidden content
audience-hidingChecks resources that hide content from the user.exercised
13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.exercised
18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.exercised

Not run, with the reason · 11

3Real execution
real-executionCalls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
4Secret leak
canary-leakPlants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
5Internal addresses
ssrfChecks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
6Unconfirmed changes
write-without-confirmationChecks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
7Bad input
error-handlingSends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
8Model requests
samplingChecks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
9Sensitive questions
elicitation-sensitive-dataChecks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
10Folder boundary
root-boundaryChecks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
11Log leaks
logging-side-channelChecks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
16Sign-in redirect
open-redirectChecks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
17Consent handling
confused-deputyChecks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside

Does not apply to this server · 2

14Token passthrough
token-passthroughChecks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
15Token audience
token-audience-validationChecks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable

Source: our own test, 2026-10-24, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

0 msStarted a read-only session with the server's remote endpoint
2,307 msConnected after 0 redirects. No credential was sent or needed.
Read the inventory: 33 tools, 353 resources, 16 prompts.
39,452 msFinished: 5 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified

developer-tools

AI-classified · 2026-10-23 · from version 1.3.1 (same title and description)

Pricing modelAI-classified

no value

The pages we read do not state how the product is priced. · from version 1.3.1 (same website)

Programming language

not stated

GitHub detects no source language in this repository (docs-only or empty)

Hosting type

remote (hosted by the publisher)

registry · 2026-10-24

MCP capability

completions, prompts, resources, tools, extensions

our test · 2026-10-24

Transport

streamable HTTP

registry · 2026-10-24

Required credentials

none declared

registry · no declaration is not a guarantee

Package registry

does not apply

remote-only server: no package is shipped, so there is no package registry

Freshness

0–30 days

registry updatedAt · 2026-10-24

Lifecycle status

active

registry · 2026-10-24

License class

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Integrity hash

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Signature / provenance

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Dependency advisories

does not apply

ships no package, so there are no dependencies to audit

Popularity

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Publisher signals

owner: an organization · repository age: 0–30 days · stars: 0–9

api.github.com · 2026-10-24

Maintenance

active

api.github.com · 2026-10-24

Environment

the publisher's infrastructure

where it runs, from the hosting type

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “com.techfabric/techfabric: MCP server record.” Data checked 2026-10-24. https://protocolprobe.com/mcp/servers/com.techfabric/techfabric

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/com.techfabric/techfabric)](https://protocolprobe.com/mcp/servers/com.techfabric/techfabric)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology