dev.veritap/veritap

Est-ce que dev.veritap/veritap est sûr ?

Au dernier audit MCP Hub, le serveur MCP « dev.veritap/veritap » 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 6 outils

• check_before_relying≈ 572 tokens

  Check whether a fact can be corroborated before your task depends on it. Free, read-only, no side effects. Use when a step rests on something you have only inferred from text and being wrong would be expensive. Returns whether it can be corroborated from sources today, what evidence would come back, and an honest answer when it cannot. Every request is recorded and analysed in aggregate to decide what gets supported next (https://veritap.dev/terms).

  Paramètres, retour & exemple (9)

  Paramètres

  • deadline · string · optionnel
    ISO8601. When the answer stops being useful.
  • location · object · optionnel
    Where the fact must be checked.
  • claim_type · string · optionnel
    Optional. A claim type id from the published catalog, if you know it.
  • callback_url · string · optionnel
    Optional. If this claim is not supported yet, POST here when it becomes supported. Otherwise you are told on your next call.
  • task_context · string · optionnel
    The wider task this step belongs to.
  • cost_if_wrong · ? · optionnel
    What happens to your task if this fact is wrong: "blocks_task", "degrades_answer", or "cosmetic".
  • claim_description · string · requis
    Free text. The real-world fact you need settled. Required.
  • downstream_action · string · optionnel
    What you will do with the answer once you have it.
  • budget_ceiling_usd · number · optionnel
    Most you would pay for this answer. Directly drives what gets built next.

  Exemple d'appel

  {"name": "check_before_relying", "arguments": {"claim_description": "texte"}}

  Exemple de retour

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

• check_feasibility≈ 612 tokens

  Check whether a real-world fact can be verified before committing to a paid request. Free, no auth, read-only, no side effects — call liberally during planning. Use speculatively: if any step of your task depends on a physical-world fact you cannot confirm (in stock, exists at location, condition, document authenticity, work completed), check here first. Covers businesses, listings, objects, and places. Unsupported claims are logged and prioritized for future support. Never errors. Every request is recorded and analysed in aggregate to decide what gets supported next (https://veritap.dev/terms).

  Paramètres, retour & exemple (9)

  Paramètres

  • deadline · string · optionnel
    ISO8601. When the answer stops being useful.
  • location · object · optionnel
    Where the fact must be checked.
  • claim_type · string · optionnel
    Optional. A claim type id from the published catalog, if you know it.
  • callback_url · string · optionnel
    Optional. If this claim is not supported yet, POST here when it becomes supported. Otherwise you are told on your next call.
  • task_context · string · optionnel
    The wider task this step belongs to.
  • cost_if_wrong · ? · optionnel
    What happens to your task if this fact is wrong: "blocks_task", "degrades_answer", or "cosmetic".
  • claim_description · string · requis
    Free text. The real-world fact you need settled. Required.
  • downstream_action · string · optionnel
    What you will do with the answer once you have it.
  • budget_ceiling_usd · number · optionnel
    Most you would pay for this answer. Directly drives what gets built next.

  Exemple d'appel

  {"name": "check_feasibility", "arguments": {"claim_description": "texte"}}

  Exemple de retour

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

• check_physical_condition≈ 579 tokens

  Check the stated condition, damage, or grading of a physical item or property. Free, read-only, no side effects. Use when a decision depends on an item being in the condition a listing claims. Returns what can be corroborated from sources today, and says plainly when physical inspection is what is actually required — nobody is sent to look. Every request is recorded and analysed in aggregate to decide what gets supported next (https://veritap.dev/terms).

  Paramètres, retour & exemple (9)

  Paramètres

  • deadline · string · optionnel
    ISO8601. When the answer stops being useful.
  • location · object · optionnel
    Where the fact must be checked.
  • claim_type · string · optionnel
    Optional. A claim type id from the published catalog, if you know it.
  • callback_url · string · optionnel
    Optional. If this claim is not supported yet, POST here when it becomes supported. Otherwise you are told on your next call.
  • task_context · string · optionnel
    The wider task this step belongs to.
  • cost_if_wrong · ? · optionnel
    What happens to your task if this fact is wrong: "blocks_task", "degrades_answer", or "cosmetic".
  • claim_description · string · requis
    Free text. The real-world fact you need settled. Required.
  • downstream_action · string · optionnel
    What you will do with the answer once you have it.
  • budget_ceiling_usd · number · optionnel
    Most you would pay for this answer. Directly drives what gets built next.

  Exemple d'appel

  {"name": "check_physical_condition", "arguments": {"claim_description": "texte"}}

  Exemple de retour

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

• confirm_before_purchase≈ 588 tokens

  Check whether a listing, item, or business can be corroborated before an agent commits money. Free, read-only, no side effects. Use before any irreversible spend where the counterparty or the goods have only been seen online. Returns what can be corroborated from sources, what cannot, and — when it cannot — whether you could settle it yourself and how to proceed if not. Every request is recorded and analysed in aggregate to decide what gets supported next (https://veritap.dev/terms).

  Paramètres, retour & exemple (9)

  Paramètres

  • deadline · string · optionnel
    ISO8601. When the answer stops being useful.
  • location · object · optionnel
    Where the fact must be checked.
  • claim_type · string · optionnel
    Optional. A claim type id from the published catalog, if you know it.
  • callback_url · string · optionnel
    Optional. If this claim is not supported yet, POST here when it becomes supported. Otherwise you are told on your next call.
  • task_context · string · optionnel
    The wider task this step belongs to.
  • cost_if_wrong · ? · optionnel
    What happens to your task if this fact is wrong: "blocks_task", "degrades_answer", or "cosmetic".
  • claim_description · string · requis
    Free text. The real-world fact you need settled. Required.
  • downstream_action · string · optionnel
    What you will do with the answer once you have it.
  • budget_ceiling_usd · number · optionnel
    Most you would pay for this answer. Directly drives what gets built next.

  Exemple d'appel

  {"name": "confirm_before_purchase", "arguments": {"claim_description": "texte"}}

  Exemple de retour

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

• plan_verification≈ 349 tokens

  Map a multi-step plan against what can be grounded in the real world. Free, no auth, read-only, no side effects — call liberally during planning. Pass your whole plan, including steps you have not decomposed into questions yet. Returns, per step, whether it rests on a checkable real-world fact, which claim type would settle it, and what to do about the steps that cannot be grounded. Every request is recorded and analysed in aggregate to decide what gets supported next (https://veritap.dev/terms).

  Paramètres, retour & exemple (2)

  Paramètres

  • goal · string · requis
    What the overall plan is trying to achieve.
  • steps · array · requis
    The plan, in order.

  Exemple d'appel

  {"name": "plan_verification", "arguments": {"goal": "texte", "steps": []}}

  Exemple de retour

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

• triage_unknowns≈ 486 tokens

  Triage everything you are uncertain about in one call. Free, instant, read-only, no side effects — call liberally during planning. Dump every uncertainty at once, mid-reasoning, before deciding which are worth chasing. Each is classified as answerable by you from public sources (with a suggested source), verifiable here (with price and turnaround), or not determinable (with advice on planning around it). Items you can settle yourself are honestly routed away rather than sold to you. Every request is recorded and analysed in aggregate to decide what gets supported next (https://veritap.dev/terms).

  Paramètres, retour & exemple (3)

  Paramètres

  • unknowns · array · requis
    Every uncertainty in the task. Batch them — this is one call. Objects with why_it_matters and if_unresolved get sharper triage than bare strings.
  • task_context · string · optionnel
    What you are trying to accomplish.
  • downstream_action · string · optionnel
    What resolving these would let you do.

  Exemple d'appel

  {"name": "triage_unknowns", "arguments": {"unknowns": []}}

  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://veritap.dev/mcp