Japan TITP Administrative Actions

io.github.mk-career-planningPublished by GitHub account mk-career-planningv0.1.0Updated Oct 24, 2026

Published TITP actions (ISA) on Japanese intern supervising/implementing orgs. Tracks file changes.

The publisher's own server: actions.world

VerifiedStreamable HTTPWeb executableData & AnalyticsBusiness & Commerce

Overview

AI-generated overview

Looks up ISA administrative actions on Japanese TITP supervising and implementing organizations and tracks changes in the published files.

What you can do
List the server's tools with prices, data sources, licensing, daily limits and data freshness. Look up whether a TITP supervising or implementing organization has an ISA-published administrative action, by permit number, plan certification number or organization name, optionally with a prefecture. Find administrative actions added or changed in ISA's published files since a date, with changed fields and before/after values. Re-fetch the stored result of a settled paid call by receipt_id.
When to use it
Use it to check whether a Japanese TITP supervising or implementing organization has an ISA-published administrative action, or to track actions added or changed in ISA's published files since a date.
Requirements
Remote HTTP endpoint; no local runtime needed. No authentication, environment variables or headers are declared. Some lookups are paid calls and network access is required.
Before you install
Lookup tools are paid calls that cost money; a lost response can be re-fetched free by receipt_id, with results kept 90 days. Data comes from ISA's published files and reflects only that source.

Installation

In SourceWeft

  1. Open Japan TITP Administrative Actions in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.mk-career-planning%2Fjp-titp-actions/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "japan-titp-administrative-actions": {
      "type": "http",
      "url": "https://jp-titp-actions-production.mk-career-planning.workers.dev/mcp"
    }
  }
}

Tools

4

catalog

Catalog: tools, prices and limits

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

Takes no parameters.

titp_action_lookup

Look up published TITP administrative actions

Has this TITP supervising or implementing organization in Japan had an administrative action published by ISA, and when? Look up by permit number (1708000404), plan certification number (1704019156) or organization name (exact after normalization; partial = candidates), optional prefecture. Returns listed, not_found_in_checked_records (not proof of no action; actions no longer published are not returned) or unknown, with type, date, reason as published, source file and as-of date.

Parametersnamelimitprefecturepermit_numbercertification_number

titp_action_changes

TITP administrative action file changes

Which TITP administrative actions were added to or changed in ISA's published files since a date? From this service's own record of file versions (ISA publishes only the current files). Each change has the action id, observed_at, changed fields and before/after. Actions that ISA no longer publishes are not returned; only the number that left the files per version is shown, without identifiers. History starts at tracking_since. Free window: last 30 days.

Parameterslimitsincerequiredchange_typetarget_type

get_receipt

Get receipt of a paid call

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.

Parametersreceipt_idrequired

Version history

1
  1. v0.1.0LatestOct 24, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Actions integrations