io.github.Toinedotcom/toolforte

Est-ce que io.github.Toinedotcom/toolforte est sûr ?

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

• calculate_vat≈ 259 tokens

  Add VAT to a net amount or extract VAT from a gross amount at any rate (e.g. 21 for Dutch BTW). Returns exact net, VAT, and gross amounts rounded to cents.

  Paramètres, retour & exemple (3)

  Paramètres

  • mode · string · requis · add | extract
    add = amount is net, add VAT on top; extract = amount is gross, split out VAT
  • rate · number · requis
    VAT rate in percent
  • amount · number · requis
    The amount

  Exemple d'appel

  {"name": "calculate_vat", "arguments": {"mode": "add", "rate": 1, "amount": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"net": 1, "vat": 1, "rate": 1, "gross": 1, "result": "texte"}}

• csv_to_json≈ 218 tokens

  Parse CSV data into JSON with delimiter auto-detection and quoted-field handling.

  Paramètres, retour & exemple (2)

  Paramètres

  • csv · string · requis
    The CSV text; the delimiter is detected automatically
  • firstRowHeaders · boolean · optionnel
    Treat the first row as column names and return objects (default true)

  Exemple d'appel

  {"name": "csv_to_json", "arguments": {"csv": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"json": [], "result": "texte", "delimiter": "texte", "row_count": 1}}

• describe_tool≈ 395 tokens

  The full definition of one ToolForte tool by name: description, argument schema (JSON Schema), output schema, annotations, cost and an example call. Use it after search_tools when the argument summary is not enough. Free.

  Paramètres, retour & exemple (1)

  Paramètres

  • name · string · requis
    The tool name, for example validate_iban

  Exemple d'appel

  {"name": "describe_tool", "arguments": {"name": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"name": "texte", "title": "texte", "listed": true, "result": "texte", "credits": 1, "example": {}, "annotations": {}, "description": "texte", "inputSchema": {}, "outputSchema": {}}}

• dutch_public_holidays≈ 201 tokens

  Exact Dutch public holidays for a year, including movable feasts (Easter, Ascension, Whitsun) and King's Day rules. Use this instead of computing Dutch holidays yourself.

  Paramètres, retour & exemple (1)

  Paramètres

  • year · integer · requis
    Calendar year, 1900 to 2200

  Exemple d'appel

  {"name": "dutch_public_holidays", "arguments": {"year": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"year": 1, "result": "texte", "holidays": []}}

• format_json≈ 234 tokens

  Validate and pretty-print JSON with a real parser. Returns formatted JSON or the exact parse error.

  Paramètres, retour & exemple (2)

  Paramètres

  • json · string · requis
    The JSON text to validate and format
  • indent · integer · optionnel
    Spaces per indentation level, 0 to 8 (default 2)

  Exemple d'appel

  {"name": "format_json", "arguments": {"json": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"valid": true, "output": "texte", "result": "texte"}}

• run_tool≈ 255 tokens

  Run any ToolForte tool by name with its arguments, whether or not it is listed in this session. The result, the cost and the metering are exactly what the tool gives when called directly; run_tool itself is free. Find names with search_tools and schemas with describe_tool.

  Paramètres, retour & exemple (2)

  Paramètres

  • name · string · requis
    The tool name, for example calculate_vat
  • arguments · object · optionnel
    The tool's arguments, as describe_tool documents them

  Exemple d'appel

  {"name": "run_tool", "arguments": {"name": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"result": "texte"}}

• search_tools≈ 332 tokens

  Find ToolForte tools by what you want done, for example "iban", "vat", "pdf merge", "working days", "csv to json", "screenshot". ToolForte has over a hundred exact tools (validation, conversion, Dutch tax and dates, test data, files, AI); a session lists a small core of them and this is how you reach the rest. Returns the best matches with their arguments and cost. Then call the tool by name, or through run_tool. Free.

  Paramètres, retour & exemple (2)

  Paramètres

  • limit · integer · optionnel
    How many matches to return, 1 to 50 (default 8)
  • query · string · optionnel
    Words describing the job. Empty lists every tool the server has.

  Exemple d'appel

  {"name": "search_tools", "arguments": {"limit": 1, "query": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"note": "texte", "count": 1, "query": "texte", "tools": [], "total": 1, "result": "texte"}}

• test_regex≈ 258 tokens

  Run a JavaScript regular expression against a test string using a real regex engine. Returns all matches with capture groups and indices.

  Paramètres, retour & exemple (3)

  Paramètres

  • text · string · requis
    The text to run the expression against
  • flags · string · optionnel
    Regex flags such as g, i, m, s, u (default g)
  • pattern · string · requis
    JavaScript regular expression source, without the slashes

  Exemple d'appel

  {"name": "test_regex", "arguments": {"text": "texte", "pattern": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"count": 1, "result": "texte", "matches": []}}

• text_diff≈ 230 tokens

  Compute an exact line-based diff between two texts with add/remove/unchanged stats.

  Paramètres, retour & exemple (2)

  Paramètres

  • modified · string · requis
    The text after the change
  • original · string · requis
    The text before the change

  Exemple d'appel

  {"name": "text_diff", "arguments": {"modified": "texte", "original": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"lines": [], "stats": {}, "result": "texte"}}

• validate_iban≈ 593 tokens

  Check whether an IBAN is well formed: the mod-97 checksum, the country code, the length that country's IBAN must have, and whether every position holds the kind of character that country allows there (mod-97 turns letters into numbers, so on its own it cannot see a capital O typed in place of a zero). Returns validity, country, and where known the bank identifier printed inside the IBAN. This is a format check, not a bank check: a passing IBAN can still name a bank code that never existed or has since merged away, and says nothing about whether the account exists or can receive a payment. For twelve countries it also verifies the national check digit that the bank computes over the bank code and account number (BE, FR, MC, ES, IT, SM, PT, SI, PL, TN, EE, HU); nationalCheck 'failed' there means the number is very probably invented, since that digit cannot be back-computed the way the mod-97 pair can. Absent nationalCheck means not checked, never approved. For Dutch IBANs it also names the institution behind the four-letter bank code, including codes that no longer issue accounts; an unrecognised code does not make the IBAN invalid. A territory that borrows another country's IBAN (Reunion, Guernsey, Aland and the like) is reported with the prefix it actually uses, since no IBAN starts with RE or GG. Never guess whether an IBAN is well formed: use this tool. Do not present a pass as confirmation that money can be sent.

  Paramètres, retour & exemple (1)

  Paramètres

  • iban · string · requis
    The IBAN to validate

  Exemple d'appel

  {"name": "validate_iban", "arguments": {"iban": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"iban": "texte", "valid": true, "result": "texte", "country": "texte", "bankCode": "texte", "checkDigits": "texte", "countryName": "texte", "institution": {}, "accountNumber": "texte"}}

• workflow_list≈ 324 tokens

  List the workflows saved to the ToolForte account this API key belongs to. A workflow runs several ToolForte tools in order, passing each one the output of an earlier step, so it does a whole job in one call instead of you orchestrating the steps yourself. Returns each workflow's id, the inputs it expects, the steps it runs and what a run costs. Call this first: workflow_run needs an id from here. Requires an API key, because a workflow belongs to an account. Get a free key at https://toolforte.com/developers and send it on the MCP connection as the header Authorization: Bearer tf_...

  Paramètres, retour & exemple (1)

  Paramètres

  • limit · integer · optionnel
    How many to return, newest first.

  Exemple d'appel

  {"name": "workflow_list", "arguments": {"limit": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"count": 1, "result": "texte", "workflows": []}}

• workflow_propose≈ 612 tokens

  Describe a job in plain words and get back a workflow built only from tools this server really has: a name, the inputs it needs, and the steps in order, each with one sentence on why it is there. The proposal is honest about gaps: partial is true and missing names what could not be done, and when nothing here fits the answer says so instead of inventing a step. Send save: true to keep it on the account, after which workflow_run can run it by the returned id. Costs 10 credits, the price of one AI generation, charged once per proposal. Requires an API key linked to a ToolForte account. Get a free key at https://toolforte.com/developers and send it on the MCP connection as the header Authorization: Bearer tf_...

  Paramètres, retour & exemple (2)

  Paramètres

  • goal · string · requis
    The job to be done, in a sentence or two, for example: take a CSV of invoices, sum the amounts per customer and write the totals to a spreadsheet.
  • save · boolean · optionnel
    Save the proposed workflow to the account so workflow_run can run it. Default false: the proposal is returned for you to read first.

  Exemple d'appel

  {"name": "workflow_propose", "arguments": {"goal": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"saved": {}, "steps": [], "result": "texte", "missing": [], "partial": true, "definition": {}, "explanation": "texte", "creditsCharged": 1}}

• workflow_run≈ 534 tokens

  Run one saved workflow by id and return what every step produced. Get the id and the input keys from workflow_list. Each step costs the credits its own tool costs, normally 1 per step, and the credit for this call counts as the first step's rather than being charged on top. Steps run in order and stop at the first failure; the result says which step stopped it and what was spent up to that point. Check the "substitutions" field when it is present: it lists values a step supplied that the tool replaced with its own, which means the run succeeded on a value you did not send. Requires an API key, because a workflow belongs to an account. Get a free key at https://toolforte.com/developers and send it on the MCP connection as the header Authorization: Bearer tf_...

  Paramètres, retour & exemple (2)

  Paramètres

  • inputs · object · optionnel
    Values for the workflow's declared inputs, keyed by the input key that workflow_list reports. Omit for a workflow that declares none.
  • workflowId · string · requis
    The id of a workflow from workflow_list.

  Exemple d'appel

  {"name": "workflow_run", "arguments": {"workflowId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"ok": true, "name": "texte", "runId": "texte", "steps": [], "output": {}, "result": "texte", "stepsRun": 1, "durationMs": 1, "workflowId": "texte", "stepsDefined": 1, "creditsCharged": 1}}

• working_days_between≈ 292 tokens

  Count working days (Mon-Fri) between two dates inclusive, optionally excluding Dutch public holidays. Exact date math for SLA, payroll, and planning questions.

  Paramètres, retour & exemple (3)

  Paramètres

  • end · string · requis
    YYYY-MM-DD
  • start · string · requis
    YYYY-MM-DD
  • excludeDutchHolidays · boolean · optionnel
    Skip Dutch public holidays that fall on a weekday (default true)

  Exemple d'appel

  {"name": "working_days_between", "arguments": {"end": "texte", "start": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"end": "texte", "start": "texte", "result": "texte", "totalDays": 1, "weekendDays": 1, "workingDays": 1, "holidaysExcluded": []}}

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://toolforte.com/api/mcp