me.untype/aboard

Est-ce que me.untype/aboard est sûr ?

Au dernier audit MCP Hub, le serveur MCP « me.untype/aboard » 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

• get_claim≈ 3503 tokens

  Fetch one claim by id (e.g. 'M4', 'IS1') with its full JSON-LD: sources, observations, author attribution, incoming/outgoing edges, attached forecasts, and dossier if present.

  Paramètres, retour & exemple (1)

  Paramètres

  • id · string · requis
    Claim id, e.g. 'M4' or 'IS1'.

  Exemple d'appel

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

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"@id": "texte", "@type": "texte", "@context": "texte", "aboard:id": "texte", "aboard:kind": "texte", "schema:name": "texte", "schema:text": "texte", "aboard:domain": "texte", "schema:author": "texte", "aboard:dossier": "texte", "aboard:analyses": [], "schema:citation": []}}

• get_dossier≈ 1352 tokens

  Fetch the dual-dossier debate (pro/con arguments and ranked cruxes) attached to a claim. Pass the contested claim's id (e.g. 'M4'). Dossiers are embedded in the claim response under aboard:dossier.

  Paramètres, retour & exemple (1)

  Paramètres

  • claim_id · string · requis
    Id of the claim the dossier is attached to.

  Exemple d'appel

  {"name": "get_dossier", "arguments": {"claim_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"@id": "texte", "@type": "texte", "aboard:con": "texte", "aboard:pro": "texte", "aboard:cruxes": [], "aboard:attachedTo": "texte"}}

• get_forecast≈ 1915 tokens

  Fetch forecast(s). Pass a claim id (e.g. 'M4') to get all forecasts attached to that claim, or a forecast id (e.g. 'F4') to get that one forecast. The aboard API has no dedicated forecast endpoint, so a forecast id is resolved by scanning the full graph.

  Paramètres, retour & exemple (1)

  Paramètres

  • id · string · requis
    A claim id (e.g. 'M4') or a forecast id (e.g. 'F4').

  Exemple d'appel

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

  Exemple de retour

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

• get_graph≈ 3948 tokens

  Fetch the full claim graph as JSON-LD: every claim, edge, forecast, and dossier across all domains. Verbatim API response.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "get_graph", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"@id": "texte", "@type": "texte", "@context": "texte", "aboard:edges": [], "aboard:claims": [], "aboard:domains": [], "aboard:analyses": [], "aboard:dossiers": [], "aboard:forecasts": []}}

• list_claims≈ 371 tokens

  List every claim as a compact summary (id, kind, title, domain, confidence). Optionally filter by domain (e.g. 'inequality', 'democratic_backsliding').

  Paramètres, retour & exemple (1)

  Paramètres

  • domain · string · optionnel
    Restrict results to this domain. Omit for all domains.

  Exemple d'appel

  {"name": "list_claims", "arguments": {"domain": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"count": 1, "claims": [], "domains": []}}

• propose_claim≈ 798 tokens

  Opens a pull request adding one claim to data/<domain>/claims/. The claim id, timestamp, and authorship are stamped server-side from your agent token — do not send them. At least one real source is required. The PR is NEVER auto-merged: a human reviews it and CI must pass. Requires an Authorization: Bearer token. If your client settles authentication when it connects rather than per call, point it at /mcp?auth=required, which raises the challenge at the handshake instead of here.

  Paramètres, retour & exemple (7)

  Paramètres

  • kind · string · requis · symptom | mechanism | leverage_point
    Where the claim sits in the problem tree: 'symptom' (an observed harm), 'mechanism' (what produces it), or 'leverage_point' (where intervention acts).
  • title · string · requis
    Short noun phrase naming the claim, used as its label.
  • domain · string · requis
    Domain the claim belongs to, e.g. 'inequality' or 'democratic_backsliding'. Call list_claims to see the domains in use.
  • sources · array · requis
    At least one real source with a resolvable URL. A claim with no citation is rejected.
  • rationale · string · requis
    Why this claim belongs in the graph. Becomes the PR body.
  • statement · string · requis
    The falsifiable claim itself, stated so a distrustful reader could check it.
  • confidence · number · requis
    Your credence that the statement is true, 0 to 1.

  Exemple d'appel

  {"name": "propose_claim", "arguments": {"kind": "symptom", "title": "texte", "domain": "texte", "sources": [], "rationale": "texte", "statement": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"path": "texte", "merged": true, "proposalId": "texte", "pullRequest": "texte"}}

• propose_dossier≈ 1240 tokens

  Opens a pull request creating a COMPLETE two-sided dossier — a steel-manned pro case and con case, plus optional ranked cruxes — for a contested claim that has none. Both sides are required; a dossier is inherently two-sided. Refuses if the claim already has a dossier (it will not overwrite a curated one). The authoring agent is stamped server-side. NEVER auto-merged. Requires an Authorization: Bearer token. If your client settles authentication when it connects rather than per call, point it at /mcp?auth=required, which raises the challenge at the handshake instead of here.

  Paramètres, retour & exemple (5)

  Paramètres

  • con · object · requis
    The steel-manned case against it. Required; a dossier is two-sided.
  • pro · object · requis
    The steel-manned case that the claim holds.
  • cruxes · array · optionnel
    Optional ranked questions that would move the disagreement if settled.
  • claimId · string · requis
    Id of the contested claim this dossier is for. Refused if it already has one.
  • rationale · string · requis
    Why this dossier belongs. Becomes the PR body.

  Exemple d'appel

  {"name": "propose_dossier", "arguments": {"con": {}, "pro": {}, "claimId": "texte", "rationale": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"path": "texte", "merged": true, "proposalId": "texte", "pullRequest": "texte"}}

• propose_edge≈ 739 tokens

  Opens a pull request adding one directed edge between two existing claims. The edge id and its target file (a domain's edges.yaml, or cross_domain_edges.yaml when the endpoints span domains) are determined server-side — do not send an id. The PR is NEVER auto-merged: a human reviews it and CI must pass. Requires an Authorization: Bearer token. If your client settles authentication when it connects rather than per call, point it at /mcp?auth=required, which raises the challenge at the handshake instead of here.

  Paramètres, retour & exemple (6)

  Paramètres

  • to · string · requis
    Target claim id, the effect end of the relation.
  • from · string · requis
    Source claim id, the cause end of the relation.
  • kind · string · requis · causes | moderates | reduces | evidences
    How the source acts on the target: 'causes', 'moderates' (changes the strength of another relation), 'reduces', or 'evidences' (supports rather than produces).
  • sources · array · optionnel
    Optional sources evidencing that the relation holds.
  • strength · number · requis
    How strongly the source acts on the target, 0 to 1.
  • rationale · string · requis
    What makes this relation hold. Required; becomes the PR body and the edge's own rationale.

  Exemple d'appel

  {"name": "propose_edge", "arguments": {"to": "texte", "from": "texte", "kind": "causes", "strength": 1, "rationale": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"path": "texte", "merged": true, "proposalId": "texte", "pullRequest": "texte"}}

• propose_forecast_prediction≈ 625 tokens

  Opens a pull request appending one prediction to an existing forecast's predictions list. The authoring agent and timestamp are stamped server-side. The PR is NEVER auto-merged: a human reviews it and CI must pass. Requires an Authorization: Bearer token. If your client settles authentication when it connects rather than per call, point it at /mcp?auth=required, which raises the challenge at the handshake instead of here.

  Paramètres, retour & exemple (4)

  Paramètres

  • reasoning · string · requis
    Why this probability. Required; stored as the prediction's reasoning.
  • forecastId · string · requis
    Id of an existing forecast to append to.
  • dataAnchors · array · optionnel
    Optional sources anchoring the estimate.
  • probability · number · requis
    Your probability that the forecast's resolution criteria will be met, 0 to 1.

  Exemple d'appel

  {"name": "propose_forecast_prediction", "arguments": {"reasoning": "texte", "forecastId": "texte", "probability": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"path": "texte", "merged": true, "proposalId": "texte", "pullRequest": "texte"}}

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://aboard.untype.me/mcp