mcp-revenue-empire MCP server

Which MCP servers are mcp-revenue-empire's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-24

← Back to mcp-revenue-empire

Whose server it is

Registry namecom.mcp-revenue-empire/japan-public-ledgersverified in the MCP registry

The registry name sits under mcp-revenue-empire.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-24

Stateanswerschecked 2026-10-24
Tools172
Server calls itselfmcp-rs-phase1-mcp
Server version0.1.0
Protocol version2025-03-26

On 2026-10-24 the server answered initialize and tools/list without a sign-in. First answer in 147 ms.

Should an agent connect itNot proven either way yet

Its tools do every use case we checked: monitor Japanese government notices for deadline and status changes; check Japanese licence and sanction records for vendor screening; store and recall short and long term memory for AI agents.
Checked on 5 of the 7 days it takes to judge reliability.

Once connected

For "store and recall short and long term memory for AI agents", the likely first call is agent_memory_store.
alerts_create_watch, alerts_delete_watch change data without a sign-in: anyone with the address can call them.
Its definitions take about 17712 tokens of context: enable only the tools a task needs.
Parameters are untyped or undescribed in 90 of 172 tools: check arguments before calling.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 5, the first on 2026-10-24

INITE MCP scoreafter a weeka score needs 7 daily checks: 5 so far
What an agent can do with it3 of 3 use cases
Answeredmeasuring5 of the 7 daily checks it takes to print a share
Median first answer152 ms
Space in an agent's context≈ 17,712 tokensthe definitions of all its tools (172), which an agent carries on every turn
Tool definitionsC · 74 of 100
Typed results0 of 172 toolsdeclared outputSchema: results come typed, read once

Parameters without a type: in 3 of 172
Parameters without a description: in 90 of 172
Not saying whether it only reads or can destroy: 172 of 172

What an agent can do with it

can do · monitor Japanese government notices for deadline and status changes
can do · check Japanese licence and sanction records for vendor screening
can do · store and recall short and long term memory for AI agents

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

Tools that change data, on a server that answers without a sign-in: alerts_create_watch, alerts_delete_watch

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers172 tools · read 2026-10-24

verify_receipt
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…
agent_memory_store
Store a memory for an AI agent (key-value, with TTL and metadata)
agent_memory_get
Retrieve a stored memory by key
agent_memory_search
Search memories by prefix, tags, or type
agent_memory_delete
Delete a memory or all memories in a namespace
agent_audit_record
Record an agent action for audit and compliance
agent_audit_query
Query agent actions with filters
agent_audit_report
Generate audit report (json/markdown/soc2 format)
agent_tempmail_create
Create a temporary email address (auto-expires)
agent_tempmail_list
List received messages in a mailbox
agent_tempmail_get
Get full message content with extracted verification links/codes
agent_tempmail_wait
Wait for an incoming message (long polling, max 60s)
agent_captcha_verify_domain
Verify ownership of a domain before using CAPTCHA solving
agent_captcha_solve
Solve a CAPTCHA for a domain you own or have explicit permission to access
agent_proxy_fetch
Fetch a URL via a rotating proxy (region/type selectable). robots.txt enforced.
agent_proxy_session
Create a sticky proxy session (same IP for multiple requests)
agent_trust_score
Get trust score for a wallet, agent card URL, or domain
agent_trust_feedback
Submit feedback about an agent/wallet (positive or negative)
agent_trust_batch
Get trust scores for multiple subjects in one call (max 100)
agent_webhook_create
Create a webhook endpoint that relays requests to your agent
agent_webhook_poll
Poll for new webhook requests (long polling, max 60s)
agent_webhook_replay
Replay a stored webhook request
agent_webhook_list_requests
List requests received by a webhook endpoint
agent_identity_register
Register an agent and get a unique identity ID + issuer-signed badge. agent_name/metadata are self-reported and unverified.
agent_identity_badge
Get the issuer-signed badge and signed fields for an identity
agent_identity_lookup
Look up an identity. Returns signatureValid (issuer+integrity only, NOT an authenticity/safety signal) and a disclaimer.
agent_identity_record
Append a hash-chained activity record (owner only). Optional provenance (repo/version/config) is self-reported.
agent_identity_activities
List activity records for an identity, newest first (owner only)
subsidy_watch_search
Search the current state of subsidy programs. Each hit includes firstSeenAt and ledgerVerified (hash-chain integrity).
subsidy_watch_get
Get a subsidy program detail plus full event timeline. Returns firstSeenAt and ledgerVerified.
subsidy_watch_timeline
Time-ordered events only for a program (the differentiator: when it appeared, changed, closed). Includes firstSeenAt and ledgerVerified.
subsidy_watch_recent_changes
Recent appearance / change / close events across all programs since the given ISO8601 timestamp. Each item includes firstSeenAt and ledgerVerified.
subsidy_watch_verify_ledger
Verify the hash-chain integrity of a program (tamper detection). Returns chainValid, brokenAt (if any), checked event count, firstSeenAt and ledgerVerified.
pubcom_watch_search
Search e-Gov public-comment notices. Each hit includes firstSeenAt and ledgerVerified (hash-chain integrity).
pubcom_watch_get
Get a public-comment notice detail plus full event timeline. Returns firstSeenAt and ledgerVerified.
pubcom_watch_timeline
Time-ordered events only for a notice (the differentiator: when it opened, deadline moved, closed, or result was published). Includes firstSeenAt and ledgerVerified.
pubcom_watch_recent_changes
Recent appearance / deadline-move / close / result-published events across all notices since the given ISO8601 timestamp. Each item includes firstSeenAt and ledgerVerified.
pubcom_watch_verify_ledger
Verify the hash-chain integrity of a notice (tamper detection). Returns chainValid, brokenAt (if any), checked event count, firstSeenAt and ledgerVerified.
grant_watch_search
Search Japanese research-grant calls-for-proposals. Each hit includes firstSeenAt and ledgerVerified (hash-chain integrity).
grant_watch_get
Get a grant call detail plus full event timeline. Returns firstSeenAt and ledgerVerified.
grant_watch_timeline
Time-ordered events only for a grant call (the differentiator: when it opened, deadline moved, closed, or closed early). Includes firstSeenAt and ledgerVerified.
grant_watch_recent_changes
Recent appearance / deadline-move / close / close-early events across all grant calls since the given ISO8601 timestamp. Each item includes firstSeenAt and ledgerVerified.
grant_watch_verify_ledger
Verify the hash-chain integrity of a grant call (tamper detection). Returns chainValid, brokenAt (if any), checked event count, firstSeenAt and ledgerVerified.
bid_watch_search
Search Japanese public-procurement bid notices (kkj.go.jp). Each hit includes firstSeenAt and ledgerVerified.
bid_watch_get
Get a bid notice detail plus full event timeline. Returns firstSeenAt and ledgerVerified.
bid_watch_timeline
Time-ordered events only for a bid notice (the differentiator: when it appeared, deadline moved, closed, was cancelled or awarded). Includes firstSeenAt and ledgerVerified.
bid_watch_recent_changes
Recent appearance / deadline-move / close / cancel / award events across all bid notices since the given ISO8601 timestamp. Each item includes firstSeenAt and ledgerVerified.
bid_watch_verify_ledger
Verify the hash-chain integrity of a bid notice (tamper detection). Returns chainValid, brokenAt (if any), checked event count, firstSeenAt and ledgerVerified.
sanction_watch_search
Search Japanese administrative sanctions (FSA jirei archive). Each hit includes firstSeenAt and ledgerVerified.
sanction_watch_get
Get a sanction detail plus full event timeline. Returns firstSeenAt and ledgerVerified.
sanction_watch_timeline
Time-ordered events only for a sanction (the differentiator: when it appeared and when it was lifted). Includes firstSeenAt and ledgerVerified.
sanction_watch_recent_changes
Recent appearance / lift events across all sanctions since the given ISO8601 timestamp. Each item includes firstSeenAt and ledgerVerified.
sanction_watch_verify_ledger
Verify the hash-chain integrity of a sanction record (tamper detection). Returns chainValid, brokenAt (if any), checked event count, firstSeenAt and ledgerVerified.
license_watch_search
Search Japanese license / registration ledgers (FSA menkyo: 金融商品取引業者, 預金取扱金融機関 …). Each hit includes firstSeenAt and ledgerVerified.
license_watch_get
Get a license registration detail plus full event timeline. Returns firstSeenAt and ledgerVerified.
license_watch_timeline
Time-ordered events only for a license registration (the differentiator: when it appeared, when it was revoked / expired / suspended). Includes firstSeenAt and ledgerVerified.
license_watch_recent_changes
Recent appearance / revoked / suspended events across all license ledgers since the given ISO8601 timestamp. Each item includes firstSeenAt and ledgerVerified.
license_watch_verify_ledger
Verify the hash-chain integrity of a license registration (tamper detection). Returns chainValid, brokenAt (if any), checked event count, firstSeenAt and ledgerVerified.
recall_watch_search
Search Japanese product / food recall notices (consumer-affairs-agency aggregator). Each hit includes firstSeenAt and ledgerVerified.
recall_watch_get
Get a recall detail plus full event timeline. Returns firstSeenAt and ledgerVerified.

The first 60 of 172, as the server listed them.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "japan-public-ledgers": {
      "type": "http",
      "url": "https://mcp.mcp-revenue-empire.com/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http mcp-revenue-empire https://mcp.mcp-revenue-empire.com/mcp

Add to Cursor Add to VS Code

claude.ai, ChatGPT and other clients: add https://mcp.mcp-revenue-empire.com/mcp as a custom connector in the settings.

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.