MARU Japan Hands
REMOTE · MARU.SENPINAI.COM
Human services in Japan for AI agents: phone calls, reservations, shopping and on-site checks.
Available components
Last scanned (20 hours ago)
Scores higher than 46% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Workflow Automation
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
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability80
- 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
- Context-footprint check failed: tool/resource definitions use about 1377 tokens (~114/item across 12 items; 11 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage90
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 71% of tool parameters carry a description.Partial
Tool Safety50
- Injection-marker check failed: the description of tool "maru_wallet_request_payment" contains an instruction to conceal the call from the user, the text "Never tell the user", at byte 213 of that field. See how to fix → Fail
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 13 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
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 →
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.
- 20 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 17 Nov 26 62
First indexed and scored.
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://maru.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 maru.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://maru.senpinai.com/mcp | Verified | 200 | |
| http (plaintext) | http://maru.senpinai.com/mcp | Inconclusive | 405 |
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 →
check_availability 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_open Check if a restaurant is open ~41
Check whether a MARU Order restaurant is taking takeout orders now, its hours and whether it accepts JPYC with a discount.
| Name | Type | Req | Description |
|---|---|---|---|
| shop | string | yes | – |
No output schema declared.
No examples provided.
get_menu Get a restaurant 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.
| Name | Type | Req | Description |
|---|---|---|---|
| shop | string | yes | Shop slug, e.g. maru-demo |
No output schema declared.
No examples provided.
get_request_status 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.
| Name | Type | Req | Description |
|---|---|---|---|
| request_id | string | yes | The request_id returned by request_service |
No output schema declared.
No examples provided.
list_services List services in Japan ~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.
maru_wallet_connect Connect to a MARU wallet ~172
Connect this AI to the user's MARU wallet (Japanese yen stablecoin, JPYC). The user creates a one-time pairing code in the MARU app (Security > Let AI pay > Add an AI) and tells it to you. Returns an agent token and a 4-symbol fingerprint: tell the user the fingerprint and ask them to approve this AI in the MARU app with Face ID. Until they approve, the token does nothing. Keep the token for later calls; never show it to anyone else.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_name | string | yes | A short name the user will recognise in their app, e.g. 'Claude (work laptop)'. |
| pairing_code | string | yes | Code shown in the MARU app, like ABCD-2345. Valid for 10 minutes, usable once. |
No output schema declared.
No examples provided.
maru_wallet_request_payment Ask the wallet owner to approve a payment ~152
File a payment request in the user's MARU wallet. This does NOT pay. The user sees the amount and recipient in the MARU app and approves with Face ID or rejects. Use maru_wallet_request_status to see the outcome. Never tell the user a payment was made until the status is 'done'.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_token | string | yes | – |
| amount_jpyc | integer | yes | Whole JPYC (1 JPYC = 1 JPY) |
| chain | string | yes | – |
| detail | string | – | – |
| title | string | yes | What this payment is for, in the user's language, max 80 characters |
| to | string | yes | Recipient address (0x…) |
No output schema declared.
No examples provided.
maru_wallet_request_status Check a payment request ~60
Status of a request made with maru_wallet_request_payment: pending (waiting for the owner), done (paid; includes the transaction link), rejected, or failed.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_token | string | yes | – |
| request_id | string | yes | – |
No output schema declared.
No examples provided.
place_takeout_order Place a 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.
| Name | Type | Req | Description |
|---|---|---|---|
| contact | string | – | Phone or email for the shop to reach the customer |
| items | array | yes | – |
| name | string | yes | Name for the order |
| pickup_time | string | yes | Pickup time today in JST, HH:MM |
| shop | string | yes | – |
No output schema declared.
No examples provided.
quote_purchase Instant quote for buying in Japan ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| estimated_weight_kg | number | – | Item weight in kg if known (default 1.0) |
| item_name | string | – | Product name |
| item_price_jpy | integer | yes | Price per unit in JPY, tax included, as shown on the shop page |
| item_url | string | – | Product page URL in Japan (Rakuten, Amazon.co.jp, brand store, etc.) |
| quantity | integer | – | – |
| seller_shipping_jpy | integer | – | Shop's shipping to our address in Japan, if any |
| ship_to_country | string | yes | ISO 2-letter country code of the destination, e.g. US, TW, CN; JP for Japan |
No output schema declared.
No examples provided.
request_service Request a service in Japan ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| budget_jpy | integer | – | Optional budget in JPY |
| callback_url | string | – | Optional public https URL that receives status updates as JSON |
| contact_email | string | – | Optional email for the quote and result |
| details | string | yes | What, where, when, how many people, names, constraints |
| language | string | – | Preferred language for replies, e.g. en, ja, zh |
| service | string | yes | Service id from list_services |
No output schema declared.
No examples provided.
How do I install the MARU Japan Hands MCP server?
MARU Japan Hands is a hosted endpoint at https://maru.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 · maru.senpinai.com
claude mcp add --transport http ihouse-corp-maru-japan-hands 'https://maru.senpinai.com/mcp'
What is the MARU Japan Hands MCP server?
MARU Japan Hands is an MCP server listed in the public MCP registry as io.github.ihouse-corp/maru-japan-hands. Human services in Japan for AI agents: phone calls, reservations, shopping and on-site checks. This page covers its hosted endpoint (https://maru.senpinai.com/mcp).
Is the MARU Japan Hands MCP server safe to use?
MARU Japan Hands scores 64 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 MARU Japan Hands MCP server expose?
MARU Japan Hands exposes 11 tools: list_services, check_availability, request_service, get_request_status, quote_purchase, and 6 more. Their descriptions and schemas cost roughly 1,226 tokens of context every time the server is loaded.
Does the MARU Japan Hands MCP server require authentication?
No. We connected to MARU Japan Hands without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the MARU Japan Hands MCP server still maintained?
MARU Japan Hands 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 MARU Japan Hands MCP server?
VerifyMCP ran 12 checks on MARU Japan Hands, 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 MARU Japan Hands: 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.