io.github.CCSTT-dev/callable

Est-ce que io.github.CCSTT-dev/callable est sûr ?

Au dernier audit MCP Hub, le serveur MCP « io.github.CCSTT-dev/callable » 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 3 outils

• get_task_status≈ 306 tokens

  Poll the status and retrieve the result of a previously submitted task. Returns the current status (pending, in_progress, pending_review, completed, disputed), the result payload, and any output URLs (video, screenshot). Use this in a polling loop after submit_task if no callback_url was provided.

  Paramètres, retour & exemple (1)

  Paramètres

  • task_id · string · requis
    The task ID returned when the task was submitted

  Exemple d'appel

  {"name": "get_task_status", "arguments": {"task_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"result": {}, "status": "pending", "task_id": "texte", "operator": "texte", "output_url": "texte", "completed_at": "texte"}}

• review_task≈ 344 tokens

  Optional. Approve or dispute a task that is in `pending_review` status. Use this after get_task_status reports the operator has completed the work. Approving releases the operator payout. Disputing requires a reason and a description of what is needed for acceptance; the operator is then allowed to resubmit. If you never call review_task, tasks are auto-approved after the review window expires.

  Paramètres, retour & exemple (4)

  Paramètres

  • task_id · string · requis
    The task ID returned by submit_task.
  • decision · string · requis · approve | dispute
    approve to accept the result and release payment; dispute to reject it and request a resubmission.
  • dispute_reason · string · optionnel
    Required when decision = 'dispute'. What went wrong with the submission.
  • what_is_needed · string · optionnel
    Required when decision = 'dispute'. What the operator must do for the submission to be accepted.

  Exemple d'appel

  {"name": "review_task", "arguments": {"task_id": "texte", "decision": "approve"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"status": "completed", "success": true}}

• submit_task≈ 636 tokens

  Submit an account verification task to a real human operator. Use this when your agent is blocked on something only a real person can complete — a KYC check, a platform sign-in or 2FA prompt, a CAPTCHA, an identity confirmation, or any verification step that requires a human. The task is charged automatically via Stripe ($39). A vetted operator claims it, performs the verification on real hardware, and returns the result (with optional screenshot) to your callback_url or via get_task_status. Typical completion: 30 minutes.

  Paramètres, retour & exemple (5)

  Paramètres

  • task_type · string · requis · account_verification
    account_verification — a real human verifies an account, KYC check, sign-in, or CAPTCHA on real hardware and returns structured proof ($39).
  • callback_url · string · optionnel
    Webhook URL to receive a POST request with the task result when completed. Recommended for async agent workflows. If omitted, poll get_task_status instead.
  • instructions · object · requis
    Structured input for account_verification. Required fields: platform (e.g. 'gmail', 'stripe'), url (where to perform the verification), credentials (login info or how to obtain the code), what_to_verify (what the operator must confirm). Optional: screenshot_required (boolean, default true), additional_notes.
  • deadline_minutes · integer · requis
    Time in minutes the operator has to complete the verification after claiming it. Minimum 20. Recommended: 30.
  • payment_credential · object · optionnel
    Stripe Link Agent Wallet Single-use Payment Token (SPT) for fully autonomous agent payments with no human intervention required. Omit if the developer account has a saved card on file.

  Exemple d'appel

  {"name": "submit_task", "arguments": {"task_type": "account_verification", "instructions": {}, "deadline_minutes": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"status": "pending", "message": "texte", "task_id": "texte", "estimated_completion": "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://getcallable.dev/api/mcp