Saltar al contenido
Logo de mcp-revenue-empire

Servidor MCP de mcp-revenue-empire

Qué servidores MCP son de mcp-revenue-empire, del registro oficial y encontrados preguntando a su propio dominio, si responden y qué ofrecen. Un programa comprobó cada dato; nada está copiado de la página del producto.

leído el 2026-10-24

← Volver a mcp-revenue-empire

De quién es el servidor
  • Nombre en el registrocom.mcp-revenue-empire/japan-public-ledgersverificado en el registro MCP

El nombre en el registro está bajo mcp-revenue-empire.com. El registro solo permite usar ese espacio de nombres a quien demuestra control del dominio por DNS o HTTP.

Cuando le preguntamoscomprobado el 2026-10-24
  • Estadorespondecomprobado el 2026-10-24
  • Herramientas172
  • El servidor se llamamcp-rs-phase1-mcp
  • Versión del servidor0.1.0
  • Versión del protocolo2025-03-26

El 2026-10-24 el servidor respondió a initialize y tools/list sin iniciar sesión. Primera respuesta en 147 ms.

¿Debe un agente conectarlo?Aún no está claro
  • Sus herramientas hacen todos los casos de uso comprobados: 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.
  • Comprobado 5 de los 7 días necesarios para juzgar su fiabilidad.

Una vez conectado

  • Para "store and recall short and long term memory for AI agents", la primera llamada probable es agent_memory_store.
  • alerts_create_watch, alerts_delete_watch cambian datos sin iniciar sesión: cualquiera con la dirección puede llamarlas.
  • Sus definiciones ocupan unos 17712 tokens de contexto: activa solo las herramientas que necesita la tarea.
  • Parámetros sin tipo o sin descripción en 90 de 172 herramientas: revisa los argumentos antes de llamar.

Lo dicen reglas a partir de las mediciones de arriba. La primera llamada probable la elige un modelo de la lista de herramientas; lee su descripción antes de fiarte.

Medido cada díacomprobaciones diarias: 5, la primera el 2026-10-24
  • Nota INITE MCPtras una semanala nota necesita 7 comprobaciones diarias: 5 hasta ahora
  • Qué puede hacer un agente con él3 de 3 casos de uso
  • Respondiómidiendo5 de las 7 comprobaciones diarias necesarias para mostrar el porcentaje
  • Mediana de la primera respuesta152 ms
  • Espacio en el contexto del agente≈ 17.712 tokenslas definiciones de todas sus herramientas (172), que el agente lleva en cada turno
  • Definiciones de herramientasC · 74 de 100
  • Resultados tipados0 de 172 herramientasdeclaran outputSchema: el resultado llega tipado y se lee de una vez
  • Parámetros sin tipo: en 3 de 172
  • Parámetros sin descripción: en 90 de 172
  • Sin indicar si solo lee o puede destruir: 172 de 172

Qué puede hacer un agente con él

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

Cada caso de uso del producto se le preguntó a Jev junto con la lista de herramientas de este servidor: ¿puede un agente hacerlo con estas herramientas?

Conviene revisar

  • Herramientas que cambian datos, en un servidor que responde sin iniciar sesión: alerts_create_watch, alerts_delete_watch

Un programa comprueba el servidor una vez al día: initialize y tools/list, sin modelo. Los tokens son la longitud de las definiciones, a unos cuatro caracteres por token. La nota promedia seis comprobaciones del nombre, la descripción, el esquema y las anotaciones de cada herramienta; dice lo bien descritas que están, no si funcionan. La nota pondera solo lo medido: si responde (25%), si hace el trabajo del producto (25%), definiciones (20%), contexto (10%), uso (10%) y lo fácil que es conectarse (10%). Lo que no se midió queda fuera, y una instrucción oculta limita la nota a 40. El estado de los servidores MCP de los proveedores: método y números →

Herramientas que ofrece172 herramientas · leído el 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.

Las primeras 60 de 172, en el orden del servidor.

Cómo conectar

Añade el servidor a la configuración de tu cliente MCP. Claude Desktop, Cursor y la mayoría de los demás clientes leen este formato:

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

Añadirlo

Claude Code, en una terminal

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

Añadir a CursorAñadir a VS Code

claude.ai, ChatGPT y otros clientes: añade https://mcp.mcp-revenue-empire.com/mcp como conector personalizado en los ajustes.

Cada línea es algo que un programa encontró al buscar: la entrada del registro, la respuesta del propio servidor, una especificación que se puede leer. Si falta una línea, es que no la encontramos, no que no exista.