Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Ask Japan

REMOTE · ASKJAPAN.SENPINAI.COM

Japanese company, invoice and postcode data, plus real people who do tasks in Japan.

+3 this week 69 Trust /100

Last scanned (22 hours ago)

Scores higher than 53% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Maps and Location

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability81
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 1701 tokens (~100/item across 17 items; 16 tools + 1 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage85
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 55% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 18 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (12)

  • TLS certificate
  • Authorization
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Nov 26 −1
    • Tool coverage: 79% → 55% ▼ functional
    • Schema quality: 1426 → 1701 ▼ functional
    • New tool “search_osaka_stays” functional
    • New tool “submit_osaka_booking_request” functional
  • 17 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 13 Nov 26 66

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://askjapan.senpinai.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=senpinai.com CN=WE1,O=Google Trust Services,C=US 5 Oct 2026 3 Jan 2027 ECDSA 256 ECDSA-SHA256 fef7845646980055137a0020302d343d
SANs: senpinai.com, *.senpinai.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of askjapan.senpinai.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
senpinai.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://askjapan.senpinai.com/mcp Verified 200
http (plaintext) http://askjapan.senpinai.com/mcp Inconclusive 405
MCP tools · 16 exposed · ~1,558 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
check_availability ~53

Check whether a new request can be taken now. Remote work (calls, online reservations) has a daily limit; on-the-ground work takes one job at a time. Returns open or full and when it reopens.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

check_invoice ~63

Check whether a Japanese corporation is a registered Qualified Invoice Issuer (needed for consumption-tax credit). Accepts T + 13 digits or the 13-digit corporate number.

NameTypeReqDescription
numberstringyesInvoice registration number (T1234567890123) or corporate number

No output schema declared.

No examples provided.

check_open ~41

Check whether a MARU Order restaurant is taking takeout orders now, its hours and whether it accepts JPYC with a discount.

NameTypeReqDescription
shopstringyes–

No output schema declared.

No examples provided.

get_company_profile ~61

One profile for a Japanese corporation from its 13-digit corporate number: registered name and address, invoice (tax) registration status, and listing, industry and capital if it files with EDINET.

NameTypeReqDescription
corporate_numberstringyes13-digit corporate number

No output schema declared.

No examples provided.

get_menu ~71

Get a MARU Order restaurant's menu: categories, items with tax-included JPY prices, options (size, toppings), allergens and sold-out flags. Use list shop slugs from the maru://order/shops resource.

NameTypeReqDescription
shopstringyesShop slug, e.g. maru-demo

No output schema declared.

No examples provided.

get_request_status ~55

Get the status of a request: received, quoted (price and how to pay), paid, in_progress, done (with result), cancelled or refunded.

NameTypeReqDescription
request_idstringyesThe request_id returned by request_service

No output schema declared.

No examples provided.

list_services ~63

List the services MARU Japan Hands provides in Japan (Japanese phone calls, restaurant and golf reservations, shopping proxy, on-site checks, interpreting, Osaka stays, home search and property viewings, app development), with prices in JPY, limits and what is not offered.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

lookup_postcode ~52

Get the address for a 7-digit Japanese postcode, including large offices that have their own postcode.

NameTypeReqDescription
postcodestringyes7 digits, hyphen optional, e.g. 530-0001

No output schema declared.

No examples provided.

place_takeout_order ~113

Place a takeout order. Returns an order number and a link. The customer pays at pickup at the counter, or opens the link to pay with JPYC (discounted). This tool never charges or moves money.

NameTypeReqDescription
contactstring–Phone or email for the shop to reach the customer
itemsarrayyes–
namestringyesName for the order
pickup_timestringyesPickup time today in JST, HH:MM
shopstringyes–

No output schema declared.

No examples provided.

quote_purchase ~212

Instant cost estimate to buy an item sold in Japan and ship it: item price (from the shop page the user or agent found), our fee (10%, minimum JPY 2,000) and shipping estimated from Japan Post's official EMS table. Read-only: it does not order or charge anything.

NameTypeReqDescription
estimated_weight_kgnumber–Item weight in kg if known (default 1.0)
item_namestring–Product name
item_price_jpyintegeryesPrice per unit in JPY, tax included, as shown on the shop page
item_urlstring–Product page URL in Japan (Rakuten, Amazon.co.jp, brand store, etc.)
quantityinteger––
seller_shipping_jpyinteger–Shop's shipping to our address in Japan, if any
ship_to_countrystringyesISO 2-letter country code of the destination, e.g. US, TW, CN; JP for Japan

No output schema declared.

No examples provided.

request_service ~234

Send a request for a service in Japan. Fixed-price services (phone_call JPY 1,500, restaurant_booking JPY 3,000, interpreting JPY 5,000 per 30 min) return the quote and payment details immediately. Other services get a fixed quote from a person within 2 hours (JST 09:00-21:00); requests sent outside hours are handled from 09:00. No email is needed: follow up with get_request_status. Creating a request is free and does not move any money. Full refund if we cannot do the task or you cancel before work starts.

NameTypeReqDescription
budget_jpyinteger–Optional budget in JPY
callback_urlstring–Optional public https URL that receives status updates as JSON
contact_emailstring–Optional email for the quote and result
detailsstringyesWhat, where, when, how many people, names, constraints
languagestring–Preferred language for replies, e.g. en, ja, zh
servicestringyesService id from list_services

No output schema declared.

No examples provided.

search_address ~46

Find postcodes by part of a Japanese address or an office name, e.g. 大阪市北区梅田.

NameTypeReqDescription
textstringyesPart of the address in Japanese

No output schema declared.

No examples provided.

search_company ~117

Search all ~5.8 million corporations registered in Japan by name (Japanese, partial match). Returns corporate number, address, type and whether it is closed. Use the corporate number with get_company_profile.

NameTypeReqDescription
include_closedboolean–Include closed corporations (default false)
limitinteger––
namestringyesCompany name or part of it, in Japanese, e.g. トヨタ自動車
prefecturestring–Optional prefecture filter in Japanese, e.g. 大阪府

No output schema declared.

No examples provided.

search_listed_companies ~102

Filter companies that file securities reports in Japan (EDINET) by industry (Japanese name, e.g. 不動産業, 輸送用機器) and minimum capital. Returns securities code and capital.

NameTypeReqDescription
industrystring–EDINET industry name in Japanese
limitinteger––
listed_onlyboolean–Only listed companies (default true)
min_capital_million_yennumber––

No output schema declared.

No examples provided.

search_osaka_stays ~68

查大阪民宿及房型,无需凭证。参考起价不是最终报价。Search Osaka stays and room types; prices indicative.

NameTypeReqDescription
guestsinteger––
limitinteger––
localestring––
querystring––

No output schema declared.

No examples provided.

submit_osaka_booking_request ~207

这是申请不是订成,不锁房、不收费。Home-booking 人工报价及代订。请把返回的专属链接私下交给客人保存,客人本人在该页确认报价后去 Home-booking 刷卡;邮件送达未核实,不可承诺一定收到邮件。绝不在工具里收款或收集卡号、护照。 Only after explicit guest consent to saving contact details and contacting the property. Reuse idempotencyKey on retries. No quote acceptance or checkout in this tool.

NameTypeReqDescription
checkInstringyes–
checkOutstringyes–
consentToContactbooleanyes–
emailstringyes–
guestNamestringyes–
guestsintegeryes–
idempotencyKeystringyes–
localestring––
propertyIdstringyes–
roomIdstringyes–

No output schema declared.

No examples provided.

Install

How do I install the Ask Japan MCP server?

Ask Japan is a hosted endpoint at https://askjapan.senpinai.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · askjapan.senpinai.com

# add to Claude Code
claude mcp add --transport http com-senpinai-ask-japan 'https://askjapan.senpinai.com/mcp'
Common questions

What is the Ask Japan MCP server?

Ask Japan is an MCP server listed in the public MCP registry as com.senpinai/ask-japan. Japanese company, invoice and postcode data, plus real people who do tasks in Japan. This page covers its hosted endpoint (https://askjapan.senpinai.com/mcp).

Is the Ask Japan MCP server safe to use?

Ask Japan scores 69 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Ask Japan MCP server expose?

Ask Japan exposes 16 tools: search_company, get_company_profile, check_invoice, search_listed_companies, lookup_postcode, and 11 more. Their descriptions and schemas cost roughly 1,558 tokens of context every time the server is loaded.

Does the Ask Japan MCP server require authentication?

No. We connected to Ask Japan without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Ask Japan MCP server still maintained?

Ask Japan is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Ask Japan MCP server?

VerifyMCP ran 12 checks on Ask Japan, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Ask Japan: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.