com.techfabric/techfabric

Est-ce que com.techfabric/techfabric est sûr ?

Au dernier audit MCP Hub, le serveur MCP « com.techfabric/techfabric » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 9 outils

• check_draft≈ 786 tokens

  Requires a TechFabric engineer's Microsoft sign-in (scope blog.write); an anonymous call is answered with the sign-in challenge. Run techfabric.com's readiness checks (the browser editor's own: the draft's items and every site gate, model-read ones by Clef) on a post's Markdown, with its frontmatter. Files nothing. A full check takes about five to ten minutes: a client with the tasks extension gets a task to poll; otherwise this waits up to wait_seconds, then returns progress, and the same markdown and images again reads on (nothing runs twice). Returns each item's status and findings, with the passage each finding is about.

  Paramètres, retour & exemple (3)

  Paramètres

  • images · array · optionnel
  • markdown · string · requis
    The whole post: frontmatter (title, description at least) and body
  • wait_seconds · integer · optionnel
    Without the tasks extension: how long to wait for the result before answering with progress (default 25)

  Exemple d'appel

  {"name": "check_draft", "arguments": {"markdown": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"run": "texte", "next": "texte", "note": "texte", "error": "texte", "items": [], "ready": true, "stage": "texte", "status": "running", "failing": [], "missing": [], "check_id": "texte", "could_not_run": []}}

• get_brief≈ 634 tokens

  Requires a TechFabric engineer's Microsoft sign-in (scope blog.write); an anonymous call is answered with the sign-in challenge. Today's topic for a daily draft, claimed for the signed-in engineer for 24 hours: a news story the content agent picked in the last two days, or a search we don't answer yet that matches the engineer's own work. Returns the topic, the angle, why it was chosen, the target search, sources, internal links to use, the editorial_rules URI and the brief_id to pass to submit_draft. Asking again the same day returns the same brief. When techfabric.com's pace (one automated post a day, three a week) is used up, today's brief has gone to a colleague, or nothing fits, it answers status none with the reason: stop there. No model is called. Ask the engineer for first-hand detail; never invent it.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "get_brief", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"day": "texte", "kind": "news", "next": "texte", "angle": "texte", "steps": [], "topic": "texte", "author": {}, "reason": "texte", "status": "claimed", "sources": [], "brief_id": "texte", "first_hand": "texte"}}

• get_page≈ 465 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • url_or_slug · string · requis
    A techfabric.com URL, a path such as /services/databricks, or a post's slug

  Exemple d'appel

  {"name": "get_page", "arguments": {"url_or_slug": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"url": "texte", "date": "texte", "faqs": [], "tags": [], "type": "post", "title": "texte", "author": "texte", "updated": "texte", "markdown": "texte", "canonical": "texte", "metaTitle": "texte", "description": "texte"}}

• get_services≈ 300 tokens

  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.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "get_services", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"total": 1, "indexes": [], "services": []}}

• get_status≈ 784 tokens

  Requires a TechFabric engineer's Microsoft sign-in (scope blog.write); an anonymous call is answered with the sign-in challenge. One of your own drafts: its state, what is failing, the last check run, its current Markdown and base_sha (for update_draft), and the preview link. Never the editor link, which can publish: the engineer has it by email, and publishes from there. When the writer is waiting on a fact only you have, this asks you for it first.

  Paramètres, retour & exemple (1)

  Paramètres

  • id · string · requis
    The idea id

  Exemple d'appel

  {"name": "get_status", "arguments": {"id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"id": "texte", "next": "texte", "note": "texte", "draft": {}, "state": "texte", "title": "texte", "byline": "texte", "meaning": "texte", "last_check": {}}}

• list_posts≈ 366 tokens

  TechFabric's blog posts, newest first, optionally only those with a tag, by an author, or dated on or after a day.

  Paramètres, retour & exemple (4)

  Paramètres

  • tag · string · optionnel
    Only posts with this tag (its name or slug, e.g. Databricks)
  • limit · integer · optionnel
    How many posts (default 20)
  • since · string · optionnel
    Only posts dated on or after this day, YYYY-MM-DD
  • author · string · optionnel
    Only posts by this author (name or slug, e.g. Preetham Reddy)

  Exemple d'appel

  {"name": "list_posts", "arguments": {"tag": "texte", "limit": 1, "since": "texte", "author": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"posts": [], "total": 1}}

• search≈ 437 tokens

  Search TechFabric's published site: blog posts, service and solution pages, case studies, city pages and events. Returns each match's title, URL, summary, date, author and type, best first. Read a result in full with get_page.

  Paramètres, retour & exemple (3)

  Paramètres

  • type · string · optionnel · post | service | solution | case_study | city | event | page
    Only this kind of page: post, service, solution, case_study, city, event or page
  • limit · integer · optionnel
    How many results (default 10)
  • query · string · requis
    What to look for, in plain words

  Exemple d'appel

  {"name": "search", "arguments": {"query": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"type": "texte", "query": "texte", "total": 1, "results": []}}

• submit_draft≈ 501 tokens

  Requires a TechFabric engineer's Microsoft sign-in (scope blog.write); an anonymous call is answered with the sign-in challenge. File a post into techfabric.com's blog pipeline under the signed-in engineer's own byline. The post, frontmatter required (title and description at least), becomes the draft exactly as sent (no model rewrites or fact-checks it; your agent writes, repairs and checks the facts): the site renders its diagrams, puts its images in blog media, builds the preview and emails it with the editor and approve links. Run check_draft first; what the draft still lacks comes back as findings. Never publishes. Returns the idea id; a client with the tasks extension gets a task that completes when the preview is up.

  Paramètres, retour & exemple (4)

  Paramètres

  • title · string · requis
    The post's working title
  • images · array · optionnel
  • brief_id · string · optionnel
    The brief_id get_brief returned, when the post is from today's brief: it marks the brief done
  • markdown · string · requis
    The whole post, with its frontmatter (title, description at least): it becomes the draft as sent

  Exemple d'appel

  {"name": "submit_draft", "arguments": {"title": "texte", "markdown": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• update_draft≈ 301 tokens

  Requires a TechFabric engineer's Microsoft sign-in (scope blog.write); an anonymous call is answered with the sign-in challenge. Save a new version of one of your own drafts, as the browser editor's Save does: only while it waits on you (state drafted), only on top of the version you edited (base_sha from get_status), and never while it is open in the browser editor. The job commits it and rebuilds the preview; it runs no checks (check_draft does, and the engineer's Run checks in the editor is what Publish needs). Never publishes.

  Paramètres, retour & exemple (3)

  Paramètres

  • id · string · requis
    The idea id
  • base_sha · string · requis
    draft.base_sha from get_status: the version your edit started from
  • markdown · string · requis
    The whole post, with its frontmatter

  Exemple d'appel

  {"name": "update_draft", "arguments": {"id": "texte", "base_sha": "texte", "markdown": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://www.techfabric.com/mcp