Look up a vehicle by license plate against official sources (make/model, year, status, restrictions)
Scored across 7 tools
The marketplace tool is overloaded with many subcommands (search, describe, invoke, install, subscribe, prompts), which overlaps with report_bug, toolkit_info, and even authenticate/connect. The single vehicle tool stands apart, but the meta-tools have blurry boundaries.
Names mix bare verbs (authenticate, connect), verb_noun pairs (report_bug, show_version), and noun phrases (marketplace, toolkit_info, veiculo_dados). The pattern is inconsistent, and languages are mixed (English vs Portuguese).
Seven tools is a reasonable number, but six of them are generic MCP-platform management utilities unrelated to the server's apparent 'Veículo' vehicle purpose. Only one tool actually provides vehicle data, making the set poorly scoped for its intended domain.
For a vehicle-data server, only one lookup operation exists with no other vehicle-related capabilities. The remaining tools cover platform plumbing but not the vehicle domain, leaving significant gaps in what an agent would expect from a 'Veículo' server.
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: "" } after the user pastes, or with no args to get the link.
Inputs: token.
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.
Inputs: no named parameters.
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/ link that opens without login.
Inputs: limit, query, action, mcp_id, +19 more.
Report a bug, missing feature, or send feedback. Include the conversation array with recent messages for reproduction.
Inputs: message (required), context, conversation.
Show the current MCP platform and adapter versions.
Inputs: no named parameters.
Returns the current toolkit state: installed MCPs, their connection status, the accounts connected to each one, and how many catalog tools each exposes.
Inputs: no named parameters.
Consulta os dados de um veículo pela placa + RENAVAM (marca/modelo, ano, combustível, situação, restrições). Funciona para qualquer veículo; não exige login.
Inputs: placa (required), renavam (required).
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Look up PUBLIC vehicle and traffic data from official sources, the same information a citizen access
Look up a UK or Dutch number plate or decode a VIN: make, model, MOT history, mileage checks
Vehicle data from its plate sourced directly from state traffic databases (DETRAN), including debts
License plate lookup for AI agents: plate messages and ALPR history via PlateQuery. OAuth 2.1.
Add one secure layer between your agents and this server.