Agent Tools
List
Back to MCP servers

ToolForte

https://toolforte.com/api/mcp
● healthy

180 tools for AI agents. Exact answers instead of guesses: IBAN and VAT checks, VAT amounts, Dutch public holidays and working days, cron parsing, regex testing, JSON, CSV and Base64 transforms, diffs, UUIDs and Dutch test data. 14 render tools turn HTML or a URL into a hosted PDF or screenshot, make QR codes, merge and split PDFs and convert images; read_page returns a JavaScript-rendered page as Markdown. Also agent memory (key-value across sessions), saved workflows and 6 AI tools. initialize, tools/list, search_tools and describe_tool work without a key; other tool calls need a free API key (Authorization: Bearer tf_...) or OAuth. Setup guides per client: https://toolforte.com/mcp

Transport
streamable-http
Auth
bearer_api_key
Cost
Free key with 100 credits/month (1 per tool call, 25 per render, 10 per AI call); Pro EUR 19/month for 7,500 credits
Protocol revision
2025-11-25
negotiated, not declared

MCP readiness

B · 89/100

Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here B+, 89.8/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ

Valid MCP handshake 10/10 initialize and tools/list both answered.
Live MCP endpoint 25/25 Endpoint answers the MCP initialize handshake (648 ms).
Protocol revision 8/10 Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28.
Signed descriptor n/a No MCP standard defines a signed server descriptor.
Uptime (30 days) 15/15 30/30 probes succeeded over 30 days (100%).
Tool declaration 10/10 Lists 14 tool(s) with descriptions.
Verified identity 8/10 Publisher declared (repository, package or homepage) and domain control verified on agent-tools.cloud (company-registry check not available yet).
Freshness + modern flags 2/5 seen within 30 days.
Auth declaration 2/5 Declares credential scheme: bearer_api_key.
Applicable criteria total 90 points, scaled to 100.
Responsiveness: Responsive (648 ms; bands ≤2.5 s, ≤5 s, ≤8 s, slower; penalty only).
Measured 2026-11-11.
Nine criteria, the same as the A2A readiness score, read from our daily MCP probe (initialize + tools/list) and 30-day probe history. No MCP standard defines a signed server descriptor, so that criterion is n/a and the other 90 points are scaled to 100. Grades: A>=90, B>=75, C>=60, D>=40, F<40. Display only: search order uses the quality grade.

Compared with peers

Against 53,039 reachable MCP servers in our daily snapshot (2026-11-12 06:46 UTC). Display only; it does not change search order.

Readiness
Higher than 96% of peers
This listing 89 · peer median 81
Latency
Faster than 24% of peers
This listing 572 ms · peer median 326 ms

Where it loses the most points, and how to win them back

  • Freshness + modern flags −3 — Keep the listing current in the registry or source it comes from.
    Now: seen within 30 days.
  • Auth declaration −3 — State how to authenticate (an auth scheme, or that none is needed).
    Now: Declares credential scheme: bearer_api_key.
  • Protocol revision −2 — Support the current protocol revision.
    Now: Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28.

How many agent tools actually work · All statistics

Listed in

Directories this entry was found in.

mcp-registry since 2026-08-27 agenstry since 2026-10-22 ↗

How to connect

MCP endpoint (streamable-http)
https://toolforte.com/api/mcp
JSON-RPC initialize probe
curl -X POST https://toolforte.com/api/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'
Homepage
https://toolforte.com/mcp