io.companygraph/mental-model

Est-ce que io.companygraph/mental-model est sûr ?

Au dernier audit MCP Hub, le serveur MCP « io.companygraph/mental-model » 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 14 outils

• describe_errors≈ 398 tokens

  What a refused call looks like. A tool's output schema covers its answers only, so use this once, to branch on refusals or validate them. No input. Returns `errors`, every `code` with `when` it is raised and the JSON Schema of its `details`, and `schema`, the JSON Schema of a whole refusal: `error` with `code`, `message`, `rule`, `details`, beside `model`.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "describe_errors", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"model": {}, "errors": [], "schema": {}}}

• describe_relations≈ 808 tokens

  What the schemas declare between types: references with form and cardinality, ownership, enums, joins, list kinds. Use for a diagram or audit; for one type's full schema use describe_schema. Optional `type` narrows every list, `direction` (declares, declared-to, both; needs `type`) one side of relations, `via` relations and enums. Returns those lists, with `forms` and `reading` explaining every term. Not paged.

  Paramètres, retour & exemple (3)

  Paramètres

  • via · string · optionnel
  • type · string · optionnel
  • direction · string · optionnel · declares | declared-to | both

  Exemple d'appel

  {"name": "describe_relations", "arguments": {"via": "texte", "type": "texte", "direction": "declares"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"enums": [], "forms": {}, "joins": [], "lists": [], "model": {}, "reading": {}, "ownership": [], "relations": []}}

• describe_rule≈ 318 tokens

  One convention of the vocabulary as written, not a company's own rule (an entity of type `rule`: list_entities, get_entity). Input: `rule`, a number from list_rules such as R9, in either case. Returns `rule`, `title`, `part`, `text` and the file's `url`. An unknown number is refused with the known ones listed.

  Paramètres, retour & exemple (1)

  Paramètres

  • rule · string · requis
    A convention's number from list_rules, such as R9

  Exemple d'appel

  {"name": "describe_rule", "arguments": {"rule": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"url": "texte", "part": "texte", "rule": "texte", "text": "texte", "model": {}, "title": "texte"}}

• describe_schema≈ 1007 tokens

  One type's schema: its sections as written and its declared relations as data. Use to learn what an entity of the type may hold; for the whole vocabulary use describe_relations. Input: `type`. Returns `url`, the schema's own file, `sections`, and `relations`: owner, owns, references both ways, enums, joins and lists.

  Paramètres, retour & exemple (1)

  Paramètres

  • type · string · requis
    A type name from list_types, such as skill

  Exemple d'appel

  {"name": "describe_schema", "arguments": {"type": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"url": "texte", "name": "texte", "type": "texte", "model": {}, "tagline": "texte", "sections": [], "relations": {}}}

• diagram≈ 1127 tokens

  A picture of the model as Mermaid; edge data: list_references. Input: `shape`; `id`, `domain`, `type` or `unit` narrow it. aggregate, flow, lifecycle take a context's `id`; organization without `id` draws the company; system a landscape, holds its data; usecase, scenario a use case's; requirements a feature's, product's, use case's or requirement's. Returns `mermaid`, `nodes`, `links`, `units`, counts. Max 50 nodes.

  Paramètres, retour & exemple (5)

  Paramètres

  • id · string · optionnel
    The process, the entity at a neighborhood's middle, the bounded context of a context map, or the aggregate or bounded context of an aggregate, flow or lifecycle picture, the group an organization is narrowed to, or the system drawn in its landscape by system and by the data it holds by holds, the use case drawn by usecase and scenario, or the feature, product, use case or requirement whose requirements are drawn, never by neighborhood
  • type · string · optionnel
    A type, to draw its schema and the types it is declared with
  • unit · string · optionnel
    core or a pack, to draw that unit's types and what they declare; a meta-model too large to draw whole is drawn as core, and `units` in the answer names every unit
  • shape · string · requis · concepts | process | neighborhood | schema | context | aggregate | flow | lifecycle
  • domain · string · optionnel
    A domain's id or address, to draw its concepts

  Exemple d'appel

  {"name": "diagram", "arguments": {"shape": "concepts"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"unit": "texte", "actor": "texte", "edges": 1, "links": [], "model": {}, "nodes": [], "shape": "concepts", "steps": [], "title": "texte", "units": [], "mermaid": "texte", "omitted": 1}}

• fetch≈ 295 tokens

  One entity's page as written. Use to quote or display the source; for structured fields and references use get_entity. Input: `id` or address, from search, list_entities or any reference. Returns `id`, `title`, `type`, `url` and `text`, the Markdown source. Takes no name: search with match "name" finds the id.

  Paramètres, retour & exemple (1)

  Paramètres

  • id · string · requis

  Exemple d'appel

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

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"id": "texte", "url": "texte", "text": "texte", "type": "texte", "model": {}, "title": "texte"}}

• find_evidence≈ 830 tokens

  Every edge into one skill, grouped by the type of the page that drew it. Use to check a claimed skill against its evidence. Input: `skill`, an id, canonical name or address; optional `limit`, `cursor`. Returns `skill`, `evidence` and `page`; a profile's claim arrives via Skills.Skill with its level, an evidence row via Evidence.Skill. Attributes are verbatim.

  Paramètres, retour & exemple (3)

  Paramètres

  • limit · integer · optionnel
    Entries per page: 50 by default, clamped to 1–200, so 0 returns one entry and 1000 returns 200.
  • skill · string · requis
    The skill's id, canonical name or address
  • cursor · string · optionnel
    `page.nextCursor` from the previous answer, sent with the same arguments; omit it for the first page.

  Exemple d'appel

  {"name": "find_evidence", "arguments": {"skill": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"page": {}, "model": {}, "skill": {}, "evidence": {}}}

• get_entity≈ 1228 tokens

  One entity as structured data: fields, sections, tables, references both ways. Use to reason over one; for its page as written use fetch. Input: `id` or address, where its page sits, or `type` and `name`; an ambiguous name is refused with candidate ids. Returns `entity`, by id. Reference lists hold at most 50 edges; `referenceCounts` gives totals, list_references the rest.

  Paramètres, retour & exemple (3)

  Paramètres

  • id · string · optionnel
    The entity's id, as any answer gives it, or its address, where its page sits
  • name · string · optionnel
    The canonical name, the entity's H1; needs type
  • type · string · optionnel

  Exemple d'appel

  {"name": "get_entity", "arguments": {"id": "texte", "name": "texte", "type": "texte"}}

  Exemple de retour

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

• list_checks≈ 334 tokens

  The checks the model's own gate runs, from the checker release this server was built with. Use to see which rules a script enforces and which are left to a reader. No input. Returns `checks`, each with `name`, `rule`, `title` and what it `reports`, a `failure` or a `note` that fails nothing, and `ranBy`. This server runs none of them.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "list_checks", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"model": {}, "ranBy": "texte", "checks": []}}

• list_entities≈ 942 tokens

  Entities with their frontmatter's short facts, in address order or newest first. Use to browse, or for what runs on a date, came last or has a value; to find by words use search. Input: optional `type`, `owner`, `order`, `on`, `by`, `where`, `fields`, `limit`, `cursor`. Returns `entities` with `fields`, and `page`; follow `page.nextCursor` while `page.hasMore`.

  Paramètres, retour & exemple (9)

  Paramètres

  • by · string · optionnel
    A date field, such as start or decided, to order by in the direction order names
  • on · string · optionnel
    A date, YYYY, YYYY-MM or YYYY-MM-DD: keep the entities whose period, start to end, holds it; an absent end is still running
  • type · string · optionnel
    A type, to keep its entities; leave it out to list every type
  • limit · integer · optionnel
    Entries per page: 50 by default, clamped to 1–200, so 0 returns one entry and 1000 returns 200.
  • order · string · optionnel · address | newest | oldest
    address, where the pages sit, by default; newest or oldest, by when each entity came into the model, or by the date `by` names
  • owner · string · optionnel
    An owner's id or address, to keep its entities
  • where · object · optionnel
    Field values to keep, ignoring case, by field name; a reference matches by the name its page writes
  • cursor · string · optionnel
    `page.nextCursor` from the previous answer, sent with the same arguments; omit it for the first page.
  • fields · array · optionnel
    Fields to add by name beside the short ones every entity carries, such as an array

  Exemple d'appel

  {"name": "list_entities", "arguments": {"by": "texte", "on": "texte", "type": "texte", "limit": 1, "order": "address", "owner": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"page": {}, "type": "texte", "model": {}, "entities": []}}

• list_references≈ 690 tokens

  The model's edges, filtered and paged. Use to inspect one entity's relations or one kind of reference without taking whole entities. Optional `entity` (an id or address), `direction` (out, in, both; needs `entity`), `via`, `type` (the far end's type, or either end's without `entity`), `limit`, `cursor`. Returns `edges`, each `from`, `via`, `to`, `attrs`, and `page`.

  Paramètres, retour & exemple (6)

  Paramètres

  • via · string · optionnel
  • type · string · optionnel
  • limit · integer · optionnel
    Entries per page: 50 by default, clamped to 1–200, so 0 returns one entry and 1000 returns 200.
  • cursor · string · optionnel
    `page.nextCursor` from the previous answer, sent with the same arguments; omit it for the first page.
  • entity · string · optionnel
  • direction · string · optionnel · out | in | both

  Exemple d'appel

  {"name": "list_references", "arguments": {"via": "texte", "type": "texte", "limit": 1, "cursor": "texte", "entity": "texte", "direction": "out"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"page": {}, "edges": [], "model": {}}}

• list_rules≈ 337 tokens

  The vocabulary's conventions the model is held to, R0 onwards, from its core's CONVENTIONS.md. Use to resolve a number a schema or refusal cites, such as R9. A company's own rules are entities of type `rule`: list_entities and get_entity. No input. Returns `tagline`, the file's `url`, and `rules`, each with `rule`, `title` and `part`; describe_rule gives one rule's text.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "list_rules", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"url": "texte", "model": {}, "rules": [], "tagline": "texte"}}

• list_types≈ 317 tokens

  Every type the model's schemas declare. Use first, to learn which types exist before listing or describing one. No input. Returns `types`, each with `type`, `name`, `tagline`, `owner` (the type it nests under, or null) and `count`, the entities it holds.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "list_types", "arguments": {}}

  Exemple de retour

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

• search≈ 835 tokens

  Find entities by words, substring or exact name. `match: "words"` needs every query word's stem in name, tagline, fields, sections or cells; `"text"` (default) is a case-insensitive substring over the same; `"name"` the exact canonical name. Optional `type`, `owner`, `limit`, `cursor`. Returns `results` with `id`, `title`, `type`, `matched`, `words` in words mode, and `page`: name matches first, then a listing.

  Paramètres, retour & exemple (6)

  Paramètres

  • type · string · optionnel
  • limit · integer · optionnel
    Entries per page: 50 by default, clamped to 1–200, so 0 returns one entry and 1000 returns 200.
  • match · string · optionnel · text | name | words
  • owner · string · optionnel
    An owner's id or address, to keep its entities
  • query · string · requis
  • cursor · string · optionnel
    `page.nextCursor` from the previous answer, sent with the same arguments; omit it for the first page.

  Exemple d'appel

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

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"page": {}, "match": "text", "model": {}, "query": "texte", "words": [], "results": []}}

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://mcp.companygraph.io/mcp