Toolforte

Last 30 days

Uptime

100%

Response time

537 ms typical, 1.1 s slowest 5%

Last check

7 h ago

Next check

any minute now

How to call it

Add it to any MCP client that supports remote servers.

{
  "mcpServers": {
    "toolforte": {
      "type": "http",
      "url": "https://toolforte.com/api/mcp"
    }
  }
}

14 tools

• text_diff

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

• format_json

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

• csv_to_json

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

• test_regex

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

• validate_iban

  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 type

• calculate_vat

  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.

• dutch_public_holidays

  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.

• working_days_between

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

• workflow_list

  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

• workflow_propose

  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

• workflow_run

  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

• search_tools

  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

• describe_tool

  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.

• run_tool

  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.

Security scan

• No findings. We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.

Recent checks