Servidor MCP de mcp-revenue-empire

Quais servidores MCP são de mcp-revenue-empire, do registro oficial e encontrados perguntando ao próprio domínio, se respondem e o que oferecem. Um programa verificou cada item; nada foi copiado da página do produto.

lido em 2026-10-24

← Voltar para mcp-revenue-empire

De quem é o servidor

Nome no registrocom.mcp-revenue-empire/japan-public-ledgersverificado no registro MCP

O nome no registro fica sob mcp-revenue-empire.com. O registro só libera esse espaço de nomes para quem prova controle do domínio por DNS ou HTTP.

Quando perguntamosverificado em 2026-10-24

Estadorespondeverificado em 2026-10-24
Ferramentas172
O servidor se chamamcp-rs-phase1-mcp
Versão do servidor0.1.0
Versão do protocolo2025-03-26

Em 2026-10-24 o servidor respondeu a initialize e tools/list sem login. Primeira resposta em 147 ms.

Um agente deve conectá-loAinda não está claro

As ferramentas fazem todos os casos de uso verificados: 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.
Verificado em 5 dos 7 dias necessários para julgar a confiabilidade.

Depois de conectar

Para "store and recall short and long term memory for AI agents", a primeira chamada provável é agent_memory_store.
alerts_create_watch, alerts_delete_watch alteram dados sem login: qualquer pessoa com o endereço pode chamá-las.
As definições ocupam cerca de 17712 tokens de contexto: ative só as ferramentas de que a tarefa precisa.
Parâmetros sem tipo ou descrição em 90 de 172 ferramentas: confira os argumentos antes de chamar.

Dito por regras a partir das medições acima. A primeira chamada provável é a escolha de um modelo na lista de ferramentas; leia a descrição antes de confiar nela.

Medido todo diaverificações diárias: 5, a primeira em 2026-10-24

Nota INITE MCPdepois de uma semanaa nota precisa de 7 verificações diárias: 5 até agora
O que um agente consegue fazer com ele3 de 3 casos de uso
Respondeumedindo5 das 7 verificações diárias necessárias para mostrar a porcentagem
Mediana da primeira resposta152 ms
Espaço no contexto do agente≈ 17.712 tokensas definições de todas as ferramentas (172), que o agente carrega a cada turno
Definições das ferramentasC · 74 de 100
Resultados tipados0 de 172 ferramentasdeclaram outputSchema: o resultado chega tipado e é lido de uma vez

Parâmetros sem tipo: em 3 de 172
Parâmetros sem descrição: em 90 de 172
Sem dizer se só lê ou se pode destruir: 172 de 172

O que um agente consegue fazer com ele

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

Cada caso de uso do produto foi perguntado ao Jev junto com a lista de ferramentas deste servidor: um agente consegue fazer isso com essas ferramentas?

Vale conferir

Ferramentas que alteram dados, em um servidor que responde sem login: alerts_create_watch, alerts_delete_watch

Um programa verifica o servidor uma vez por dia: initialize e tools/list, sem modelo. Os tokens são o tamanho das definições, a cerca de quatro caracteres por token. A nota é a média de seis verificações do nome, da descrição, do esquema e das anotações de cada ferramenta; diz se as ferramentas estão bem descritas, não se funcionam. A nota pesa só o que foi medido: se responde (25%), se faz o trabalho do produto (25%), definições (20%), contexto (10%), uso (10%) e a facilidade de conectar (10%). Uma parte não medida fica de fora, e uma instrução oculta limita a nota a 40. O estado dos servidores MCP dos fornecedores: método e números →

Ferramentas que oferece172 ferramentas · lido em 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.

As primeiras 60 de 172, na ordem do servidor.

Como conectar

Adicione o servidor à configuração do seu cliente MCP. Claude Desktop, Cursor e a maioria dos outros clientes leem este formato:

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

Adicionar

Claude Code, no terminal

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

Adicionar ao Cursor Adicionar ao VS Code

claude.ai, ChatGPT e outros clientes: adicione https://mcp.mcp-revenue-empire.com/mcp como conector personalizado nas configurações.

Cada linha é algo que um programa encontrou ao procurar: o registro, a resposta do próprio servidor, uma especificação que se lê. Linha ausente quer dizer que não encontramos, não que não exista.