io.github.geml-spec/geml

Est-ce que io.github.geml-spec/geml est sûr ?

Au dernier audit MCP Hub, le serveur MCP « io.github.geml-spec/geml » 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

• geml_add≈ 548 tokens

  Insert new content — one or more blocks, or prose — at the end of the document (`position: append`) or before/after the block named by `anchor`. Use this for content that does not exist yet; to change a block that does, use geml_set. Ids inside the content are kept. In a `.md` file Markdown lands as written, and GEML content is converted to Markdown as `to: "md"` converts it, the result's `notes` saying so; content Markdown cannot hold, such as a view without its source, is refused. Like every write here it is validated first: a missing anchor, an id that clashes with an existing one, or content that would break the document is refused. Returns `{ok, file, diagnostics, revision}`, with `notes` when the write did something to say out loud (a block it dropped, an address it changed); a refusal is `ok: false` with a `hint`, and the file is unchanged. This server is STATELESS: the document travels in `source` and a write comes back as `document` for you to save; it holds no other documents, so a cross-document reference such as `[[other.geml#id]]` cannot be resolved here and is reported as `unresolvable-document`.

  Paramètres, retour & exemple (5)

  Paramètres

  • name · string · optionnel
    The document's file name, e.g. notes/spec.geml or README.md — it decides whether the text is read as GEML or as Markdown (a `.md` name), and it is how the document is called in messages. Default: document.geml.
  • anchor · string · optionnel
    The block the insertion is relative to — an id, or any address geml_list prints; it must name one block. Required for before/after
  • source · string · requis
    The document's full text. This server keeps no files: what you send is the document.
  • content · string · requis
    The GEML fragment to insert
  • position · string · requis · append | before | after
    Where to insert

  Exemple d'appel

  {"name": "geml_add", "arguments": {"source": "texte", "content": "texte", "position": "append"}}

  Exemple de retour

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

• geml_check≈ 314 tokens

  Validate a GEML document without changing it: returns every diagnostic with a stable `code`, a severity and a line, and an empty list means the document is valid. Use it to confirm a document is sound before reporting work as finished. Every write through this server runs the same check before it lands, so a refused write already carries this information. This server is STATELESS: the document travels in `source` and a write comes back as `document` for you to save; it holds no other documents, so a cross-document reference such as `[[other.geml#id]]` cannot be resolved here and is reported as `unresolvable-document`.

  Paramètres, retour & exemple (2)

  Paramètres

  • name · string · optionnel
    The document's file name, e.g. notes/spec.geml or README.md — it decides whether the text is read as GEML or as Markdown (a `.md` name), and it is how the document is called in messages. Default: document.geml.
  • source · string · requis
    The document's full text. This server keeps no files: what you send is the document.

  Exemple d'appel

  {"name": "geml_check", "arguments": {"source": "texte"}}

  Exemple de retour

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

• geml_delete≈ 472 tokens

  Remove one or more blocks, each named by an id or any address geml_list prints; a filter (`=== type`, `{key=value}`) removes every block it matches. Each block takes the blank line that separated it from its neighbours, so deleting what geml_add inserted leaves the file as it was. To undo a deletion, geml_revert the removed id; to change a block rather than remove it, use geml_set. References left pointing at a removed block come back as diagnostics but do NOT block the deletion — read them, then repair the references or revert. A selector that names nothing is skipped, so repeating a call changes nothing. Returns `{ok, file, diagnostics, revision}`, with `notes` when the write did something to say out loud (a block it dropped, an address it changed); a refusal is `ok: false` with a `hint`, and the file is unchanged. This server is STATELESS: the document travels in `source` and a write comes back as `document` for you to save; it holds no other documents, so a cross-document reference such as `[[other.geml#id]]` cannot be resolved here and is reported as `unresolvable-document`.

  Paramètres, retour & exemple (3)

  Paramètres

  • ids · array · requis
    The blocks to remove: ids or addresses
  • name · string · optionnel
    The document's file name, e.g. notes/spec.geml or README.md — it decides whether the text is read as GEML or as Markdown (a `.md` name), and it is how the document is called in messages. Default: document.geml.
  • source · string · requis
    The document's full text. This server keeps no files: what you send is the document.

  Exemple d'appel

  {"name": "geml_delete", "arguments": {"ids": [], "source": "texte"}}

  Exemple de retour

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

• geml_find≈ 475 tokens

  Search block CONTENT in the document; each hit is one `<name>\t<address>` row. geml_list says what a document contains, this says which block holds the words — as an address that pastes straight into geml_get or geml_set, not a line number the next edit invalidates. The address is the innermost block holding the match, and a block matching on many lines is reported once. Substring, case-insensitive unless `case` is true. No match is an empty result, not an error. This server is STATELESS: the document travels in `source` and a write comes back as `document` for you to save; it holds no other documents, so a cross-document reference such as `[[other.geml#id]]` cannot be resolved here and is reported as `unresolvable-document`.

  Paramètres, retour & exemple (6)

  Paramètres

  • case · boolean · optionnel
    Match case exactly (default: case-insensitive)
  • head · boolean · optionnel
    Add the matching line as a third column
  • name · string · optionnel
    The document's file name, e.g. notes/spec.geml or README.md — it decides whether the text is read as GEML or as Markdown (a `.md` name), and it is how the document is called in messages. Default: document.geml.
  • source · string · requis
    The document's full text. This server keeps no files: what you send is the document.
  • within · string · optionnel
    Optional: only look inside the blocks this selector names, e.g. `#install` for a section or `=== table` for every table. It takes the same selector forms as geml_get's `id`.
  • pattern · string · requis
    Text to look for inside block bodies

  Exemple d'appel

  {"name": "geml_find", "arguments": {"source": "texte", "pattern": "texte"}}

  Exemple de retour

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

• geml_get≈ 753 tokens

  Read ONE block from a GEML document instead of the whole file: only that block comes back, typically a few percent of the document. Pass the `address` geml_list prints as `id` — it also reaches blocks with no `#id`; to locate a block by its words instead, use geml_find first. An `id` that matches nothing, or a file that is not under the server root, is an error naming it. This server is STATELESS: the document travels in `source` and a write comes back as `document` for you to save; it holds no other documents, so a cross-document reference such as `[[other.geml#id]]` cannot be resolved here and is reported as `unresolvable-document`.

  Paramètres, retour & exemple (6)

  Paramètres

  • id · string · requis
    What to read: a block id (with or without `#`), a `## Heading` line (its whole section), `=== type` for every block of a type, `=== code {lang=py}` or `{.warn}` for every block carrying those attributes, a `@<hex>` content address for a block with no id, or `L27`/`L27-58` for the smallest block holding those lines — the forms `geml_list` prints, plus the line numbers an editor or a diff hunk speaks
  • name · string · optionnel
    The document's file name, e.g. notes/spec.geml or README.md — it decides whether the text is read as GEML or as Markdown (a `.md` name), and it is how the document is called in messages. Default: document.geml.
  • part · string · optionnel · whole | head | intro | body
    How much of the block to return (default: whole). For a SECTION these cut it three ways: `head` is the heading line, `intro` everything under it up to its first subheading, `body` everything under it — so `body` always contains `intro`, and equals it when the section has no subheading. Reach for `intro` to read a section's opening without pulling its subsections into the conversation; a whole `#id` on a top-level heading is often the entire document. Only a heading has an intro. `body` is usually what you want together with `view`.
  • view · boolean · optionnel
    Read THROUGH an `embed` block to the entity block it stands for, following a multi-layer chain to its end. An `embed` has no content of its own, so this is the only way to see what it points at; on any other block it changes nothing. Returns {from, content}: `from` names the document the content actually came from, and its references and relative paths resolve against THAT document, not this one.
  • source · string · requis
    The document's full text. This server keeps no files: what you send is the document.
  • within · string · optionnel
    Optional: only look inside the blocks this selector names, e.g. `#install` for a section or `=== table` for every table. It takes the same selector forms as geml_get's `id`.

  Exemple d'appel

  {"name": "geml_get", "arguments": {"id": "texte", "source": "texte"}}

  Exemple de retour

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

• geml_list≈ 407 tokens

  List every addressable block in a GEML document — its address, kind and heading text — in one call, with no paging. Call this FIRST: what it returns is what every other tool here addresses, and it is cheaper and more reliable than reading the file to see what is in it. Rows marked `anon` have no `#id`; geml_get and geml_set take their `address` as `id`, while the other write tools need a real id, so give such a block one first. A file that is not under the server root is an error. This server is STATELESS: the document travels in `source` and a write comes back as `document` for you to save; it holds no other documents, so a cross-document reference such as `[[other.geml#id]]` cannot be resolved here and is reported as `unresolvable-document`.

  Paramètres, retour & exemple (3)

  Paramètres

  • name · string · optionnel
    The document's file name, e.g. notes/spec.geml or README.md — it decides whether the text is read as GEML or as Markdown (a `.md` name), and it is how the document is called in messages. Default: document.geml.
  • source · string · requis
    The document's full text. This server keeps no files: what you send is the document.
  • within · string · optionnel
    Optional: only look inside the blocks this selector names, e.g. `#install` for a section or `=== table` for every table. It takes the same selector forms as geml_get's `id`.

  Exemple d'appel

  {"name": "geml_list", "arguments": {"source": "texte"}}

  Exemple de retour

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

• geml_rename≈ 423 tokens

  Rename a block id AND every reference to it in the same document, in one id-boundary-safe write. Use this rather than geml_set or a text search-and-replace, which would also hit ids that merely share a prefix. A Markdown heading's anchor is its text, so it is renamed by changing the heading with geml_set (`part: head`), not here. An `old` id that does not exist, or a `new` one already taken, is refused. Returns `{ok, file, diagnostics, revision}`, with `notes` when the write did something to say out loud (a block it dropped, an address it changed); a refusal is `ok: false` with a `hint`, and the file is unchanged. This server is STATELESS: the document travels in `source` and a write comes back as `document` for you to save; it holds no other documents, so a cross-document reference such as `[[other.geml#id]]` cannot be resolved here and is reported as `unresolvable-document`.

  Paramètres, retour & exemple (4)

  Paramètres

  • new · string · requis
    New id
  • old · string · requis
    Current id
  • name · string · optionnel
    The document's file name, e.g. notes/spec.geml or README.md — it decides whether the text is read as GEML or as Markdown (a `.md` name), and it is how the document is called in messages. Default: document.geml.
  • source · string · requis
    The document's full text. This server keeps no files: what you send is the document.

  Exemple d'appel

  {"name": "geml_rename", "arguments": {"new": "texte", "old": "texte", "source": "texte"}}

  Exemple de retour

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

• geml_set≈ 740 tokens

  Replace ONE block and leave every other byte untouched — prefer this to rewriting a file. For content that does not exist yet use geml_add; to remove a block, geml_delete. The replacement is validated before it is written: if it would break the document, nothing is written and the diagnostics come back — fix the body rather than resending it. Removing content is not refused: if the replacement drops blocks, the write goes through and the result names each one, so check it after shortening a section; geml_revert puts one back. `part` replaces the whole block (default), its head line, a section's `intro`, or its body. In a Markdown file a heading's anchor is its text, as on GitHub: new heading text gives the heading a new address, and the document's links to the old one follow in the same write. GEML content written over a Markdown heading or prose is converted to Markdown, as in geml_add; a GEML block already in the file stays GEML. An `id` that matches no block, or several, is refused. Returns `{ok, file, diagnostics, revision}`, with `notes` when the write did something to say out loud (a block it dropped, an address it changed); a refusal is `ok: false` with a `hint`, and the file is unchanged. This server is STATELESS: the document travels in `source` and a write comes back as `document` for you to save; it holds no other documents, so a cross-document reference such as `[[other.geml#id]]` cannot be resolved here and is reported as `unresolvable-document`.

  Paramètres, retour & exemple (5)

  Paramètres

  • id · string · requis
    Which block to replace: an id (with or without `#`), a `@<hex>` content address from `geml_list` for a block with no id, or `L27`/`L27-58` for the smallest block holding those lines. Must match exactly one block
  • body · string · requis
    The replacement text
  • name · string · optionnel
    The document's file name, e.g. notes/spec.geml or README.md — it decides whether the text is read as GEML or as Markdown (a `.md` name), and it is how the document is called in messages. Default: document.geml.
  • part · string · optionnel · whole | head | intro | body
    What to replace (default: whole). `intro` replaces a section's opening — everything under the heading up to its first subheading — and leaves every subsection byte-identical, which is what makes a read-edit-write cycle on a long section safe. An empty intro (a subheading follows the heading immediately) is written into, so this also adds an opening where there was none.
  • source · string · requis
    The document's full text. This server keeps no files: what you send is the document.

  Exemple d'appel

  {"name": "geml_set", "arguments": {"id": "texte", "body": "texte", "source": "texte"}}

  Exemple de retour

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

• geml_to≈ 528 tokens

  Convert a WHOLE document and get the result back as text — the read half of the CLI's `geml <file> --to <fmt>`. `to: "geml"` on a Markdown file is the importer, the one thing the block tools cannot do; `to: "md"` projects a GEML document out (lossy); `to: "json"` returns the full document model, for when geml_list plus geml_get is not enough. Nothing is written — pass the result to geml_add or geml_set to land it. `to: "html"` also works but returns a whole self-contained page, usually tens of kilobytes this server cannot save: prefer the CLI (`geml <file> --to html -o out.html`) unless you want the markup in the conversation. A document with errors returns its diagnostics instead of a conversion, and a file that is not under the server root is an error. This server is STATELESS: the document travels in `source` and a write comes back as `document` for you to save; it holds no other documents, so a cross-document reference such as `[[other.geml#id]]` cannot be resolved here and is reported as `unresolvable-document`.

  Paramètres, retour & exemple (4)

  Paramètres

  • to · string · optionnel · json | md | geml | html
    Target format. Default is the CLI's: a GEML input becomes json, a Markdown input becomes geml. `html` is a whole page — large, and not writable from here.
  • from · string · optionnel · geml | md | json
    Override the input format, which is otherwise inferred from the extension (.md -> md, .json -> json, else geml).
  • name · string · optionnel
    The document's file name, e.g. notes/spec.geml or README.md — it decides whether the text is read as GEML or as Markdown (a `.md` name), and it is how the document is called in messages. Default: document.geml.
  • source · string · requis
    The document's full text. This server keeps no files: what you send is the document.

  Exemple d'appel

  {"name": "geml_to", "arguments": {"source": "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://geml-mcp.supermarket.workers.dev/mcp