jp-mlit-recalls
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
@pipeworx/jp-mlit-recalls
Has this vehicle maker or importer filed a recall (リコール) or an improvement measure (改善対策) with Japan's Ministry of Land, Infrastructure, Transport and Tourism (国土交通省)?
Part of Pipeworx — an MCP gateway connecting AI agents to 2014+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.
Tools
jp_mlit_recalls_search(name?, kind?, year?, years_back?, limit?)— filter the ministry's public notification lists by filing company (Japanese short name as printed, e.g. トヨタ, or a common English spelling) and kind. Each match gives the filing date, recall or improvement measure, the companies that filed and a link to the ministry's press release. Also returnsresult(hit/no_hit),total_matches,notifications_read,covers,individuals_droppedanddata_as_of. Default scope is the latest two calendar years; one year back to 2001 or up to five latest years can be asked for.jp_mlit_recalls_get(link)— one press release: the heading with the model names, the kind, the filing date, the filing company's full legal name and the title, format and size of the attached documents.
Related MCP server: china-recalls
Auth
Keyless.
Data sources
Japan Ministry of Land, Infrastructure, Transport and Tourism (国土交通省), notifications of motor-vehicle recalls and improvement measures. Cars, trucks, motorcycles and work vehicles. Read from the publisher on request and held in the serving process for an hour.
data_as_ofis the day the lists were read;covers.tois the latest filing.
Behaviour worth knowing
The lists name filing companies, not models; model names are in each press release's heading. The defect, number of vehicles and chassis ranges are in attached documents that are not read; every response says so.
Only the years read are checked, and the response lists them in
query.years_read. No hit means no filing by that company in those years, as read now; it does not clear the company.Filers are manufacturers and importers. A name in an individual's honorific form would be dropped and counted in
individuals_dropped. The ministry's inquiry-office contact details are never returned.A list without the expected markup, a year that parses to nothing or an HTTP failure is refused, so a source that is down is never read as "no recall found".
Quick Start
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"jp-mlit-recalls": {
"url": "https://gateway.pipeworx.io/jp-mlit-recalls/mcp"
}
}
}What this endpoint actually serves
tools/list at https://gateway.pipeworx.io/jp-mlit-recalls/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}Both URLs reach the same gateway and the same 2014+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
No MCP client? Call it over HTTP
curl -X POST https://gateway.pipeworx.io/v1/tools/jp_mlit_recalls_search \
-H 'Content-Type: application/json' \
-d '{"name":"トヨタ"}'No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/jp_mlit_recalls_search. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.
Run it from npm
@pipeworx/mcp-jp-mlit-recalls is a local stdio bridge to the Pipeworx gateway: your MCP client
starts it with npx, and it forwards every call to the same
https://gateway.pipeworx.io/jp-mlit-recalls/mcp endpoint shown above. It needs network access;
there is no offline mode.
{
"mcpServers": {
"jp-mlit-recalls": {
"command": "npx",
"args": ["-y", "@pipeworx/mcp-jp-mlit-recalls"]
}
}
}Without a key it calls anonymously, capped at 50 calls a day. A free account
raises that to 200 a day: get a key at https://pipeworx.io/signup and add
"env": { "PIPEWORX_API_KEY": "<your key>" } to the server entry.
The key is sent as a Bearer token, the same way a hosted connection sends it,
so calls are metered and billed exactly as they are there.
It lists only this pack's tools by default. Set PIPEWORX_META_TOOLS=1 to
also list ask_pipeworx and the other gateway-wide tools.
Behind an HTTPS proxy: Node's built-in fetch does not read HTTPS_PROXY by
default. Newer Node releases honour it when NODE_USE_ENV_PROXY=1 is set; check
your Node version's documentation.
Using with ask_pipeworx
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Jp Mlit Recalls data" })The gateway picks the right tool and fills the arguments automatically.
More
License
MIT
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Search Japanese product recalls by keyword and category using public Consumer Affairs Agency data.
Check U.S. NHTSA vehicle safety recall campaigns by make, model, and year. Live official data.
UK MOT failure data and official UK, French, Japanese and EU vehicle recalls.
Search Japanese subsidies and public company data using J-Grants, gBizINFO, and EDINET.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to look up US NHTSA and EU Safety Gate car recalls and complaints, compare a model's years by risk score, check UK MOT failure rates, retrieve EU vehicle specifications with WLTP CO2 and fuel consumption, and verify Cyprus company records, EU VAT numbers via VIES and LEIs. It draws only on official open data and is hosted through Apify, so nothing needs to be installed.MIT
- AlicenseNot gradedqualityCmaintenanceEnables searching and retrieving Chinese product recall announcements from the State Administration for Market Regulation, with title, category and date filters plus full notice text including recalling company, units affected, defect and remedy details. Answers questions about whether a company or product has been recalled in China and when.90 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to read public vehicle data such as NHTSA recalls, complaints, and crash ratings, EPA engines and fuel economy, Transport Canada dimensions, and published bilingual automotive guides through search and retrieval tools.96 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables searching Japanese Consumer Affairs Agency announcements of administrative dispositions and surcharge orders against businesses by company name, returning dates, laws, order types, business types, named companies, titles, and source links.MIT