Consulta de Radar (PSIE/Inmetro)

io.github.mcp-dirPublished by GitHub account mcp-dirv0.1.0Updated Oct 27, 2026

Look up the metrological status of a city's speed cameras and breathalyzers in Inmetro's official re

VerifiedStreamable HTTPWeb executableLocation & LifestyleDeveloper Tools

Overview

AI-generated overview

Remote MCP server for querying Inmetro's PSIE radar registry by municipality, plus mcp.ai platform tools for marketplace, auth and feedback.

What you can do
  • Look up Inmetro instruments (speed radars and breathalyzers by default) for a municipality, with serial number, direction, nominal speed, responsible party, location, declaration and validity dates, and metrological result (approved, rejected, repaired).
  • Check platform and adapter versions.
  • Report bugs or send feedback, optionally with recent conversation messages.
  • Inspect connection status, connect URLs and toolkit state (installed MCPs, connected accounts, tool counts).
  • Search and describe MCPs in the mcp.ai marketplace by intent.
  • Authenticate with a browser-obtained token, either as a session login or a bearer header.
When to use it
Useful when you need to verify whether a specific speed radar or breathalyzer in a Brazilian municipality has a valid Inmetro metrological declaration, for example before contesting a fine. The remaining tools are platform plumbing for the mcp.ai hosting service rather than radar data.
Requirements
Runs as a remote streamable HTTP endpoint; no package or local runtime needed. No authentication is declared, though the authenticate tool describes an optional bearer token for a permanent connection. Network access to the endpoint is required.
Before you install
The authenticate tool asks for an access token (a JWT) to be pasted or stored in a header; treat it as a secret. The report_bug tool can send recent conversation messages to the provider. The marketplace and toolkit tools describe and connect other MCP servers, which may involve further credentials. Radar results come from a third-party registry and should be confirmed at the official source.

Installation

In SourceWeft

  1. Open Consulta de Radar (PSIE/Inmetro) in the dashboard and add it to a workspace.
  2. 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.mcp-dir%2Fpsie-mcp/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.

{
  "mcpServers": {
    "consulta-de-radar-psie-inmetro": {
      "type": "http",
      "url": "https://api.mcp.ai/p_psie"
    }
  }
}

README

This repository has no README.

Tools

7

psie_consulta_municipio

Lista os instrumentos do Inmetro (radares/medidores de velocidade por padrão) de um município e a situação metrológica de cada um: Nº de Série, Sentido, Vel. Nominal, Responsável, Local, Data da Declaração, Data Validade e Resultado (Aprovado/Reprovado/Reparado). Use pra checar se o radar que autuou (case o Nº de Série da sua multa na lista) estava aprovado e dentro da validade na data da infração. Consulta paga (debita a carteira).

Parametersufrequiredtipomunicipiorequired

show_version

Show Version

Show the current MCP platform and adapter versions.

Takes no parameters.

report_bug

Report Bug

Report a bug, missing feature, or send feedback. Include the conversation array with recent messages for reproduction.

Parameterscontextmessagerequiredconversation

connect

Connection Status

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.

Takes no parameters.

toolkit_info

Toolkit Info

Returns the current toolkit state: installed MCPs, their connection status, the accounts connected to each one, and how many catalog tools each exposes.

Takes no parameters.

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. It also carries the mcp.ai PROMPT LIBRARY, which is about ready-made prompt TEXT rather than MCPs: search_prompts finds one, get_prompt returns its full text with {{variables}} filled, and publish_prompt saves a prompt and returns a shareable mcp.ai/p/<slug> link that opens without login.

Parameterslimitqueryactionmcp_idmessagetool_idargumentsimmediatetier_slugprompt_bodyprompt_slugprompt_tool+11 more

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.

Parameterstoken

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

75% 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 listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

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

  • License10 pts

    Declare a license in the repository or the registry entry.