jp-fsa-licensed
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-fsa-licensed
Is this company on a Japan Financial Services Agency (金融庁) register of
licensed or registered financial business operators, under which category, and
with which registration number? The positive side of jp-fsa-warnings (which
lists the unregistered operators the agency has warned).
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_fsa_licensed_search(name, category?, limit?)— exact or partial name match across the covered registers after Unicode folding, old-form kanji folding (證 = 証) and dropping corporate-form words. Each match is the agency's own row: category, registration number, registration date, registering bureau (from the registration number), the list's own 所管 (jurisdiction), 13-digit corporate number where the list carries it, postal code, registered-office address, phone, the business types and trade associations held (financial instruments and funds transfer lists), and the crypto assets or payment instruments handled (crypto-asset and electronic payment instrument lists). Also returnsresult(hit/no_hit/unavailable),total_matches,categories_checked(list size and date for each),categories_failed,not_coveredanddata_as_of(the oldest list date among those read).
Related MCP server: edinet
Covered (18 company registers)
Financial instruments business operators (securities, investment advice, management; ~1,950 firms), crypto-asset exchange service providers (27), electronic payment instrument service providers (2), funds transfer service providers (84), banks incl. foreign bank branches (189), bank holding companies, registered financial institutions (891), life insurers, non-life insurers, insurance holding companies, insurance brokers, shinkin banks, credit cooperatives, money lenders registered with a Local Finance Bureau (246), electronic payment agency service providers, trust companies, registered investment corporations, third-party prepaid payment instrument issuers (787).
Not covered
Financial instruments intermediaries and self-issued prepaid instruments: their lists name natural persons, so they are not read at all.
The financial instruments register itself includes a handful of sole proprietors (no corporate number, no company form in the name); those rows are dropped and counted in
omitted_persons.Agents and intermediaries (bank agents, financial service intermediaries, electronic payment agents of cooperative banks), clearing houses, trade repositories, rating agencies, auditing firms and the other small registers on the agency's licence page: not read yet.
Operators registered only with a prefectural governor.
Auth
Keyless.
Data sources
Japan Financial Services Agency (金融庁), registers of licensed and registered financial business operators, one list per business category. Read from the publisher on request and held in the serving process for an hour; each list's own "as of" date is
data_as_of. Roughly 1.7 MB of lists in total, all categories read on a cold call.
Behaviour worth knowing
Names on the lists are mostly Japanese; an English-name query only matches firms registered in Latin script (bitFlyer, SBI VC Trade) and a katakana query will not match those.
A header row that changes, a list that parses to implausibly few rows, a stated total that disagrees with the rows read, or a non-spreadsheet answer is refused rather than read as zero. A list that cannot be read is named in
categories_failedand turns a would-beno_hitintounavailable.Not on a register is not a finding of unlicensed activity; a hit can be a different party with a similar name.
Quick Start
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"jp-fsa-licensed": {
"url": "https://gateway.pipeworx.io/jp-fsa-licensed/mcp"
}
}
}What this endpoint actually serves
tools/list at https://gateway.pipeworx.io/jp-fsa-licensed/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_fsa_licensed_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_fsa_licensed_search. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.
Run it from npm
@pipeworx/mcp-jp-fsa-licensed 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-fsa-licensed/mcp endpoint shown above. It needs network access;
there is no offline mode.
{
"mcpServers": {
"jp-fsa-licensed": {
"command": "npx",
"args": ["-y", "@pipeworx/mcp-jp-fsa-licensed"]
}
}
}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 Fsa Licensed 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
Japanese public records on 1-10 companies per call: FSA, MOF, EDINET, ISA, gBizINFO. Evidence only.
Judge Japanese companies against your criteria using Japan's public data (gBizINFO, NTA, EDINET).
HKMA, Japan FSA, Taiwan FSC licence registers plus OFAC sanctions screening; pay per call via x402
Japan company checks by corporate number: status, closure cause, successor, LEI and sanctions.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceEnables querying the Japanese corporate registry from METI's gBizINFO for company profiles, government procurement, subsidies, patents, certifications, financials, and workplace disclosures using corporate numbers or names.95 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables searching for Japanese companies and retrieving their securities filings from Japan's Financial Services Agency, including daily filing lists and historical filing ranges for specific filers.157 npmMIT
- AlicenseNot gradedqualityCmaintenanceProvides access to the UK FCA Financial Services Register, enabling firm and individual searches, firm details by FRN, appointed representatives lookups, and individual records by IRN.83 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables lookup of any of Japan's 5.8M registered 13-digit corporate numbers for legal name, katakana/English name, address, corporate kind and merger/closure status, with check-digit validation and clear reasons for malformed or missing numbers. Also supports company search by Japanese or romanised name, corporate suffix, and prefecture, bridging to GLEIF LEI records when the tax agency published no English name.82 npmMIT