Webmotors

Reviewed 19h ago.

• tools: 12 tools scanned
• metadata: scanned

No findings.

Tools (12)

• webmotors_search

  Busca anúncios de veículos na Webmotors. Filtre por marca e modelo; pagine e ordene. Retorna { total, results[] } com { id, title, make, model, version, year, km, price, fipePercent, slug, detailUrl, seller, photo }. Use o `slug` em wm_detail e o `id` em wm_market_price.

• webmotors_detail

  Detalhe completo de um anúncio. Informe o `slug` retornado por wm_search (o caminho após /comprar, ex.: '/honda/civic/2-0-.../4-portas/2023/71895570'). Retorna specs, preços, vendedor, fotos e descrição.

• webmotors_market_price

  Preço médio de mercado do modelo de um anúncio (id = UniqueId de wm_search). Retorna { Make, Model, Version, Year, FipeCode, FipePrice, BiggestPrice, MediumPrice, SmallestPrice }. Diferencial sobre a FIPE: reflete o preço real pedido no marketplace. Bulk support: accepts ids for batched execution.

• webmotors_location

  Resolve uma localização (cidade/estado/geo) a partir de um texto livre, para filtrar a busca por região.

• webmotors_filters

  Lista as opções de filtro da busca (marcas, modelos e demais facetas) para montar consultas válidas.

• webmotors_category

  Lista as categorias de veículo da Webmotors.

• show_version

  Show the current MCP platform and adapter versions.

• report_bug

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

• 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.

• 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.

• 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;

• 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.