Prototipo · Versión preliminar: todos los servidores del registro oficial, sincronizados cada 30 minutos. Inicia sesión con Google para escribir reseñas.Prototipo · se actualiza cada 30 min
PopNx MCPServidores MCP para quienes usan IA · en palabras sencillas Iniciar sesión

Japan Corporate Number

de pipeworx-ioversión 0.2.1i★ 0iComputadora o nubeSitio oficial ↗
Nombre en el registroio.github.pipeworx-io/japan-corporate-number

Cómo instalar

Qué hace

japan-corporate-number — Japan's National Tax Agency (国税庁) corporate number register (法人番号公表サイト).…

Texto original del autor

  • Conexión Computadora o nube
  • Cuenta o clave No necesita clave
  • Categoría Contabilidad, finanzas e impuestos

Por qué está en este puesto

Las listas se ordenan por una puntuación de uso (sobre 100) con estas partes

Popularidad0/80Estrellas de GitHub o descargas semanales: la mayor cuenta 60, la menor 20
Actualidad12/12Puntuación completa con una versión o cambio de código en 30 días
Sigue respondiendo8/8El endpoint en la nube respondió en la última revisión
Puntuación de uso20/100

Calidad: Pasó 5/5 revisiones básicas (se muestra, no ordena) · Impulso: Sin datos aún (Solo se usa en la pestaña En auge)

Instalación

Elige la app de IA que usas y copia la configuración.

Que tu IA lo instale con una frase

Instala Japan Corporate Number. Sigue https://mcp.popnx.com/i/pipeworx-io-japan-corporate-number.md, enséñame los comandos y espera mi OK antes de ejecutarlos.

Pégala en una IA que trabaje en tu equipo (como Claude Code o Cursor). Lee nuestros pasos, te muestra los comandos y espera tu OK. Sin clave ni registro. · Ver el texto completo que lee tu IA

Pasó 5/5 revisiones · Lo que preguntas pasa por el servidor del autor (gateway.pipeworx.io) · ✓ Comandos revisados el 14 nov 2026

Primero: ¿qué IA usas?

Elige tu app y los pasos aparecen abajo.

Funciona con Claude · unos 2 min

Sin clave y sin instalar nada · Configúralo una vez en claude.ai o en la app de escritorio y úsalo en el chat · las cuentas gratis pueden añadir 1 · en Team/Enterprise lo añade un Owner

  1. Abre la página Connectors de Claude

    CustomizeConnectors

    CustomizeConnectors1Add2https://…3Add4
  2. Pulsa “Add” → “Custom” → “Web” y completa estos 2 campos

    Copia cada valor al campo con el mismo nombre en Claude y pulsa Continue

    Name · NombreJapan Corporate Number
    Remote MCP server URL · Direcciónhttps://gateway.pipeworx.io/japan-corporate-number/mcp

    Pulsa Continue en la pantalla de inicio de sesión que detectó Claude · en Authentication elige lo que indique el autor (Sign in now, Sign in when needed o No sign in) y pulsa Add

  3. Actívalo en un chat

    +ConnectorsJapan Corporate Number

  4. Pruébalo

    Usa Japan Corporate Number y dime qué puedes hacer por mí; luego muéstrame una cosa

    ✓ Si Claude dice que está usando Japan Corporate Number o muestra una herramienta de Japan Corporate Number en la respuesta, ya está conectado

Nombres de menú comprobados con la ayuda de Anthropic el 11 nov 2026 · tu pantalla puede variar un poco según la versión

Funciona con ChatGPT según tu plan

MCP completo: ChatGPT Business, Enterprise o Edu en la web · Pro: conecta con permisos de lectura/obtención, así que las herramientas que cambian datos pueden no funcionar · Plus: no confirmado en la documentación; si ves una opción para añadir MCP propio en la página de plugins puedes probar · solo web

  1. Abre la página para añadir MCP en ChatGPT web

    Plugins+Add custom MCP server

    ChatGPTPlugins1+2https://…3Create4
  2. Escribe el nombre y la dirección

    Pon un nombre, pega la dirección en Connection, marca el aviso de riesgo y pulsa Create as a plugin

    Name · NombreJapan Corporate Number
    Connection · Direcciónhttps://gateway.pipeworx.io/japan-corporate-number/mcp
  3. Elige Japan Corporate Number en un chat

    Abre un chat nuevo y elige Japan Corporate Number en tus plugins antes de escribir

  4. Pruébalo

    Usa Japan Corporate Number y dime qué puedes hacer por mí; luego muéstrame una cosa

    ✓ Si ChatGPT dice que está usando Japan Corporate Number o muestra una herramienta de Japan Corporate Number en la respuesta, ya está conectado

Nombres de menú comprobados con la ayuda de OpenAI el 11 nov 2026 · tu pantalla puede variar un poco según la versión

Funciona con Claude Code · unos 2 min

Sin clave y sin instalar nada

  1. Abre la Terminal

    Mac: pulsa Command+Espacio y escribe Terminal · Windows: abre PowerShell

  2. Pega este comando y pulsa Enter

    claude mcp add --transport http --scope user japan-corporate-number https://gateway.pipeworx.io/japan-corporate-number/mcp
  3. Escribe /mcp en Claude Code

    Deberías ver Japan Corporate Number en la lista como conectado

  4. Pruébalo

    Usa Japan Corporate Number y dime qué puedes hacer por mí; luego muéstrame una cosa

    ✓ Si Claude Code dice que está usando Japan Corporate Number o muestra una herramienta de Japan Corporate Number en la respuesta, ya está conectado

Nombres de menú comprobados con la ayuda de Anthropic el 11 nov 2026 · tu pantalla puede variar un poco según la versión

Funciona con Cursor · unos 2 min

Sin clave y sin instalar nada

  1. Pulsa este botón para abrir Cursor

    Abrir en Cursor

    Cursor te pedirá confirmar; pulsa Install

  2. Abre el chat de IA de Cursor en modo Agent

  3. Pruébalo

    Usa Japan Corporate Number y dime qué puedes hacer por mí; luego muéstrame una cosa

    ✓ Si Cursor dice que está usando Japan Corporate Number o muestra una herramienta de Japan Corporate Number en la respuesta, ya está conectado

Nombres de menú comprobados con la ayuda de Cursor el 11 nov 2026 · tu pantalla puede variar un poco según la versión

Funciona con VS Code · unos 2 min

Sin clave y sin instalar nada

  1. Pulsa este botón para abrir VS Code

    Abrir en VS Code

    VS Code te pedirá confirmar; pulsa Install

  2. Abre el chat de IA de VS Code en modo Agent

  3. Pruébalo

    Usa Japan Corporate Number y dime qué puedes hacer por mí; luego muéstrame una cosa

    ✓ Si VS Code dice que está usando Japan Corporate Number o muestra una herramienta de Japan Corporate Number en la respuesta, ya está conectado

Nombres de menú comprobados con la ayuda de VS Code el 11 nov 2026 · tu pantalla puede variar un poco según la versión

Otras apps que usan MCP, como Windsurf, Zed o Gemini CLI, añaden servidores de forma distinta. Míralo en la lista de apps

Ver todas las apps que usan MCP →

Dirección para apps que se conectan por la web

Direcciónhttps://gateway.pipeworx.io/japan-corporate-number/mcp

La configuración JSON está en “Para desarrolladores”, abajo

¿Te atascaste? Pregunta a quien usa Japan Corporate Number💬 Conversación →
Para desarrolladores: comandos de Terminal y configuración JSON

Por la web

Claude Code

claude mcp add --transport http --scope user japan-corporate-number https://gateway.pipeworx.io/japan-corporate-number/mcp

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "japan-corporate-number": {
      "url": "https://gateway.pipeworx.io/japan-corporate-number/mcp"
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "japan-corporate-number": {
      "type": "http",
      "url": "https://gateway.pipeworx.io/japan-corporate-number/mcp"
    }
  }
}

Instalado en tu computadora

Claude Code

claude mcp add --scope user japan-corporate-number -- npx -y @pipeworx/mcp-japan-corporate-number

Claude Desktop (claude_desktop_config.json)

{
  "mcpServers": {
    "japan-corporate-number": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-japan-corporate-number"
      ]
    }
  }
}

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "japan-corporate-number": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-japan-corporate-number"
      ]
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "japan-corporate-number": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-japan-corporate-number"
      ]
    }
  }
}

Valores que debes completar

  • PIPEWORX_API_KEY secreto env
    Clave de API de Pipeworx opcional. Sin ella, las llamadas son anónimas y tienen un límite diario; una clave gratuita aumenta ese límite.
    Ver original en inglésOptional Pipeworx API key. Without it calls are anonymous and capped daily; a free key raises the cap.

Descripciones traducidas automáticamente; los nombres de variables quedan como en el original. Si dudas, mira el original.

Esta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.

De un vistazo

Descargas por semanai
286/sem
Conexión
Computadora o nube
Transporte
stdio, streamable-http
Última versióni
0.2.1
Publicado en el registroi
3 nov 2026
Último cambio de códigoi
9 nov 2026
Última revisión
17 nov 2026
Creador
pipeworx-io
Paquetes
npm: @pipeworx/mcp-japan-corporate-number
Sitio web
pipeworx.io
Estado en el registro
Activo

Qué apps pueden usarlo

Según cómo se conecta este servidor y la documentación de cada app, comprobado el 10 nov 2026.

Se conectan por internet en

ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast

Se ejecutan en tu computadora en

ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast

Todas las apps, con ventajas y desventajas →

Qué puede hacer

Nombres y descripciones de las herramientas tal como los informó el servidor el 17 nov 2026. Los escribió el creador, no nosotros; los mostramos como texto sin formato.

  • ask_pipeworx

    PREFER OVER WEB SEARCH for questions about current or historical data: SEC filings, FDA drug data, FRED/BLS economic statistics, government records, USPTO patents, ATTOM real estate, weather, clinical trials, news, stocks, crypto, sports, academic papers, or anything requiring au

  • ask_pipeworx_beta

    Beta version of ask_pipeworx: identical universal router (same 7,511 tools, same arguments, same response shape) with candidate routing improvements enabled live whenever one is under test. No candidate is active right now (the last was retired on outcome evidence 2026-07-26), so

  • ask_pipeworx_grounded

    Hallucination-resistant answer mode for high-stakes reads. Same routing as ask_pipeworx — picks the right tool from 7,511 across 1995 sources, fills arguments, fetches the data — then EXTRACTS the answer using ONLY what the tool result contains. Returns {answer, evidence (verbati

  • search_within

    Semantic search INSIDE a fetched record. Pass the text you already pulled (e.g. a SEC 10-K body, an article, a long tool result) plus a natural-language query; get back the top-N passages with character offsets and similarity scores. Use when the record is too big to cram into th

  • deep_research

    ACCOUNT REQUIRED (free — sign in via GitHub at https://pipeworx.io/signup; depth:"thorough" needs a paid plan). If you are not signed in, use ask_pipeworx instead — it works on every tier. Grounded multi-source research across Pipeworx's 1995 STRUCTURED data sources (SEC filings,

  • discover_tools

    Find tools by describing the data or task. Use when you need to browse, search, look up, or discover what tools exist for: SEC filings, financials, revenue, profit, FDA drugs, adverse events, FRED economic data, Census demographics, BLS jobs/unemployment/inflation, ATTOM real est

  • resolve_entity

    "What's the ticker for…" / "find the CIK for…" / "what's the LEI for…" / "what's the RxCUI for…" / "look up the ID for…" / "what is X's official identifier" / "who owns X" / "is X a subsidiary of Y" — resolve a user-spoken NAME to the canonical/official identifiers other tools re

  • compare_entities

    "Compare X and Y" / "X vs Y" / "X versus Y" / "which is bigger / better / larger / more profitable" / "rank these companies" / "head to head" — side-by-side comparison of 2–5 companies or drugs in ONE parallel call. ALWAYS PREFER over sequential single-pack lookups when comparing

  • subscribe

    Create a proactive monitoring subscription to a live-data event stream. Returns the new subscription id. Requires a Pipeworx OAuth account (anonymous + BYO cannot persist subscriptions). Supported types: "sec_8k" (8-K filings matching ticker + item codes — e.g. items:["5.02"] = o

  • unsubscribe

    Cancel a subscription by id. Ownership is enforced — you can only cancel your own subscriptions. The row is deactivated (not deleted) so its historical events stay available via recent_alerts.

  • list_subscriptions

    List the caller's active subscriptions. Returns id, type, params, created_at, last_fired_at, fire_count for each. Use this to review what you're monitoring before adding more or to find an id to cancel.

  • recent_alerts

    Pull fired events from your subscription feed. Returns the most recent alerts the evaluator has written to your persisted feed — each carries source, citation_uri (pipeworx:// when available), and the raw event payload. Filter by type (e.g. "sec_8k") and/or since (ISO timestamp).

  • entity_profile

    "Tell me about X" / "research Acme" / "brief me on Tesla" / "what does Apple do" / "company profile for Microsoft" / "give me the rundown on NVDA" / "everything you know about $TICKER" — full cross-source profile of a US public company in ONE parallel call. ALWAYS PREFER over cha

  • recent_changes

    "What's new with X" / "latest on Y" / "what happened to Z this week / month / quarter" / "updates on Acme" / "news on Tesla recently" / "what's happening with Apple" — change feed for a company in the last N days/weeks/months in ONE parallel call. Fans out to SEC EDGAR (filings s

  • validate_claim

    "Is it true that…" / "fact check" / "verify the claim that…" / "did X really…" / "was Y actually…" / "confirm or refute" / "true or false" — natural-language claim verification against authoritative sources. Use whenever the agent needs to check whether something a user said is f

  • company_facts

    TYPED, DETERMINISTIC financial facts for a US public company for an EXPLICITLY NAMED reporting period — "Apple revenue for fiscal 2023", "Walmart net income FY2026 Q3", "Microsoft cash at the end of fiscal 2024". PREFER OVER entity_profile / get_company_financials whenever the pe

  • company_register_search

    Search the NATIONAL BUSINESS REGISTERS by company name and get the register's own id back — a Companies House number, a Norwegian organisasjonsnummer, a Finnish business id, a SIREN, a Japanese corporate number, an Estonian registry code, a CRO number, a CNPJ, a US state entity n

  • scan_dependency

    Composite "should I add this npm package to my project" check in ONE call — fans out across deps.dev (license + advisories + version history) and bundlephobia (gzipped/minified bundle size, dependency count, ESM/tree-shake support). Use whenever an agent asks "is X safe / popular

  • bet_research

    Research a Polymarket bet by pulling the relevant Pipeworx data for it in one call. Pass a market slug ("will-kristi-noem-win-the-2028-republican-presidential-nomination"), a polymarket.com URL, or a question text. A dated slug ("...-by-june-30-2026") still resolves after it sett

  • polymarket_arbitrage

    Find arbitrage opportunities on Polymarket via monotonicity violations + partition-sum checks. Call with NO args for a `trending_scan` of the top ~200 markets by weekly volume; pass `event` for the strongest per-event partition_check, or `topic` for a themed cross-event scan. `ev

  • polymarket_edges

    Scan top Polymarket markets and return opportunities where Pipeworx data disagrees with market price. Built for "what should I bet on today" — agents discover opportunities without paging hundreds of markets. FIVE MODEL FAMILIES grouped into three response segments under by_segme

  • polymarket_kalshi_spread

    Cross-venue spread between Kalshi and Polymarket for the same resolving question. The two venues sometimes price the same outcome 2-25pp apart because their participant pools differ — when the bet shapes are equivalent that delta is a real signal, when they aren't the tool says s

  • polymarket_fill_risk

    Realizable-vs-theoretical edge check against live CLOB order-book depth — AND Polymarket's own taker fee, which is never zero and is folded in rather than left for you to add (fleet #3446: r/PredictionsMarkets flagged a "clean" fill that quietly omitted it as optimistic in the di

  • polymarket_edge_tracker

    Edge persistence and decay telemetry built from daily polymarket_edges snapshots. Answers "how long has this edge existed and is it shrinking?" — a fresh wide edge and a 3-week-old wide edge are different trades (the latter is wide for a reason nobody is willing to take). Args: d

  • kalshi_weather_edge

    Prices Kalshi daily high-temperature markets against the NWS forecast for the market's OWN settlement station, and measures whether that forecast actually beats the market. Two modes. LIVE (default): returns the full strike ladder for one city and settlement date with market_prob

  • resolution_audit

    Extract the settlement clause of a single Polymarket (.com or .us) or Kalshi market: who publishes the settling number (source), the clock time + timezone it is taken at (falling back to the market TITLE when the clause itself says "the time range specified in the title" — e.g. P

  • resolution_diff

    Field-by-field diff of TWO markets' settlement clauses (one from each of `a` and `b`; either can be Polymarket .com, Polymarket US, or Kalshi) — runs resolution_audit on both sides and compares source, settle time, precision, comparison_basis, and evidence standard. Returns `equi

  • release_calendar_markets

    JOIN of the official release calendar (econ data, the FOMC, FDA decisions, SEC rules) against LIVE Polymarket/Kalshi markets — which scheduled releases land in the next N hours, and which live markets resolve on them. This is a POSITIONING tool, not a speed product: results are c

  • prediction_calibration

    REALIZED win rate by shown price and minutes elapsed for short-horizon crypto up/down markets, net of taker fee — read from our own settled-outcomes archive, not from live prices. Answers the one question no venue will: "a side shown at 82 with five minutes left, how often did it

  • updown_venue_compare

    The same 15-minute crypto "up or down" window priced on polymarket.com, Polymarket US and Kalshi, side by side, with whether each pair is actually the same contract. Pass asset (btc | eth | sol | xrp | bnb) and window ("current" default, "next", "previous", or the window START as

  • updown_divergence_rate

    How often two venues settled the SAME 15-minute crypto window differently, over every settled window on record. Compares polymarket.com (Chainlink TWAP) with Kalshi and with Polymarket US (both CF Benchmarks BRTI), and Kalshi with Polymarket US as the same-feed control. Per pair:

  • archive_evidence

    What did a web page say on a given date? Finds the archived capture of a URL nearest that date across the Internet Archive Wayback Machine, Common Crawl and Arquivo.pt, reads it, and returns the readable text (HTML stripped) with the capture timestamp, a link to the archived copy

  • archive_compare

    What changed on a web page between two dates? Resolves the archived capture nearest each date (Internet Archive Wayback Machine, Common Crawl, Arquivo.pt), extracts the readable text of both, and returns a text-level diff: the segments removed and added, a similarity score, and b

  • research_row

    Claygent-style per-row research: answer ONE question about ONE company and return a JSON object matching your output_schema, with every field wrapped in its own evidence — {value, evidence_url, quote, status}. status is NEVER self-reported by the model: "found" means this code in

  • classify_row

    Cheap categorization: given a company and a list of candidate labels, decide which labels apply — the most common GTM/AI usage shape (tagging a list by industry, ICP fit, etc.), one small model call. Same evidence contract as research_row: each label comes back {label, applies, e

  • pipeworx_trending

    What other AI agents are calling on Pipeworx right now. Returns the top tools, top packs, and total call volume over a recent window (24h, 7d, or 30d). Useful for: (1) discovering what data sources are hot for current events, (2) confirming a popular tool is the canonical choice

  • suggest_questions

    What can I ask Pipeworx? / what is Pipeworx good for? / what can you do? / give me ideas / show me examples / getting started / what data do you have? — the onboarding entry point for an agent that just connected and wants to know what is worth asking. Returns category-bucketed e

  • generate_llms_txt

    Generate a production-ready llms.txt file for any URL so AI crawlers (ChatGPT, Claude, Perplexity) can index the site cleanly. Fetches the page, extracts title/description/key links, and emits the standard llms.txt markdown format. Output is a single text blob ready to drop at si

  • ai_visibility_check

    Probe one or more LLMs for what they know about a business / brand / product / topic and score visibility (0-100) per model. Default model is Workers AI Llama-3.3-70b (free); pass `_apiKey` to also probe Anthropic (BYO key — you pay Anthropic directly for those calls). Returns pe

  • scan_competitor_ai_presence

    Compare AI visibility across multiple entities side-by-side. Probes each entity (your brand + N competitors) with ai_visibility_check, ranks by score, surfaces which is most/least recognized. Useful for competitive AI-marketing audits: "does Claude know about us as well as our co

  • pipeworx_feedback

    Tell the Pipeworx team something is broken, missing, or needs to exist. Use when a tool returns wrong/stale data (bug), when a tool you wish existed isn't in the catalog (feature/data_gap), or when something worked surprisingly well (praise). ONLY for tools served by this Pipewor

  • remember

    Save data the agent will need to reuse later — across this conversation or across sessions. Use when you discover something worth carrying forward (a resolved ticker, a target address, a user preference, a research subject) so you don't have to look it up again. Stored as a key-v

  • recall

    Retrieve a value previously saved via remember, or list all saved keys (omit the key argument). Use to look up context the agent stored earlier — the user's target ticker, an address, prior research notes — without re-deriving it from scratch. Scoped to your identifier (anonymous

  • forget

    Delete a previously stored memory by key. Use when context is stale, the task is done, or you want to clear sensitive data the agent saved earlier. Pair with remember and recall.

  • jp_corporate_number

    Look up one Japanese corporation/organization by its 13-digit 法人番号 (corporate number) in Japan's National Tax Agency register: legal name, katakana reading and English name when NTA holds one, address, corporate-kind (stock company, LLC, government body, etc.) and status (active,

  • jp_company_search

    Search Japan's National Tax Agency corporate-number register by name — Japanese (kanji/katakana, substring match; 株式会社/(株)/㈱/有限会社/合同会社 accepted as prefix or suffix), the official English name/katakana reading NTA holds for some entities, or the English name GLEIF holds for entiti

Revisiones básicasi

Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 20 nov 2026

  • ✓ Superada

    El creador coincide con el repo

    El nombre en el registro se verificó con la cuenta de GitHub pipeworx-io, dueña del repo

  • ✓ Superada

    Sigue en mantenimiento

    Último cambio de código: hace 11 días

  • ✓ Superada

    Tiene licencia

    Usa MIT

  • ✓ Superada

    El endpoint responde

    Respondió en 126 ms (HTTP 200)

  • – No aplica

    Inicio de sesión con OAuth

    No hace falta iniciar sesión

  • ✓ Superada

    Sin instrucciones ocultas en las descripciones de herramientas

    Leímos 46 descripciones de herramientas y no encontramos instrucciones ocultas para la IA

Vulnerabilidades publicadas (OSV.dev)

Sin entradas en OSV.dev para @pipeworx/mcp-japan-corporate-number@0.2.1

Solo revisa esta versión del paquete, no todas sus dependencias · revisado 15 nov 2026

Qué revisamos → · JSON

Creadores: pedir otra revisión o avisar de un dato erróneo
Para autores: añade una insignia a tu README

Si lo creaste tú, pega este código en tu README. La insignia enlaza a esta página.

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/pipeworx-io-japan-corporate-number.svg)](https://mcp.popnx.com/en/servers/pipeworx-io-japan-corporate-number)

Conversación

Pregunta, comparte un consejo o avisa de que no funciona. Ordenado por lo que la gente marcó como útil.

Aún no hay publicaciones. Sé la primera persona en preguntar o compartir.

Lo publicado aquí lo escriben usuarios, no el equipo de PopNx.

Inicia sesión para publicar

Reseñas de usuarios

Aún no hay reseñas

Inicia sesión para escribir una reseña

Comparado con otros en Contabilidad, finanzas e impuestosi

  • Más estrellas que el 0% de los otros 3462 servidores de esta categoría
  • Publicado en el registro más recientemente que el 64% de los otros 3462 servidores de esta categoría
  • Revisiones básicas iguales o mejores que el 99% de los otros 3462 servidores de esta categoría

Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.

Preguntas frecuentes

¿Es seguro Japan Corporate Number?

Superó 5 de 5 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.

¿Qué claves o códigos necesita?

El registro no indica ninguna clave obligatoria, aunque algunos servidores te piden iniciar sesión la primera vez que los usas.

¿Se ejecuta en mi computadora o en la nube?

Funciona de las dos formas: instálalo en tu computadora o conéctate a la versión en la nube.

¿Sigue en mantenimiento?

El repo de GitHub cambió por última vez hace 11 días, y la última versión (0.2.1) llegó al registro hace 17 días.

¿Qué apps pueden usarlo?

Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. Se conecta por URL, así que también sirve en apps que aceptan MCP remoto, como ChatGPT en la web (MCP completo en Business y superiores; Pro solo lectura).

¿Qué puedo usar en su lugar?

En la misma categoría: SolidInvoice, Signal8, Journalit, Beancount.io, Tapetide - Indian Stock Market MCP

Alternativas parecidas

Misma categoría, otros creadores, comandos ya revisados. Primero los oficiales, luego por estrellas.

Cómo leer una tarjeta:↓ Descargas por semanai★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi

SolidInvoice

Create and send invoices and quotes, manage clients, and track payments in SolidInvoice.

de SolidInvoiceEn crecimiento★ 990Actualizado hace 11 días

Se ejecuta en la nube✓ del servicio · solidinvoice.co

Signal8

SEC filings, dilution, insider & institutional ownership, and political-trade data for AI agents.

de signal8aiEn crecimiento↓ 431/sem★ 425Actualizado hace 11 días

Computadora o nube✓ del servicio · signal8.ai

Journalit

Trading journal in Obsidian. Ask Claude or ChatGPT about your trades; edits are previewed first.

de CursivezEn crecimiento★ 261Actualizado hace 12 días

Se ejecuta en la nube✓ del servicio · journalit.co

Beancount.io

Query, edit, and reconcile a hosted Beancount ledger: BQL, reports, files, and bank imports.

de bex-coEn crecimiento★ 707 Estrellas de todo el repositorioActualizado el mes pasado

Se ejecuta en la nube✓ del servicio · beancount.io
Comparado con otros parecidos
Este
Japan Corporate Number
SolidInvoiceSignal8JournalitBeancount.ioTapetide - Indian Stock Market MCP
Dónde se ejecutaEn la nube o instalado en tu equipoFunciona en la nube, sin instalar nadaEn la nube o instalado en tu equipoFunciona en la nube, sin instalar nadaFunciona en la nube, sin instalar nadaEn la nube o instalado en tu equipo
Necesita claveNoNoSíNoNoSí
Se añade con + en ClaudeNoNoNoNoNoNo
Revisiones básicas5/54/65/54/44/45/5
LicenciaMITMITMITNOASSERTIONMITMIT
PrecioSin coste en el registroSin coste en el registroSin coste en el registroSin coste en el registroSin coste en el registroSin coste en el registro

README del creador

Abrir el README

Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.

@pipeworx/japan-corporate-number

Japan's National Tax Agency (国税庁) corporate-number register (法人番号公表サイト) — the complete spine of every 13-digit 法人番号 issued since 2015-10-05: legal name, katakana reading and English name when NTA holds one, address, corporate kind (stock company, LLC, government body, NPO, etc.) and status (active, or closed/merged with the narrative NTA published). 5,837,980 entities as of the 2026-09-30 cut.

Part of Pipeworx — an MCP gateway connecting AI agents to 1865+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.

gBizINFO (mcps/gbizinfo, METI) is a different source hanging richer government records — procurement, subsidies, patents, financials — off the same corporate number, with partial coverage. This pack is the complete spine (every registered number, from NTA directly); use gbizinfo for the government-record detail once you have a number.

Tools

  • jp_corporate_number(number) — look up one entity by its 13-digit 法人番号. Validates the check digit before looking up (see "Check digit" below) and returns found: false with a reason for a malformed number, a check-digit failure, or a correctly-formed number simply not in the register — never an empty object.
  • jp_company_search(name, prefecture?, limit?) — search by Japanese name (substring; 株式会社, (株), ㈱, 有限会社, 合同会社 etc. accepted as prefix or suffix), the English name/katakana reading NTA published for some entities, or the English name GLEIF holds for entities with an LEI. prefecture accepts a Japanese name, an English name, or a 2-digit code. Results carry lei and matched_via (register_name or gleif_lei_bridge); the response carries name_bridge.status.

Auth

Keyless. The gateway supplies the data directly — no caller-facing key, and no vendor key of any kind (the register is published as a monthly file, not a live API). The tools work only through the hosted gateway: a standalone build has no data to read and returns a loud error (StoreUnavailableError) naming that, never an empty result.

Data source & reuse terms

  • Japan National Tax Agency (国税庁), Corporate Number Publication Site (法人番号公表サイト) — the whole-country corporate-number register, published monthly. Pipeworx loads each monthly edition; data_as_of on every response is when the loaded edition was taken. The fetch mechanics (and the verified column mapping) live only in scripts/japan-corporate-number/README.md, which does not publish — CLAUDE.md step 9b (a4c024647): name the source, never the source file/path/form fields.
  • Terms of use (Japan's Public Data License v1.0, quoted from NTA's terms-of-use page): attribution is required ("本コンテンツを利用する際は出典を記載してください" — when using this content, state the source); edits/derivative processing must be disclosed separately from the attribution; and edited/processed data must never be presented as though the government itself produced it ("編集・加工等した情報を、あたかも国(又は府省等)が作成したかのような 態様で公表・利用することは禁止します"). Otherwise permissive — commercial reuse and redistribution are not restricted. This README and every tool response carry the source and data_as_of; the data is NTA's, reformatted by Pipeworx, never presented as government-produced.
Kind codes (法人種別)

The complete set observed: 101 national government organization, 201 local government, 301 Kabushiki Kaisha (stock company), 302 Godo Kaisha (LLC-equivalent), 303 Gomei Kaisha, 304 Goshi Kaisha, 305 other registered corporation (e.g. incorporated association/foundation), 399 other, 499 foreign company etc. Labels are best-effort English glosses of NTA's standard code table; the raw code is always returned alongside the label.

Status — a real correctness trap (and a second one inside it)

A corporation closed by merger (process_type 71/72, ~31,000 entities) carries closure_event_text (a Japanese sentence naming the other party) but `closure_date` and `closure_cause_code` are NULL for these rows — that pair is populated by a *different* closure mechanism entirely (mostly process_type 21, ~784K rows), which mostly has no closure_event_text. Checking closure_date alone misses every merged-away entity.

The trap inside the trap: closure_event_text describes a merger from either side, and only the wording says which. "...を合併" (absorbed [other]) names the SURVIVOR — this entity continues (e.g. Toyota Motor Corporation absorbing a subsidiary). "...に合併し解散" (merged INTO [other] and DISSOLVED) names the entity that disappeared. Treating any closure_event_text as closed is wrong — found live reporting an active, operating company as closed. status is closed_or_merged when closure_date is set, OR closure_event_text is set AND literally contains 解散 ("dissolved").

Check digit

A 法人番号's first digit is a check digit over the other 12 (most significant first), weighted 2,1,2,1,... (the most significant base digit carries weight 2), summed, mod 9, check = 9 - (sum mod 9). Verified against real numbers from the register (1000012160153, 1000013050386, 1000013050394 all pass; the naive "textbook" weighting 1,2,1,2,... fails all three). jp_corporate_number validates this before looking up, so a malformed or impossible number gets a specific bad_format / bad_check_digit reason rather than a bare "not found".

"Japanese and romanised matching" — what this is and is not

GLEIF name bridge (fleet #3020). NTA published an English name for only 15,352 of 5.8M entities — not for Sharp, Sony Group or Toyota Motor. Every search therefore also makes one live call to GLEIF (Global Legal Entity Identifier Foundation) LEI records, filtered to Japan. For a Japanese entity GLEIF records its 会社法人等番号 under registration authority RA000412; the 法人番号 is that 12-digit number with NTA's check digit prepended, so each GLEIF hit resolves to a register row by number. Bridged rows rank ahead of register-only rows at the same name tier, which is what puts Sharp Corporation first among the 100+ シャープ-named companies. The bridge is a live proxy call (nothing is copied) and fails open: if GLEIF is down the search answers from the register alone and says name_bridge.status: "unavailable".

jp_company_search matches a single FTS5 trigram index over the Japanese core name (corporate-suffix stripped, e.g. "株式会社" / "K.K." both fold away), the English name, and the katakana reading — whichever of these NTA actually published for that entity. It is not a transliterator: a company with no registered English name/kana will not be found by a romanised query that NTA never recorded — except through the GLEIF bridge below. prefecture is resolved against a static 47-prefecture table (src/prefectures.ts) so it works by Japanese name, English name, or code regardless of whether the matched *company* registered an English address — filtering on the register's own per-company prefecture_en column directly would silently miss almost every entity in a prefecture whose companies have no English name at all.

FTS5's trigram tokenizer windows by character, not byte: a query under 3 characters produces no trigrams and matches nothing via MATCH even when it is a real substring (verified: a 2-character Japanese query returns 0 rows via FTS, 5+ via LIKE, for an identical string). jp_company_search falls back to a plain substring scan for any query under 3 characters.

Refresh and dupe-check notes: see scripts/japan-corporate-number/README.md (operator-only, does not publish) and gbizinfo above.

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{

"mcpServers": { "japan-corporate-number": { "url": "https://gateway.pipeworx.io/japan-corporate-number/mcp" } } }

What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/japan-corporate-number/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — ask_pipeworx, discover_tools, search_within, remember/recall and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for a given day.

This is deliberate, not multiplexing by accident. The meta-tools are what let a scoped connection answer a question this pack does not cover — via ask_pipeworx, which routes across the whole catalog — without you adding a second MCP server. There is currently no way to mount a pack endpoint without them; if the extra schemas cost you more context than the routing is worth, connect to the full gateway once rather than to several pack endpoints.

Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:

{

"mcpServers": { "pipeworx": { "url": "https://gateway.pipeworx.io/mcp" } } }

Both URLs reach the same gateway and the same 1865+ data sources. The only difference is which pack's tools are listed directly; ask_pipeworx reaches all of them from either one.

No MCP client? Call it over HTTP

curl -X POST https://gateway.pipeworx.io/v1/tools/jp_corporate_number \

-H 'Content-Type: application/json' \ -d '{"number":"1000012160153"}'

No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/jp_corporate_number. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.

Run it from npm

@pipeworx/mcp-japan-corporate-number is a local stdio bridge to the Pipeworx gateway: your MCP client starts it with npx, and it forwards every call to the same https://gateway.pipeworx.io/japan-corporate-number/mcp endpoint shown above. It needs network access; there is no offline mode.

{

"mcpServers": { "japan-corporate-number": { "command": "npx", "args": ["-y", "@pipeworx/mcp-japan-corporate-number"] } } }

Without a key it calls anonymously, capped at 50 calls a day. A free account raises that to 200 a day: get a key at https://pipeworx.io/signup and add "env": { "PIPEWORX_API_KEY": " " } to the server entry. The key is sent as a Bearer token, the same way a hosted connection sends it, so calls are metered and billed exactly as they are there.

It lists only this pack's tools by default. Set PIPEWORX_META_TOOLS=1 to also list ask_pipeworx and the other gateway-wide tools.

Behind an HTTPS proxy: Node's built-in fetch does not read HTTPS_PROXY by default. Newer Node releases honour it when NODE_USE_ENV_PROXY=1 is set; check your Node version's documentation.

Using with ask_pipeworx

Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:

ask_pipeworx({ question: "your question about Japan Corporate Number data" })

The gateway picks the right tool and fills the arguments automatically.

More

License

MIT