mcpbeat

INPI MCP Server

io.github.mcp-dir/inpi-mcp
answering

INPI is answering right now. Last checked 7 min ago. It exposes 11 tools. Last commit 25 Jun 2026.

Brazilian INPI trademark & patent lookup by name, process number or holder (CPF/CNPJ).

Uptime history 44 hours of history · worst hour 50%
44 hours agonow
96.7%
Uptime 24h
88 of 91 checks
11
Tools
read from the server
531 ms
Response time
average over 24h
0
Stars
last commit 25 Jun 2026

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 7 min ago.

run in your terminal
claude mcp add inpi-mcp --transport http https://api.mcp.ai/p_inpi
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "inpi-mcp": {
      "url": "https://api.mcp.ai/p_inpi"
    }
  }
}
~/.codex/config.toml
[mcp_servers.inpi-mcp]
url = "https://api.mcp.ai/p_inpi"
.cursor/mcp.json
{
  "mcpServers": {
    "inpi-mcp": {
      "url": "https://api.mcp.ai/p_inpi"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "inpi-mcp": {
      "url": "https://api.mcp.ai/p_inpi"
    }
  }
}

Available tools 11

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

inpi
inpi_marcas_busca
Busca marcas no INPI pelo nome/termo (anterioridade/colidência). Retorna até 100 processos (marca, número, classe, situação, titular). Útil pra ver se um nome de marca já está depositado ou registrado.
inpi_marcas_processo
Detalhes completos de um processo de registro de marca no INPI pelo número do processo (situação, depósito, concessão, vigência, titulares, classes Nice/Viena, petições, publicações).
inpi_marcas_processo_resumido
Resumo de um processo de registro de marca no INPI pelo número do processo (marca, titular, classe, situação). Versão enxuta do detalhe completo, mais rápida e barata quando você só precisa do status.
inpi_marcas_titular
Marcas registradas no INPI por titular (CPF ou CNPJ).
inpi_patentes
Patentes registradas no INPI por titular (CPF ou CNPJ).
authenticate
authenticate
MCP.AI for IDE agents (Cursor, etc.): log in in the browser, copy the access token. Best: add it to this server's config as a header `Authorization: Bearer <token>` for a permanent, non-expiring connection. Or paste it here for a session-only login: call with { token: "<jwt>" } after the user pastes, or with no args to get the link.
connect
connect
Returns connection status and URLs. When all providers are connected, returns authenticated:true and empty pending[]. When credentials are missing, returns connect_url for the toolkit and per-install URLs.
marketplace
marketplace
The official mcp.ai marketplace — the in-platform catalog of every MCP/tool, AND the way to run them. Covers capability requests like "find an MCP that does X", "consulta um CPF", "is there a tool for Y". Core flow: action=search discovers MCPs by intent → describe returns one MCP's full profile (every tool with its id + params, pricing, auth) so you pick the right tool_id → invoke RUNS that tool. KEY: invoke works even when the MCP is NOT installed — it runs the tool pontualmente (one-off), without adding the MCP to the toolkit and without bloating the tool list. If the MCP needs a credential/login, invoke returns a connect link; if it is paid and the wallet is empty, invoke returns a checkout/top-up link (the user opens it, then you retry). Use install only to make an MCP PERMANENT in the active toolkit (its tools then show up natively in future sessions); prefer invoke for a single/occasional use. list_tools lists what is callable right now. subscribe/cancel handle per-MCP billing; report_bug sends feedback; request_mcp asks us to build a NEW MCP when nothing fits. Search/describe flag installed_in_toolkit vs installed_in_workspace. Writes (install/uninstall/subscribe/cancel and the one-off install behind invoke) require workspace owner/admin.
report
report_bug
Report a bug, missing feature, or send feedback. Include the conversation array with recent messages for reproduction.
show
show_version
Show the current MCP platform and adapter versions.
toolkit
toolkit_info
Returns the current toolkit state: installed MCPs, their connection status, and how many catalog tools each exposes.

Endpoints

URLTransportStateLatencyChecked
https://api.mcp.ai/p_inpi streamable-http answering 170 ms 7 min ago

INPI — questions

Answers built from our own checks of this server.

What can INPI do?
It exposes 11 tools, read directly from the server on our last check. Among them: authenticate, connect, inpi_marcas_busca, inpi_marcas_processo, inpi_marcas_processo_resumido, inpi_marcas_titular and 5 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is INPI working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 88 of 91 checks got a reply (96.7%), average response time 531 ms. The bar chart above shows every period we have measured.
How do I connect INPI?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does INPI need an API key?
No. INPI completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 11 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is INPI?
It answers our handshake in 531 ms on average, which is faster than 20% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is INPI open source?
Yes — it is published under the MIT licence and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.