directory.tangent/tangent

Est-ce que directory.tangent/tangent est sûr ?

Au dernier audit MCP Hub, le serveur MCP « directory.tangent/tangent » 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 10 outils

• browse_vertical≈ 1010 tokens

  The newest resources in one section: inspiration, components, motion, build, visuals, tools or learn. Use it to browse without a query, with the same filters as search_resources and cursor paging. Example: {"vertical": "components", "technology": "react", "limit": 20}

  Paramètres, retour & exemple (8)

  Paramètres

  • type · string · optionnel
    Resource type, e.g. "website", "product", "library", "tool", "gallery", "article".
  • limit · integer · optionnel
    Results per page (1 to 50, default 20).
  • cursor · string · optionnel
    next_cursor from the previous call, with the same query and filters. Omit for the first page.
  • pricing · string · optionnel · free | freemium | paid | open_source
    Pricing model.
  • category · string · optionnel
    Category slug or name, e.g. "finance", "component-libraries", "typography".
  • vertical · string · requis
    Section: "inspiration", "components", "motion", "build", "visuals", "tools" or "learn".
  • technology · string · optionnel
    Technology slug or name, e.g. "react", "tailwind-css", "three-js".
  • open_source · boolean · optionnel
    true: only open-source resources; false: only ones known not to be.

  Exemple d'appel

  {"name": "browse_vertical", "arguments": {"vertical": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"results": [], "vertical": "texte", "next_cursor": "texte", "ignored_filters": []}}

• find_inspiration≈ 979 tokens

  Turns a design brief into a short list of references (default 8, at most 10), each with `why` it fits: the pattern, style, category, technology or platform it shares with the brief, or how search matched it (e.g. "similar meaning"). It reads the brief against Tangent's taxonomy and synonyms and combines that with search; no AI calls. Use it when someone describes a screen or product they are about to design. `interpreted_as` shows how the brief was read. Example: {"brief": "onboarding for a fintech app, playful but clean", "platform": "mobile"}

  Paramètres, retour & exemple (3)

  Paramètres

  • brief · string · requis
    What you are designing, in plain words, e.g. "onboarding for a fintech app, playful but clean".
  • limit · integer · optionnel
    How many picks (1 to 10, default 8).
  • platform · string · optionnel
    Prefer resources for this platform: "web", "mobile" or "desktop".

  Exemple d'appel

  {"name": "find_inspiration", "arguments": {"brief": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"brief": "texte", "results": [], "interpreted_as": []}}

• get_pattern≈ 795 tokens

  One UI pattern: its definition, its best examples, related patterns and the technologies the examples use. Use it before designing that pattern. Example: {"slug": "empty-state", "limit": 8}

  Paramètres, retour & exemple (2)

  Paramètres

  • slug · string · requis
    Pattern slug, e.g. "command-menu" or "empty-state".
  • limit · integer · optionnel
    How many examples to return (1 to 60, default 12).

  Exemple d'appel

  {"name": "get_pattern", "arguments": {"slug": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"name": "texte", "slug": "texte", "summary": "texte", "examples": [], "definition": "texte", "tangent_url": "texte", "technologies": [], "related_patterns": []}}

• get_person≈ 1085 tokens

  One person's profile: role, bio, website, social links, studios, what their site is built with (confirmed technologies) and their work on Tangent. Set include_image to also get a small preview of their site. Example: {"slug": "emil-kowalski"}

  Paramètres, retour & exemple (2)

  Paramètres

  • slug · string · requis
    Person slug, e.g. "rauno-freiberg".
  • include_image · boolean · optionnel
    Also attach a small WebP thumbnail (under ~100 KB) as an image block. Off by default to save tokens.

  Exemple d'appel

  {"name": "get_person", "arguments": {"slug": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"bio": "texte", "name": "texte", "role": "texte", "slug": "texte", "work": [], "links": [], "studios": [], "website": "texte", "added_at": "texte", "site_url": "texte", "image_url": "texte", "avatar_url": "texte"}}

• get_resource≈ 1558 tokens

  Everything Tangent knows about one resource: descriptions, taxonomy, editorial notes, the people behind it, and its related resources (tangents) with reasons. Use it to go deeper on a search pick. Set include_image to also get a small screenshot. Example: {"slug": "linear"}

  Paramètres, retour & exemple (2)

  Paramètres

  • slug · string · requis
    Resource slug, e.g. "linear".
  • include_image · boolean · optionnel
    Also attach a small WebP thumbnail (under ~100 KB) as an image block. Off by default to save tokens.

  Exemple d'appel

  {"name": "get_resource", "arguments": {"slug": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"url": "texte", "name": "texte", "slug": "texte", "tags": [], "type": "texte", "notes": [], "domain": "texte", "people": [], "styles": [], "license": "texte", "pricing": "texte", "studios": []}}

• list_patterns≈ 261 tokens

  Every UI and interaction pattern resources are filed under (Command Menu, Onboarding, Empty State and more), with example counts. Use it to pick a slug for get_pattern. Example: {}

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "list_patterns", "arguments": {}}

  Exemple de retour

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

• list_people≈ 628 tokens

  Designers and design engineers in the catalogue, featured first, then by name, with optional technology and role filters and cursor paging. Use search_people to find someone by name or focus. Example: {"role": "design engineer", "technology": "nextjs", "limit": 20}

  Paramètres, retour & exemple (4)

  Paramètres

  • role · string · optionnel
    Words in their role, e.g. "design engineer" or "product designer".
  • limit · integer · optionnel
    Results per page (1 to 50, default 20).
  • cursor · string · optionnel
    next_cursor from the previous call, with the same query and filters. Omit for the first page.
  • technology · string · optionnel
    Only people whose site is built with this technology, e.g. "nextjs", "astro", "framer".

  Exemple d'appel

  {"name": "list_people", "arguments": {"role": "texte", "limit": 1, "cursor": "texte", "technology": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"results": [], "next_cursor": "texte"}}

• related_resources≈ 686 tokens

  Resources related to one resource, each with the reason (e.g. "shares Command Menu", "same maker"). Use it to follow tangents from a site you like. Example: {"slug": "stripe"}

  Paramètres, retour & exemple (1)

  Paramètres

  • slug · string · requis
    Resource slug, e.g. "stripe".

  Exemple d'appel

  {"name": "related_resources", "arguments": {"slug": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"slug": "texte", "results": []}}

• search_people≈ 655 tokens

  Find designers and design engineers by name, role, focus or stack, ranked, with optional technology and role filters. Example: {"query": "motion", "role": "design engineer"}

  Paramètres, retour & exemple (5)

  Paramètres

  • role · string · optionnel
    Words in their role, e.g. "design engineer" or "product designer".
  • limit · integer · optionnel
    Results per page (1 to 50, default 10).
  • query · string · requis
    Name, role, focus or stack, e.g. "motion" or "Rauno".
  • cursor · string · optionnel
    next_cursor from the previous call, with the same query and filters. Omit for the first page.
  • technology · string · optionnel
    Only people whose site is built with this technology, e.g. "nextjs", "astro", "framer".

  Exemple d'appel

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

  Exemple de retour

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

• search_resources≈ 1137 tokens

  Ranked search over Tangent's catalogue of design and design-engineering resources (sites, products, component libraries, tools, articles). Use it when you know roughly what you want; narrow with vertical, category, technology, type, pricing or open_source, and page with cursor. For a whole brief, use find_inspiration. Example: {"query": "command menu", "technology": "react", "limit": 5}

  Paramètres, retour & exemple (9)

  Paramètres

  • type · string · optionnel
    Resource type, e.g. "website", "product", "library", "tool", "gallery", "article".
  • limit · integer · optionnel
    Results per page (1 to 50, default 10).
  • query · string · requis
    What to look for, e.g. "command menu" or "dark dashboard".
  • cursor · string · optionnel
    next_cursor from the previous call, with the same query and filters. Omit for the first page.
  • pricing · string · optionnel · free | freemium | paid | open_source
    Pricing model.
  • category · string · optionnel
    Category slug or name, e.g. "finance", "component-libraries", "typography".
  • vertical · string · optionnel
    Section: "inspiration", "components", "motion", "build", "visuals", "tools" or "learn".
  • technology · string · optionnel
    Technology slug or name, e.g. "react", "tailwind-css", "three-js".
  • open_source · boolean · optionnel
    true: only open-source resources; false: only ones known not to be.

  Exemple d'appel

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

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"query": "texte", "results": [], "next_cursor": "texte", "related_terms": [], "ignored_filters": []}}

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://tangent.directory/api/mcp