Monitor de Marcas INPI — Alertas da RPI por Processo

io.github.paulovitortiPublished by GitHub account paulovitortiv1.0.0Updated Oct 24, 2026

Monitora marcas no INPI e alerta despachos novos da RPI por processo ou titular.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

A remote MCP server that monitors INPI trademarks and alerts on new RPI dispatches by process or holder.

What you can do
Monitor trademark processes at INPI and detect new RPI dispatches by process number or holder name, based on the registry description. The manifest lists no individual tools, so the exact operations are not documented here. It runs as a hosted remote endpoint rather than a local package.
When to use it
Useful for trademark owners, agents or paralegals who want an assistant to keep track of new INPI RPI publications for specific processes or holders instead of checking manually.
Requirements
A remote endpoint at mcp.apify.com reached over streamable HTTP, with OAuth authentication required. No environment variables or headers are declared. Network access is needed.
Before you install
OAuth sign-in is required, so the assistant acts under your account. The server watches trademark publications and may send alerts; the manifest lists no tools, so confirm what it reads or changes before relying on it. Data about your processes and holders is handled by a third-party host.

Installation

In SourceWeft

  1. Open Monitor de Marcas INPI — Alertas da RPI por Processo in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.paulovitorti%2Frpi-inpi-delta-monitor-marcas/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "monitor-de-marcas-inpi-alertas-da-rpi-po": {
      "type": "http",
      "url": "https://mcp.apify.com/?tools=paulovitor18/rpi-inpi-delta-monitor-marcas"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.