Cuelark Tools

At a glance

Runs where

On their server. What you send to it goes to them.

What you need

Nothing: it answered without a login

Tools

15 tools

Its own safety labels

15 read-only

Memory it takes

About 3,200 tokens of your AI's memory, just for its tool descriptions

Largest answer

About 2.6 KB in our test

Speed

Average answer in our test: 135 ms

Tokens are an estimate: the characters in its tool names, descriptions and inputs, divided by 4. The exact number depends on your AI model. Safety labels are what the server says about itself. From our latest test, 10 Nov 2026.

Is Cuelark Tools MCP server safe?

• None of the hidden-instruction wordings we know were found in its 15 tool descriptions.
• Its error messages showed no secrets or internal details.
• All 15 of its tools are labeled read-only.
• Overall it scored 83/100 on 10 Nov 2026.

A test can only see what the server shows from outside, not what it does with your data behind the scenes. Connect servers from makers you trust.

What this test does not check

• Its source code and packages.
• What a tool quietly does behind the scenes, such as writing a file or calling another service.
• Instructions hidden inside live tool answers. We only look for those in tool descriptions.
• Hidden instructions worded in a way our list doesn't know yet.
• Tools that could change something. Those are read, never run.

What QAmcp can and can't see · How to tell if an MCP server is safe · Hidden instructions · Prompt injection

Known security advisories

It lists no public code, so there is nothing to look up in GitHub Security Advisories or OSV.dev. QAmcp tests how a server behaves. It does not scan source code.

What it can do

15 tools, in the server's own words.

Test results

Safe mode: only tools labeled read-only were run. How the test works

• !
  Ready for the newest MCP version

  1 warning

  • !Uses an older MCP version (2025-11-25). It works today, but it isn't on the July 2026 version (2026-07-28) yet.
  note
• !
  Every tool is described

  15 warnings

  • !json: Inputs with no description: op, indent, sort_keys
  • !text: Inputs with no description: op, text, flags, replace, encoding
  • !dates: Inputs with no description: op, unit, year, exam, timezone
  • !time: Inputs with no description: op, zone, from_zone, to_zone
  • !encode: Inputs with no description: op, text, algo, url_safe, version, count
  • !convert: Inputs with no description: op, direction, width, height, unit, dpi, scheme, cgpa, percentage
  • !finance: Inputs with no description: op, amount, months, years, compounding, monthly_contribution, percent_op, a, b, kind, inter_state
  • !calculate: Inputs with no description: op, expression, values, value, decimals, mode, weight_lb, height_in, weight_kg, height_cm
  • and 7 more
  note
• !
  Bad inputs give a clean error

  7 warnings

  • !json: Accepted wrong type for "input" without complaining
  • !text: Accepted wrong type for "text" without complaining
  • !time: Accepted wrong type for "date" without complaining
  • !calculate: Accepted wrong type for "expression" without complaining
  • !verify_links: Accepted wrong type for "urls" without complaining
  • !package_check: Accepted wrong type for "name" without complaining
  • !ui_component_lookup: Accepted wrong type for "query" without complaining
  • and 15 more
  note
• ✓
  ConnectsConnected in 811 ms
  pass
• ✓
  Lists its toolsFound 15 tools
  pass
• ✓
  Tools are labeled safe or dangerousEvery tool has a safety label
  pass
• ✓
  No known hidden instructionsNone of the hidden-instruction wordings we know were found in tool descriptions. New wordings can get past this check.
  pass
• ✓
  Tools work with good inputs

  All good

  • ✓json: Answered with an error, probably because of our sample input: Invalid JSON: Unexpected token 'e', "test" is not valid JSON
  • ✓text: Answered with an error, probably because of our sample input: "text" is required
  • ✓time: Worked (69 ms)
  • ✓encode: Answered with an error, probably because of our sample input: "text" is required
  • ✓convert: Answered with an error, probably because of our sample input: "value" must be a number
  • ✓calculate: Answered with an error, probably because of our sample input: "expression" is required
  • ✓income_tax: Worked (42 ms)
  • ✓validate: Worked (41 ms)
  • and 7 more
  pass
• ✓
  Fast enough

  All good

  • ✓Connecting took 811 ms
  • ✓Listing tools took 61 ms
  • ✓Average tool answer: 135 ms
  • ✓ifsc_lookup: Slowest tool: ifsc_lookup (886 ms)
  pass
• ✓
  No secrets leakedChecked 22 error messages: no secrets or internal details
  pass
• ✓
  Follows MCP best practices (not scored yet)Tool names, safety labels and tool list size follow the MCP guide
  pass
• –
  Tools work togetherNo tool's answer could be fed into another tool, so there were no chains to test (not counted either way)
  not tested

Test it yourself

Free and open source. Same checks, same score.

Show this score on GitHub

Free for every server in the directory. Paste this into your README: the badge shows the score from our latest test.

Score over time

• 10 Nov 202683

One test so far. New tests will show here.

Reviews

Coming soon: reviews from people who use Cuelark Tools, signed in with GitHub, one per person. Reviews never change the score.