jp-mic-actions
by pipeworx-io
README.md
# @pipeworx/jp-mic-actions
Has Japan's Ministry of Internal Affairs and Communications (総務省) announced
guidance (指導), an order or another administrative measure against this
company, for example a telecom carrier, an internet provider or a radio-equipment
maker?
Part of [Pipeworx](https://pipeworx.io) — 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_mic_actions_search(name, limit?)` — exact or partial company-name match after
Unicode folding and dropping corporate-form words. Each match gives the release
date, the companies named, the release title, the issuing bureau and a link to the
ministry's release. Also returns `result` (`hit` / `no_hit`), `total_matches`,
`notices_read`, `months_read`, `covers`, `unnamed_notices` and `data_as_of`.
- `jp_mic_actions_read(link)` — one release: its heading and the attached documents
(title, format, link) that state what the ministry required.
## Auth
Keyless.
## Data sources
- Japan Ministry of Internal Affairs and Communications (総務省), press releases
(報道資料). The latest 12 monthly press lists are read from the publisher on
request and held in the serving process for an hour. The ministry publishes no
table of measures, so each measure is found from the title of its release, which
names the company. `data_as_of` is the day the lists were read; `covers.to` is the
latest matching release.
## Behaviour worth knowing
- The window is the latest 12 months, not the full history; `covers` says which.
- Titles that name no company (for example a guidance notice about a reporting
error) cannot be searched by name and are counted in `unnamed_notices`.
Individuals are never served. The ministry's own policy-evaluation follow-ups
(recommendations to ministries) are excluded.
- No hit means no release naming that company in the window read; it does not clear
the company. A list that cannot be read, or that changed format, is an error and is
never reported as no hit.
## Quick Start
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
```json
{
"mcpServers": {
"jp-mic-actions": {
"url": "https://gateway.pipeworx.io/jp-mic-actions/mcp"
}
}
}
```
### What this endpoint actually serves
`tools/list` at `https://gateway.pipeworx.io/jp-mic-actions/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:
```json
{
"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
```bash
curl -X POST https://gateway.pipeworx.io/v1/tools/jp_mic_actions_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_mic_actions_search`. Find one: `POST https://gateway.pipeworx.io/v1/tools/search_packs` with `{"query":"..."}`.
## Run it from npm
`@pipeworx/mcp-jp-mic-actions` 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-mic-actions/mcp` endpoint shown above. It needs network access;
there is no offline mode.
```json
{
"mcpServers": {
"jp-mic-actions": {
"command": "npx",
"args": ["-y", "@pipeworx/mcp-jp-mic-actions"]
}
}
}
```
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 Mic Actions data" })
```
The gateway picks the right tool and fills the arguments automatically.
## More
- [Docs and guides](https://pipeworx.io/docs)
- [pipeworx.io](https://pipeworx.io)
## License
MIT
This server cannot be deployed
Maintenance
ActivityMaintained
ResponsivenessNo recent community issues