JPVerify

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

14 tools

Its own safety labels

14 read-only

Memory it takes

About 9,100 tokens of your AI's memory, just for its tool descriptions

Largest answer

About 18.5 KB in our test

Tools that look alike

1 pair of tools with nearly the same description, so the AI may pick the wrong one

Speed

Average answer in our test: 208 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, 8 Nov 2026.

Is JPVerify MCP server safe?

• None of the hidden-instruction wordings we know were found in its 14 tool descriptions.
• Its error messages showed no secrets or internal details.
• All 14 of its tools are labeled read-only.
• Overall it scored 93/100 on 8 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

Not looked up yet. QAmcp tests how a server behaves. It does not scan source code.

What it can do

14 tools, in the server's own words.

Test results

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

• !
  Every tool is described

  1 warning

  • !jp_invoice_issuer_match and jp_invoice_issuer_match_extract have nearly the same description (79% of their words are shared; the only difference: "compare", "structured", "field" vs "read", "before", "matching"), so an AI may not know which
  note
• ✓
  ConnectsConnected in 629 ms
  pass
• ✓
  Ready for the newest MCP versionUses the latest MCP version (2026-07-28)
  pass
• ✓
  Lists its toolsFound 14 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

  • ✓jpverify_guide: Worked (253 ms)
  • ✓jp_company_verify: Answered with an error, probably because of our sample input: {"code":"validation_error","message":"Request validation failed; no payment was requested or processed.","retryable":false,"detail":[{"type…
  • ✓jp_invoice_registration_verify: Answered with an error, probably because of our sample input: {"code":"validation_error","message":"Request validation failed; no payment was requested or processed.","retryable":false,"detail":[{"type…
  • ✓jp_invoice_issuer_check: Answered with an error, probably because of our sample input: {"code":"validation_error","message":"Request validation failed; no payment was requested or processed.","retryable":false,"detail":[{"type…
  • ✓jp_invoice_extract: Answered with an error, probably because of our sample input: {"code":"validation_error","message":"Request validation failed; no payment was requested or processed.","retryable":false,"detail":[{"type…
  • ✓jp_invoice_extract_and_verify: Answered with an error, probably because of our sample input: {"code":"validation_error","message":"Request validation failed; no payment was requested or processed.","retryable":false,"detail":[{"type…
  • ✓jp_receipt_extract: Answered with an error, probably because of our sample input: {"code":"validation_error","message":"Request validation failed; no payment was requested or processed.","retryable":false,"detail":[{"type…
  • ✓jp_business_card_extract: Answered with an error, probably because of our sample input: {"code":"validation_error","message":"Request validation failed; no payment was requested or processed.","retryable":false,"detail":[{"type…
  • and 6 more
  pass
• ✓
  Bad inputs give a clean error

  All good

  • ✓jpverify_guide: Refused wrong type for "question" with a clear error
  • ✓jp_company_verify: Refused wrong type for "response_language" with a clear error
  • ✓jp_invoice_registration_verify: Refused missing required input "registration_number" with a clear error
  • ✓jp_invoice_registration_verify: Refused wrong type for "registration_number" with a clear error
  • ✓jp_invoice_issuer_check: Refused missing required input "registration_number" with a clear error
  • ✓jp_invoice_issuer_check: Refused wrong type for "registration_number" with a clear error
  • ✓jp_invoice_extract: Refused wrong type for "fields" with a clear error
  • ✓jp_invoice_extract_and_verify: Refused wrong type for "fields" with a clear error
  • and 10 more
  pass
• ✓
  Fast enough

  All good

  • ✓Connecting took 629 ms
  • ✓Listing tools took 571 ms
  • ✓Average tool answer: 208 ms
  • ✓jpverify_guide: Slowest tool: jpverify_guide (253 ms)
  pass
• ✓
  No secrets leakedChecked 31 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

• 8 Nov 202693

One test so far. New tests will show here.

Reviews

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