Japan Public Ledgers MCP
REMOTE · MCP.MCP-REVENUE-EMPIRE.COM · SCANNED SEP 29
Tamper-evident daily ledgers of 12 Japanese public-data domains, with cross-ledger entity search.
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 → Why this is hard to score →
Endpoint Security46
- 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 172 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 enforcement could not be verified: the plaintext port answered with HTTP 404, 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 Usability73
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 12421 tokens (~72/item across 172 items; 172 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage83
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 48% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "agent_memory_delete" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 172 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
How do I install the Japan Public Ledgers MCP server?
Japan Public Ledgers MCP is a hosted endpoint at https://mcp.mcp-revenue-empire.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 · mcp.mcp-revenue-empire.com
claude mcp add --transport http com-mcp-revenue-empire-japan-public-ledgers 'https://mcp.mcp-revenue-empire.com/mcp'
{
"mcpServers": {
"com-mcp-revenue-empire-japan-public-ledgers": {
"url": "https://mcp.mcp-revenue-empire.com/mcp"
}
}
} {
"servers": {
"com-mcp-revenue-empire-japan-public-ledgers": {
"type": "http",
"url": "https://mcp.mcp-revenue-empire.com/mcp"
}
}
} [mcp_servers.com-mcp-revenue-empire-japan-public-ledgers] url = "https://mcp.mcp-revenue-empire.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-mcp-revenue-empire-japan-public-ledgers": {
"type": "remote",
"url": "https://mcp.mcp-revenue-empire.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-mcp-revenue-empire-japan-public-ledgers --url 'https://mcp.mcp-revenue-empire.com/mcp' --transport streamable-http
mcp_servers:
com-mcp-revenue-empire-japan-public-ledgers:
url: "https://mcp.mcp-revenue-empire.com/mcp" {
"McpServers": {
"com-mcp-revenue-empire-japan-public-ledgers": {
"Transport": "http",
"Url": "https://mcp.mcp-revenue-empire.com/mcp"
}
}
} assistant mcp add com-mcp-revenue-empire-japan-public-ledgers -t streamable-http -u 'https://mcp.mcp-revenue-empire.com/mcp'
{
"mcpServers": {
"com-mcp-revenue-empire-japan-public-ledgers": {
"type": "http",
"url": "https://mcp.mcp-revenue-empire.com/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.
- 28 Sept 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
- 25 Sept 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
- 26 Aug 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
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 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
- 6 Aug 26 0
- Schema quality: 10448 → 12421 ▼ functional
- Tool coverage: 41% → 48% ▲ functional
- New tool “cve_lookup_cvss_parse” functional
- New tool “cve_lookup_get_cve” functional
- New tool “cve_lookup_package_advisory” functional
- New tool “cve_lookup_search_cve” functional
- New tool “cve_lookup_severity_summary” functional
- New tool “email_verify_check_mx” functional
- New tool “email_verify_check_spf” functional
- New tool “email_verify_detect_disposable” functional
- New tool “email_verify_role_account” functional
- New tool “email_verify_verify_syntax” functional
- New tool “fx_tax_convert” functional
- New tool “fx_tax_list_rates” functional
- New tool “fx_tax_sales_tax” functional
- New tool “fx_tax_vat_calc” functional
- New tool “fx_tax_vat_validate” functional
- New tool “holiday_calendar_business_days_between” functional
- New tool “holiday_calendar_is_holiday” functional
- New tool “holiday_calendar_list_holidays” functional
- New tool “holiday_calendar_next_business_day” functional
- New tool “holiday_calendar_tz_convert” functional
- New tool “ip_reputation_asn_lookup” functional
- New tool “ip_reputation_classify_ip” functional
- New tool “ip_reputation_detect_datacenter” functional
- New tool “ip_reputation_reverse_dns” functional
- New tool “ip_reputation_risk_score” functional
- 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 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 29 Sept 2026 · Probed https://mcp.mcp-revenue-empire.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp-revenue-empire.com | CN=WE1,O=Google Trust Services,C=US | 14 Aug 2026 | 12 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 3ba2bb8026d9fe480ea33ca79b5956bc |
| SANs: mcp-revenue-empire.com, *.mcp.mcp-revenue-empire.com, mcp.mcp-revenue-empire.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 mcp.mcp-revenue-empire.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| mcp-revenue-empire.com. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.mcp-revenue-empire.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.mcp-revenue-empire.com/mcp | Inconclusive | 404 |
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 →
sanctions_screen_by_country ~65
Summarize sanction programs and entity counts associated with a country (name or ISO-3166 code) across the consolidated lists. Read-only; price 0.0 (free).
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | yes | Country name or ISO-3166 alpha-2 code |
No output schema declared.
No examples provided.
sanctions_screen_check_address ~50
Screen a physical or crypto address string against address entries in the consolidated sanctions lists. Read-only; price 0.0 (free).
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Physical or crypto address to screen |
No output schema declared.
No examples provided.
sanctions_screen_entity ~119
Screen an entity name against public consolidated sanctions lists (OFAC SDN / UN / EU), fetched at request time. Returns scored fuzzy matches with programs and countries. Informational only, not legal advice. Read-only; price 0.0 (free).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max matches to return |
| minScore | number | – | Minimum match score 0-100 (default heuristic threshold) |
| name | string | yes | Entity / person / vessel name to screen |
| types | array | – | Restrict to sanction subject types. |
No output schema declared.
No examples provided.
sanctions_screen_list_programs ~64
List sanction programs known across the consolidated lists, with per-program entity counts. Optionally filter by source. Read-only; price 0.0 (free).
| Name | Type | Req | Description |
|---|---|---|---|
| source | string | – | Optional source id filter (e.g. ofac / un / eu) |
No output schema declared.
No examples provided.
sanctions_screen_list_sources ~40
List the sanctions data sources queried (OFAC SDN / UN / EU) with metadata. Read-only; price 0.0 (free).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
subsidy_watch_get ~35
Get a subsidy program detail plus full event timeline. Returns firstSeenAt and ledgerVerified.
| Name | Type | Req | Description |
|---|---|---|---|
| programId | string | yes | – |
No output schema declared.
No examples provided.
subsidy_watch_recent_changes ~67
Recent appearance / change / close events across all programs since the given ISO8601 timestamp. Each item includes firstSeenAt and ledgerVerified.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
| issuerCode | string | – | – |
| limit | integer | – | – |
| since | string | yes | – |
No output schema declared.
No examples provided.
subsidy_watch_search ~88
Search the current state of subsidy programs. Each hit includes firstSeenAt and ledgerVerified (hash-chain integrity).
| Name | Type | Req | Description |
|---|---|---|---|
| amountMin | integer | – | – |
| category | string | – | – |
| issuerCode | string | – | JIS X 0401/0402 自治体コード |
| limit | integer | – | – |
| query | string | – | – |
| status | string | – | – |
No output schema declared.
No examples provided.
subsidy_watch_timeline ~47
Time-ordered events only for a program (the differentiator: when it appeared, changed, closed). Includes firstSeenAt and ledgerVerified.
| Name | Type | Req | Description |
|---|---|---|---|
| programId | string | yes | – |
No output schema declared.
No examples provided.
subsidy_watch_verify_ledger ~53
Verify the hash-chain integrity of a program (tamper detection). Returns chainValid, brokenAt (if any), checked event count, firstSeenAt and ledgerVerified.
| Name | Type | Req | Description |
|---|---|---|---|
| programId | string | yes | – |
No output schema declared.
No examples provided.
temporal_query ~231
Reconstruct what a ledger item (or items matching a query) officially said AS OF a past date T, by replaying the kept event history. Returns each item's point-in-time state plus an F-037 provenance receipt (observed_at = the state's effective time). existence:false with a first_seen receipt when the item did not yet exist at T; latest state with as_of_clamped:false when T is in the future. Read-only; price 0.0.
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | string | yes | ISO-8601 point in time T. |
| item_id | string | – | Stable item id (single-item reconstruction). |
| jurisdiction | string | – | Jurisdiction code (default 'jp'). |
| ledger | string | yes | Ledger key (e.g. 'sanction', 'license', 'subsidy', 'recall', 'pharma', 'bid', 'grant', 'pubcom', 'ordinance', 'tos', 'realestate', 'landprice'). |
| query | string | – | Title substring to reconstruct every matching item (capped at 25). Use instead of item_id. |
No output schema declared.
No examples provided.
tos_watch_get ~36
Get a ToS snapshot detail plus full event timeline. Returns firstSeenAt and ledgerVerified.
| Name | Type | Req | Description |
|---|---|---|---|
| itemId | string | yes | – |
No output schema declared.
No examples provided.
tos_watch_recent_changes ~59
Recent revised events across all SaaS ToS documents since the given ISO8601 timestamp. Each item includes firstSeenAt and ledgerVerified.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| since | string | yes | – |
| vendor | string | – | – |
No output schema declared.
No examples provided.
tos_watch_search ~117
Search Japanese / English-language SaaS Terms of Service snapshots (Stripe / Anthropic / AWS / Google Cloud / GitHub …). Stage 1 covers 'terms' docs. Each hit includes firstSeenAt and ledgerVerified.
| Name | Type | Req | Description |
|---|---|---|---|
| docType | string | – | – |
| limit | integer | – | – |
| query | string | – | タイトル / 本文先頭抜粋・部分一致 |
| vendor | string | – | 'stripe' / 'anthropic' / 'aws' / 'gcp' / 'github' … |
No output schema declared.
No examples provided.
tos_watch_timeline ~49
Time-ordered events only for a ToS document (the differentiator: when it appeared and each revision since). Includes firstSeenAt and ledgerVerified.
| Name | Type | Req | Description |
|---|---|---|---|
| itemId | string | yes | – |
No output schema declared.
No examples provided.
tos_watch_verify_ledger ~55
Verify the hash-chain integrity of a ToS document (tamper detection). Returns chainValid, brokenAt (if any), checked event count, firstSeenAt and ledgerVerified.
| Name | Type | Req | Description |
|---|---|---|---|
| itemId | string | yes | – |
No output schema declared.
No examples provided.
verify_receipt ~132
Verify a provenance receipt (F-037): recomputes the HMAC signature, checks the intra-receipt chain linkage, and — when the receipt carries an external anchor reference — confirms it against the published F-028 anchor. Returns {valid:true, anchor:"verified"|"pending"|"unverified"} or {valid:false, reason:"signature_mismatch"|"chain_link_broken"|"anchor_mismatch"|"malformed"}. Tamper-evident; price 0.0 (free).
| Name | Type | Req | Description |
|---|---|---|---|
| receipt | object | yes | A receipt JSON object as produced by any provenance-emitting tool. |
No output schema declared.
No examples provided.
weather_risk_air_quality ~84
Air-quality snapshot (PM2.5, PM10, US / European AQI and a coarse category) for a lat/lon via the free Open-Meteo air-quality API. Read-only; price 0.0 (free).
| Name | Type | Req | Description |
|---|---|---|---|
| lat | number | yes | Latitude (-90..90) |
| lon | number | yes | Longitude (-180..180) |
No output schema declared.
No examples provided.
weather_risk_current_weather ~77
Current weather (temperature, apparent temperature, humidity, precipitation, wind, weather code) for a lat/lon via the free Open-Meteo API. Read-only; price 0.0 (free).
| Name | Type | Req | Description |
|---|---|---|---|
| lat | number | yes | Latitude (-90..90) |
| lon | number | yes | Longitude (-180..180) |
No output schema declared.
No examples provided.
weather_risk_forecast ~94
Daily weather forecast (temp max/min, precipitation probability, wind, weather code) for up to N days for a lat/lon via the free Open-Meteo API. Read-only; price 0.0 (free).
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Forecast horizon in days (bounded) |
| lat | number | yes | Latitude (-90..90) |
| lon | number | yes | Longitude (-180..180) |
No output schema declared.
No examples provided.
weather_risk_heat_index ~74
Compute the heat index (feels-like temperature) and risk category from air temperature (Celsius) and relative humidity. Pure compute; price 0.0 (free).
| Name | Type | Req | Description |
|---|---|---|---|
| humidityPct | number | yes | Relative humidity percent (0-100) |
| tempC | number | yes | Air temperature in degrees Celsius |
No output schema declared.
No examples provided.
weather_risk_severe_flags ~79
Severe-weather flags (heavy rain / high wind / extreme heat / frost) derived from the Open-Meteo forecast, each with its threshold and worst value. Read-only; price 0.0 (free).
| Name | Type | Req | Description |
|---|---|---|---|
| lat | number | yes | Latitude (-90..90) |
| lon | number | yes | Longitude (-180..180) |
No output schema declared.
No examples provided.
What is the Japan Public Ledgers MCP server?
Japan Public Ledgers MCP is listed in the public MCP registry as com.mcp-revenue-empire/japan-public-ledgers. Tamper-evident daily ledgers of 12 Japanese public-data domains, with cross-ledger entity search. This page covers its hosted endpoint (https://mcp.mcp-revenue-empire.com/mcp).
Is the Japan Public Ledgers MCP server safe to use?
Japan Public Ledgers MCP scores 68 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 Japan Public Ledgers MCP server expose?
Japan Public Ledgers MCP exposes 172 tools: verify_receipt, agent_memory_store, agent_memory_get, agent_memory_search, agent_memory_delete, and 167 more. Their descriptions and schemas cost roughly 12,421 tokens of context every time the server is loaded.
Does the Japan Public Ledgers MCP server require authentication?
No. We connected to Japan Public Ledgers MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Japan Public Ledgers MCP server still maintained?
Japan Public Ledgers MCP is still listed as active in the MCP registry. We last reached this channel on 29 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.