io.github.mk-career-planning/jp-finance

Est-ce que io.github.mk-career-planning/jp-finance est sûr ?

Au dernier audit MCP Hub, le serveur MCP « io.github.mk-career-planning/jp-finance » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 7 outils

• catalog≈ 799 tokens

  List the tools of this server with prices, data sources, licensing, daily limits and data freshness.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "catalog", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"legal": {}, "terms": "texte", "tools": [], "paused": {}, "server": {}, "payment": {}, "provenance": [], "daily_limits": {}, "fetch_status_values": {}}}

• fsa_enforcement_by_corporate_number≈ 1677 tokens

  Which rows of the Japan FSA case list of adverse administrative actions (business improvement or suspension orders and similar, by the FSA and Local Finance Bureaus, fiscal 2002 to the list's as-of date) state this 13-digit corporate number? Rows as published: date, action type, legal basis, business type, lifted flag, with the list version, SHA-256 and the scope of what was checked. Zero rows is not_found_in_checked_records with that scope; after the as-of date is unknown. No name search.

  Paramètres, retour & exemple (2)

  Paramètres

  • since · string · optionnel
    Optional: only actions published on or after this date (YYYY-MM-DD). A date after the list's as-of date returns unknown.
  • corporate_number · string · requis
    13-digit Japanese corporate number (houjin bangou), e.g. 3010401049814. The check digit is verified.

  Exemple d'appel

  {"name": "fsa_enforcement_by_corporate_number", "arguments": {"corporate_number": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"query": {}, "scope": {}, "terms": "texte", "total": 1, "source": {}, "status": "listed", "actions": [], "registry": "texte", "authority": "texte", "truncated": true, "provenance": [], "source_url": "texte"}}

• fsa_register_changes≈ 1871 tokens

  Which entries were added to, dropped from, changed in or returned to Japan FSA registers and warning lists since a date? From this service's own record of list versions (the FSA publishes only current lists). Each change has the list, registration number, name as published (personal names withheld), before/after fields, observed_at and the list as-of date. Reasons are not published or inferred. History starts at tracking_since; free window: last 30 days.

  Paramètres, retour & exemple (4)

  Paramètres

  • list · string · optionnel
    Optional: one list id (fib, cae, epi, fts, ml, w_fib_dom, w_fib_ovs, w_fib_qii, w_cae_dom, w_cae_ovs) or registers / warnings; default all lists
  • limit · integer · optionnel
    Maximum number of changes, 1-500 (default 100)
  • since · string · requis
    ISO 8601 date or date-time with time zone, e.g. 2026-10-01 or 2026-10-01T00:00:00Z
  • change_type · string · optionnel · added | no_longer_listed | details_changed | relisted
    Optional filter: added, no_longer_listed, details_changed or relisted

  Exemple d'appel

  {"name": "fsa_register_changes", "arguments": {"since": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"lists": [], "query": {}, "terms": "texte", "changes": [], "coverage": {}, "name_note": "texte", "truncated": true, "provenance": [], "answered_at": "texte", "history_note": "texte", "legal_notice": "texte", "checked_until": "texte"}}

• get_receipt≈ 676 tokens

  Re-fetch the stored result of a settled paid call by its receipt_id, for when the response was lost after payment. Free. Unknown or unsettled receipt ids return RECEIPT_NOT_FOUND. Results are kept for 90 days after settlement.

  Paramètres, retour & exemple (1)

  Paramètres

  • receipt_id · string · requis
    The receipt_id returned with a paid result ("rcpt_" + 64 hex characters).

  Exemple d'appel

  {"name": "get_receipt", "arguments": {"receipt_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"tool": "texte", "terms": "texte", "result": "texte", "payment": {}, "provenance": [], "receipt_id": "texte", "settled_at": "texte"}}

• jp_customs_fx≈ 722 tokens

  Which JPY rate did Japan Customs publish for this currency on this date? Input: ISO 4217 code and YYYY-MM-DD date. Returns status (valid/invalid/unknown), the inclusive effective period, the JPY rate as published with its base units (1 or 100), source URLs, retrieval and verification times and SHA-256 hashes. Dates from 2021-08-15. Unpublished periods and unlisted currencies return unknown. Reference for customs and bookkeeping only; not a market or remittance rate; no tax calculation.

  Paramètres, retour & exemple (2)

  Paramètres

  • date · string · requis
    Calendar date YYYY-MM-DD (Japan), e.g. 2026-10-07
  • currency · string · requis
    Uppercase ISO 4217 alpha-3 code, e.g. USD

  Exemple d'appel

  {"name": "jp_customs_fx", "arguments": {"date": "texte", "currency": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"rate": "texte", "query": "texte", "terms": "texte", "notice": "texte", "reason": "matched", "status": "valid", "sources": [], "answered_at": "texte", "dataset_version": "texte", "effective_period": "texte"}}

• jp_customs_fx_batch≈ 1216 tokens

  Which JPY rates did Japan Customs publish for these 1-50 currency/date pairs? One call returns ordered per-item status, effective periods, JPY rates as published with base units (1 or 100), source URLs, retrieval and verification times and hashes, read from one dataset snapshot. Dates from 2021-08-15. Unpublished periods and unlisted currencies return unknown. Not charged if no item can be answered. No date selection, tax calculation, market or remittance rates, or forecasts.

  Paramètres, retour & exemple (1)

  Paramètres

  • items · array · requis
    1 to 50 items {currency, date}; order kept, duplicates answered twice

  Exemple d'appel

  {"name": "jp_customs_fx_batch", "arguments": {"items": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• jp_fsa_registry_lookup≈ 1406 tokens

  Is this business (name, registration or 13-digit corporate number) on a Japan FSA register or warning list? Exact match (optional domain) against FSA registers (financial instruments, crypto-asset exchange, electronic payment instruments, funds transfer, money lending) and warnings to unregistered businesses. Returns matches with registration type, entity tie (domain alone: unverified), name candidates and as-of dates. Stated scope only; no warning match is not proof none exists. No advice.

  Paramètres, retour & exemple (3)

  Paramètres

  • name · string · optionnel
    Business name as written, e.g. 株式会社SBI証券 or Bybit Fintech Limited
  • domain · string · optionnel
    Optional domain or URL, e.g. example.com
  • number · string · optionnel
    Registration number (e.g. 関東財務局長(金商)第44号) or 13-digit corporate number

  Exemple d'appel

  {"name": "jp_fsa_registry_lookup", "arguments": {"name": "texte", "domain": "texte", "number": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"note": "texte", "query": {}, "terms": "texte", "provenance": [], "answered_at": "texte", "interpreted": {}, "not_covered": [], "source_errors": [], "name_candidates": {}, "sources_checked": [], "coverage_complete": true, "entity_resolution": {}}}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://jp-finance-production.mk-career-planning.workers.dev/mcp