PegaRex MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PEGAREX_MCP_URL | No | URL of the PegaRex MCP endpoint. Defaults to https://pegarex.com.br/api/mcp. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_vehiclesA | Search 1.8M+ Brazilian vehicle listings aggregated from 96 platforms (OLX, Webmotors, Napista, etc.). Returns listings with price, year, mileage, location, source platform, the original ad URL, FIPE reference price and a deal_score (% vs FIPE; negative means priced below FIPE). |
| get_vehicle_by_idB | Fetch the full details of a single listing by its PegaRex id: brand, model, version, year, price, mileage, fuel, transmission, city/state, FIPE price, deal_score, source platform and the original ad URL. |
| get_market_statsA | Live size of the PegaRex database: total active listings, number of source platforms, and when the data was last refreshed. Use this for the current count instead of quoting a fixed number. |
| list_brandsA | List available vehicle brands (makes) with their catalog id and active
listing count. Pass a brand's id as |
| list_modelsA | List models for a brand (pass brand_id from list_brands, or a brand name) with each model's catalog id and active listing count. |
| list_versionsA | List versions/trims for a model (pass model_id from list_models, or brand+model names) with each version's catalog id and active listing count. |
| list_filter_optionsA | Return the valid values for the constrained search filters — fuel_type, transmission, sort_by — and the list of source platforms. Use this to build a valid call to search_vehicles in a single round-trip. |
| get_listing_detailsA | Fatos do próprio anúncio (cor, portas, opcionais, vendedor, fonte, km, link). Use para perguntas diretas sobre este carro específico. |
| get_technical_specsB | Ficha técnica completa (motor, potência, torque, câmbio, consumo,
desempenho, dimensões, freios, pneus). |
| get_avg_days_to_sellA | Tempo médio (mediana) que anúncios semelhantes ficam ativos antes de sair do ar — estimativa de liquidez/tempo de venda. 'model_year' (padrão) = mesmo modelo e ano; 'model' = todos os anos; 'model_state' = neste estado. |
| get_cheapest_statesA | Estados (UF) onde este modelo está mais barato agora, por preço mediano crescente. Use para 'onde é mais barato comprar'. (top_n padrão 5, máx 10.) |
| get_market_positionA | Posição de preço DESTE anúncio: vs. tabela FIPE e vs. o mercado de anúncios ativos do mesmo modelo. Use para 'esse preço é bom?' / 'está caro ou barato?'. |
| get_price_distributionA | Faixa de preços (mínimo, p25, mediana, p75, máximo) de anúncios ativos semelhantes. Use para dar contexto de preço. (year_tolerance ±anos, padrão 1, máx 5.) |
| get_similar_active_listingsA | Outras unidades à venda do MESMO modelo (mesmo carro, outros anúncios) — ex.: mais baratas, outras cores/anos. Use para 'tem opções mais baratas DESTE carro?'. NÃO use para sugerir modelos diferentes. (max_results padrão 5, máx 8; cheaper_only=true só mais baratos que este.) |
| get_alternative_modelsA | Sugere OUTROS MODELOS diferentes (outras marcas/modelos) na mesma categoria, faixa de preço e tipo de carroceria — alternativas de compra. Use para 'recomende outros modelos' / 'alternativas a este carro'. (max_results padrão 4, máx 6.) |
| get_fipe_valuationB | Valor oficial da tabela FIPE deste carro e tendência recente. Use para perguntas sobre a FIPE. |
| get_mileage_contextA | Avalia se a quilometragem deste carro é alta ou baixa para o modelo/ano (mediana do mercado + km/ano). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 17 tools
Most tools have clearly distinct purposes: search, market stats, model alternatives, FIPE, and catalog listing are all separable. The only real overlap is get_vehicle_by_id and get_listing_details, both return details about a single listing, though one focuses on catalog/price fields and the other on ad-specific facts.
All tools consistently follow verb_noun snake_case naming: get_* for analyses/detail lookups, list_* for catalog options, and search_vehicles for the main query. There are no mixed conventions or vague verbs.
17 tools is at the high end for an MCP server, and several are narrow analytics endpoints (avg_days_to_sell, cheapest_states, market_position) that could be consolidated. Still, each tool has a distinct role, so the count is not excessive enough for a lower score.
The server covers the full read-only lifecycle for vehicle listings: search and filtering, single-listing details, catalog resolution, market pricing context, FIPE valuation, and alternatives. There are no obvious dead-end queries for a user researching or comparing Brazilian car listings.