Look up a supplier's award history by 法人番号 over MCP

Why look up a supplier by corporate number

A market researcher checking what a counterparty or competitor has won from government buyers runs into trouble searching by name: spellings vary, and unrelated firms share names. The corporate number avoids both problems. Japan's National Tax Agency assigns each corporation one thirteen-digit number, and that number points to exactly one company.

Hashike is a bilingual research service that organizes US federal contract opportunities performed in Japan and Japanese central-government award results. It joins the Japanese award records to their suppliers by corporate number, and the supplier_profile tool is how an AI assistant or a program retrieves that per-company summary.

MCP (the Model Context Protocol) is a standard way for AI assistants to call outside tools. Once you connect to Hashike over MCP, one corporate number and an API key get you that company's award-history summary, whether you ask through an AI assistant or call from your own script. The final section sets out what the summary leaves out.

What supplier_profile returns

The tool covers Japanese central-government award results. It counts over a rolling sixty-month window that ends when you call it.

• ·The exact award count and award value within the window
• ·The ministries that bought from the company
• ·The contract methods used
• ·Recent awards, included when you set the includeAwards parameter
• ·Registry facts about the company, where Hashike has them cached

Amounts are in yen. US federal dollar figures come from a different government, source and fiscal calendar, so the two cannot be summed or ranked against each other.

Making the call

Hashike's MCP server is a remote HTTP endpoint at https://hashike.io/api/mcp that accepts JSON-RPC requests over POST. There is no package to install, no local process to run and no environment-variable configuration.

1. Get the corporate number of the company you want to look up. Each Hashike company page under /companies shows the number.
2. Have your credentials ready: a Hashike API key (prefix hsk_live_) or a Supabase OAuth access token.
3. Send requests to the endpoint with an Authorization: Bearer <token> header. Putting the raw API key in an x-api-key header also works.
4. The server answers initialize, ping, tools/list and tools/call. A tools/list call shows that supplier_profile takes corporateNumber, which is required, and includeAwards.
5. Send tools/call with name set to supplier_profile and the corporate number in the corporateNumber argument. The code example below shows the shape.
6. An AI assistant such as Claude, once connected to the endpoint, makes the same call for you when your request includes the corporate number.

Use the Hashike supplier_profile tool for corporate number <corporate number> with includeAwards set. Summarize the award count and value, the ministries that bought from this company and its contract methods. State the period the figures cover and keep all amounts in yen.

curl -X POST https://hashike.io/api/mcp \
  -H "Authorization: Bearer <token>" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":"<request id>","method":"tools/call","params":{"name":"supplier_profile","arguments":{"corporateNumber":"<corporate number>","includeAwards":true}}}'

The same data over the public API

supplier_profile has a matching companies endpoint on the public API that takes the corporate number in its path and returns the same summary over GET, without MCP. The developer page at /developers lists every endpoint. Hashike's service registry defines 9 tools on the MCP server and 11 public API endpoints.

The registry lists 3 download formats: Markdown export, Markdown copy and PDF. Hashike does not offer a CSV or Excel export.

Scope and allowance

supplier_profile counts Japanese central-government award results only, so a company's US federal contracts do not appear in it. For the US side, search_opportunities finds opportunities and us_buyer_profile summarizes one US agency's contracting.

API and MCP access is metered against a plan allowance, and every response states what is left. The public API also has a usage endpoint that reports consumption.

This page describes Hashike's capabilities as they stood when it was verified. Tools and output formats change; the verification date is stated at the foot of the page.