mcp-registry/com.mcp-revenue-empire/japan-public-ledgers · v0.1.0
As of 2026-10-18 16:45 UTC, the Mcp Revenue Empire Japan Public Ledgers MCP server is up with a Glimind reliability score of 99/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Tamper-evident daily ledgers of 12 Japanese public-data domains, with cross-ledger entity search.
Claude Code
claude mcp add --transport http mcp-revenue-empire-japan-public-ledgers- https://mcp.mcp-revenue-empire.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"mcp-revenue-empire-japan-public-ledgers-": {
"type": "http",
"url": "https://mcp.mcp-revenue-empire.com/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
172 of 172 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
172 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.
Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →
214 parameter(s) across 90 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
5 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
3 tool(s) have parameters with no type (no type/enum/anyOf/$ref).
Give every parameter a "type" (or "enum"/"anyOf"). Untyped parameters make models guess — strings for numbers, objects for arrays. How to fix →
Loading this server's tool list costs an agent ~19,664 tokens before any work — more than 95% of MCP servers.
Split rarely-used tools into a separate server or a toolset the client can enable, or expose one "search tools" entry point. Many agents load every connected server's tools into every request. How to fix →
Negotiates MCP 2025-03-26. Structured output, tool output schemas and elicitation arrived in 2025-06-18.
Upgrade the MCP SDK and negotiate 2025-06-18 or newer. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 90 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.mcp-revenue-empire%2Fjapan-public-ledgers/fixes
{
"name": "agent_audit_query",
"description": "Query agent actions with filters",
"inputSchema": {
"type": "object",
"properties": {
"to": {
"type": "string",
"format": "date-time"
},
"from": {
"type": "string",
"format": "date-time"
},
"limit": {
"type": "integer",
"default": 100
},
"agentId": {
"type": "string"
},
"riskMin": {
"type": "number"
},
"sessionId": {
"type": "string"
},
"actionType": {
"type": "string"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "agent_audit_record",
"description": "Record an agent action for audit and compliance",
"inputSchema": {
"type": "object",
"required": [
"agentId",
"actionType",
"actionName"
],
"properties": {
"input": {
"type": "string"
},
"output": {
"type": "string"
},
"agentId": {
"type": "string"
},
"metadata": {
"type": "object"
},
"sessionId": {
"type": "string"
},
"actionName": {
"type": "string"
},
"actionType": {
"enum": [
"llm_call",
"tool_use",
"api_call",
"decision",
"error"
],
"type": "string"
}
}
}
}{
"name": "agent_identity_lookup",
"description": "Look up an identity. Returns signatureValid (issuer+integrity only, NOT an authenticity/safety signal) and a disclaimer.",
"inputSchema": {
"type": "object",
"required": [
"identityId"
],
"properties": {
"identityId": {
"type": "string"
}
}
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.mcp-revenue-empire/japan-public-ledgers"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.mcp-revenue-empire/japan-public-ledgers"}) over MCP.
temporal_query ~310 tokensfreshness_subscribe ~304 tokensalerts_create_watch ~249 tokenskyb_report ~219 tokenssanctions_screen_entity ~207 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fcom.mcp-revenue-empire%2Fjapan-public-ledgers?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.mcp-revenue-empire%2Fjapan-public-ledgers?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.mcp-revenue-empire%2Fjapan-public-ledgers.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.mcp-revenue-empire%2Fjapan-public-ledgers.svg :target: https://glimind.com/server/mcp-registry%2Fcom.mcp-revenue-empire%2Fjapan-public-ledgers?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:315cbb5f3933cb65…, first seen 2026-10-17, included at leaf 14353 of 22,769. Version history · verify what your client received.
Compare: most reliable security servers · most reliable other servers · most reliable knowledge servers · most reliable web servers · most reliable communication servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-18 16:45 UTC, the Mcp Revenue Empire Japan Public Ledgers MCP server is up with a Glimind reliability score of 99/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Mcp Revenue Empire Japan Public Ledgers MCP server advertises 172 tools, including agent_audit_query, agent_audit_record, agent_audit_report, agent_captcha_solve, agent_captcha_verify_domain.
Point your MCP client at this streamable-http endpoint: https://mcp.mcp-revenue-empire.com/mcp
Glimind scanned all 172 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.