io.github.kodandy/jp-crypto-tax-rules
REMOTE · JP-CRYPTO-TAX-RULES-62KO7B2UWA-AN.A.RUN.APP · SCANNED AUG 3
Machine-readable Japanese crypto-asset tax rules for AI agents: rules-as-code with citations, x402.
Available components
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 →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- 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 Usability60
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 616 tokens (~154/item across 4 items; 4 tools + 0 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 Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · jp-crypto-tax-rules-62ko7b2uwa-an.a.run.app
claude mcp add --transport http kodandy-jp-crypto-tax-rules https://jp-crypto-tax-rules-62ko7b2uwa-an.a.run.app/mcp
[mcp_servers.kodandy-jp-crypto-tax-rules] url = "https://jp-crypto-tax-rules-62ko7b2uwa-an.a.run.app/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"kodandy-jp-crypto-tax-rules": {
"type": "remote",
"url": "https://jp-crypto-tax-rules-62ko7b2uwa-an.a.run.app/mcp",
"enabled": true
}
}
} openclaw mcp add kodandy-jp-crypto-tax-rules --url https://jp-crypto-tax-rules-62ko7b2uwa-an.a.run.app/mcp --transport streamable-http
mcp_servers:
kodandy-jp-crypto-tax-rules:
url: "https://jp-crypto-tax-rules-62ko7b2uwa-an.a.run.app/mcp" {
"mcpServers": {
"kodandy-jp-crypto-tax-rules": {
"type": "http",
"url": "https://jp-crypto-tax-rules-62ko7b2uwa-an.a.run.app/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 3 Aug 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.
- 1 Aug 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.
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 28 Jul 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.
- 27 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 59
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 3 Aug 2026 · Probed https://jp-crypto-tax-rules-62ko7b2uwa-an.a.run.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.a.run.app | CN=WR2,O=Google Trust Services,C=US | 29 Jun 2026 | 21 Sept 2026 | ECDSA 256 | SHA256-RSA | 256a5f8c86b8938c0929b2764cd03964 |
| SANs: *.a.run.app, run.app, *.africa-south1.run.app, *.asia-east1.run.app, *.asia-east2.run.app, *.asia-northeast1.run.app, *.asia-northeast2.run.app, *.asia-northeast3.run.app, *.asia-south1.run.app, *.asia-south2.run.app, *.asia-southeast1.run.app, *.asia-southeast2.run.app and 91 more | ||||||
| CN=WR2,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7ff005a07c4cded100ad9d66a5107b98 |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
DNSSEC insecure
Validation of jp-crypto-tax-rules-62ko7b2uwa-an.a.run.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| run.app. | absent | 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 |
| Header | Value |
|---|---|
| content-security-policy | default-src 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://jp-crypto-tax-rules-62ko7b2uwa-an.a.run.app/mcp | Verified | 200 | |
| http (plaintext) | http://jp-crypto-tax-rules-62ko7b2uwa-an.a.run.app/mcp | HTTPS enforced | 302 | https://jp-crypto-tax-rules-62ko7b2uwa-an.a.run.app/mcp |
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.
get_rule_pack Curated scenario rule pack (x402 metered) ~197
Scenario-curated bundle of full structured rules (statements, citations, parameters) for one use case: defi_staking | overseas_exchange | corporate_holding | transition_2028. Paid via x402: each call costs 0.05 USDC. This tool returns the HTTP 402 payment challenge (spec-conformant accepts list) for the pack resource. The 402 is real: settle it against /v1/packs/{scenario} with an X-PAYMENT header and the 200 response delivers the full pack body ({status:"settled", settlement, pack}) — payment buys the actual structured rules, not a receipt. Not tax advice. 一般的な税制情報の提供であり、個別の税務判断は税理士にご相談ください。
| Name | Type | Req | Description |
|---|---|---|---|
| scenario | string | yes | Scenario pack to retrieve: defi_staking | overseas_exchange | corporate_holding | transition_2028 |
No output schema declared.
No examples provided.
get_tax_parameters Japanese tax parameters (brackets, rates, thresholds) ~126
FREE — returns structured tax parameters with per-value sources: progressive income tax brackets, resident tax and reconstruction surtax figures, the 2028-reform separate-taxation rate and loss-carryforward years, and the salary-filer filing threshold. Approximate reference values from public sources; not tax advice. 一般的な税制情報の提供であり、個別の税務判断は税理士にご相談ください。
| Name | Type | Req | Description |
|---|---|---|---|
| tax_year | integer | — | Tax year for epoch annotation of pending-reform rules, e.g. 2026 or 2028 |
No output schema declared.
No examples provided.
get_tax_rule Full structured rule record (rule_id lookup) ~97
FREE — returns one full structured rule: statement, exceptions, status, effective dates, machine tags and statutory citations (sources), served verbatim from the versioned rules corpus. Not tax advice. 一般的な税制情報の提供であり、個別の税務判断は税理士にご相談ください。
| Name | Type | Req | Description |
|---|---|---|---|
| rule_id | string | yes | Rule id, e.g. jp.crypto.income.classification.individual |
No output schema declared.
No examples provided.
list_tax_rules List structured Japanese crypto tax rules ~196
FREE — returns structured rules. Catalog of machine-readable Japanese crypto-asset tax rules (rules-as-code): titles, status (current / enacted_pending), effective dates and statutory citations, filterable by category, taxpayer and tax_year. tax_year resolves the current-vs-2028-reform epoch per rule (applies / pending_enforcement). Sources are public only (NTA FAQ, e-Gov statutes, MOF documents); not tax advice. 一般的な税制情報の提供であり、個別の税務判断は税理士にご相談ください。
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | — | Category filter: corporate | cost_basis | filing | income_classification | reform_2028 | taxable_events |
| tax_year | integer | — | Tax year to resolve rule applicability, e.g. 2026 or 2028 |
| taxpayer | string | — | Taxpayer filter: all | corporate | individual |
No output schema declared.
No examples provided.