Unstable preview. Pages, data and API fields can change or break without notice, so please don't rely on this for anything critical yet. See what has changed.
Agent Service Directory
Menu

Johto Data

MCP server · johtodata.com · found in a public list · checked since 2026-11-08

Live, handshake completed · latest check

As JSON

Lints config files for mistakes and compresses documents to a token budget.

Our summary of what its own text says it does: automated, not reviewed by a person (placement-ai/7). What this means

Placed in Validate data and config files: Check JSON, CSV, XML, config and agent instruction files against a schema or format rules, and return the exact errors.

https://johtodata.com/mcp MCP endpoint (Streamable HTTP)

The name is the registry's label, not ours. Not reviewed by a person.

Our checks

An unpaid request daily, from eastern North America

Last 2 checks, oldest to newest; room for 28 more

2 passed, 0 failed, 28 not run.

Passed, 30 daysshort history2 of 2 run
Checks missed0in 30 days
Response, latest114 mswhole handshake
Scheduledailyset by usage; rule below
Checked since2026-11-081 day
Freshnessfreshagainst its schedule

Checked daily. Daily: 5 to 99 payers, and every new service until it has been probed 3 times.

Response times

WindowChecksTimeoutsMedian90th95th99thFastestSlowest
24 hours10——————
7 dayssince 2026-11-0820——————
30 dayssince 2026-11-0820——————

Milliseconds, from eastern North America, timing the whole MCP handshake (initialize to the tools/list answer). Timeouts count at the 10000 ms limit. A dash means too few checks for that figure. As of . Definitions and method.

Details

Tools listed by the server

carton_weightcatalog_diffchina_us_duty_layerscompany_dossiercompany_factscompany_filingscompany_legal_identifierconfig_lintcontext_packcredits/packdataset_checkdns_recordsdocument_searchdocx_to_markdowndrug_ndc_factsecb_fxemail_domain_checkerc20_decodeextract_contactsextract_jsonldfunding_rate_normalizegtin_validatehtml_to_raginjection_scanjobs_feedjson_repairlanded_marginlead_listlisting_qa_enzhofac_crypto_screenpage_structured_extractpii_redactplace_disastersplace_earthquakesplace_weather_alertsproduct_compliance_checklistproduct_device_clearancesproduct_title_normalizerecord_vulnerabilityschema_diff+16

Tools
56
This list since
2026-11-09
First listed to us
2026-11-08
List changes, 90 days
1

Names as the server reported them at our latest completed handshake (mcp-handshake/2); a listed tool is not a tested one. Definitions

Access

Our latest check
Nothing asked
Stated
not stated
Payment model
not known
Currency
not known

"Nothing asked" describes one plain request, not every operation. Statements are claims, not our measurements. Definitions

Interface it declares

Protocol
MCP 2025-06-18
Capabilities
tools
Transports
streamable-http

As its initialize reply stated it at our check on (mcp-handshake/2): a claim, not tested. Definitions

Calls it declares

  • url_to_markdown url*
  • extract_contacts url*
  • context_pack query budget documents*
  • dataset_check csv rows key
  • x402_lint url method header body expected live facilitator mcpUrl mcpTool
  • json_repair text*
  • schema_diff old* new* mode
  • injection_scan text html url
  • pii_redact text* types style
  • config_lint content* kind filename format
  • validate_id items*
  • html_to_rag html url chunkTokens overlapTokens

From the tool list it returned to our check (request-shape/2). * marks a required parameter; after → the fields it says it returns. What it declares, not that a call works.

Listing

In the capability tree: Compute, code and storage / Developer data / Validate and test / Validate data and config files (primary). Placed by three checks by a small AI model: placed, found blind from its tasks, and verified against its own text (placement-ai/7, tree/3) on 2026-11-08. Wrong place? Tell us.

In the directory: meets our listing criteria (listing-criteria/6): ✓ says what it does; ✓ its latest check passed.

Recent probes

WhenResultTime to headers

cloudflare:EWR		 Live, handshake completed HTTP 200 114 ms

cloudflare:EWR		 Live, handshake completed HTTP 200 219 ms

What these figures do not show

  • A passing check means the server completed the MCP handshake with us (initialize, then tools/list, with no credentials; mcp-handshake/2) or asked for credentials first (HTTP 401). It does not show that the server's tools work or what they return. Tool names are as the server listed them.
  • Listed in the Official MCP Registry; this data comes from the Official MCP Registry. Its listing's description is not republished.
  • Limited evidence: monitored for 1 day (less than 30).

Something wrong here?

Operate this service and want it reviewed, corrected or removed? Email hello@agentservicedirectory.com or use the opt-out page. A wrong place in the tree? Tell us.

Machine-readable: /api/v1/services/cand_298fa3b2515de4e6