Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

PegaRex

REMOTE · PEGAREX.COM.BR · SCANNED SEP 28

Search 1.8M+ live Brazilian used-car and motorcycle listings, with FIPE reference prices.

Available components

70 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security74
Transport & Reachability100
Schema Quality & AI Usability73
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1834 tokens (~107/item across 17 items; 17 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
  • Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 17 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 18 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the PegaRex MCP server?

PegaRex is a hosted endpoint at https://pegarex.com.br/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · pegarex.com.br

# add to Claude Code
claude mcp add --transport http br-com-pegarex-mcp 'https://pegarex.com.br/api/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "br-com-pegarex-mcp": {
      "url": "https://pegarex.com.br/api/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "br-com-pegarex-mcp": {
      "type": "http",
      "url": "https://pegarex.com.br/api/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.br-com-pegarex-mcp]
url = "https://pegarex.com.br/api/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "br-com-pegarex-mcp": {
      "type": "remote",
      "url": "https://pegarex.com.br/api/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add br-com-pegarex-mcp --url 'https://pegarex.com.br/api/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  br-com-pegarex-mcp:
    url: "https://pegarex.com.br/api/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "br-com-pegarex-mcp": {
      "Transport": "http",
      "Url": "https://pegarex.com.br/api/mcp"
    }
  }
}
# add to Vellum
assistant mcp add br-com-pegarex-mcp -t streamable-http -u 'https://pegarex.com.br/api/mcp'
// mcp.json
{
  "mcpServers": {
    "br-com-pegarex-mcp": {
      "type": "http",
      "url": "https://pegarex.com.br/api/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 28 Sept 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Sept 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “search_vehicles” rewrote its description, which is the text the model reads security
    • Schema quality: pass → fail ▼ functional
    • Stability: unverified → 0.03 ▲ functional
  • 25 Sept 26 68

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 28 Sept 2026 · Probed https://pegarex.com.br/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=pegarex.com.br CN=YE2,O=Let's Encrypt,C=US 19 Sept 2026 18 Dec 2026 ECDSA 256 ECDSA-SHA384 6b0c43488082d4518b75071dc8be8e14e11
SANs: pegarex.com.br, www.pegarex.com.br
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of pegarex.com.br. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
br. present 38298 13 Verified
com.br. present 2557 13 Verified
pegarex.com.br. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://pegarex.com.br/api/mcp Verified 200
http (plaintext) http://pegarex.com.br/api/mcp HTTPS enforced 301 https://pegarex.com.br/api/mcp
MCP tools · 17 exposed · ~1,538 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
get_alternative_models ~92

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

NameTypeReqDescription
car_idintegeryes–
max_resultsinteger––

No output schema declared.

No examples provided.

get_avg_days_to_sell ~89

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.

NameTypeReqDescription
car_idintegeryes–
granularitystring––

No output schema declared.

No examples provided.

get_cheapest_states ~67

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

NameTypeReqDescription
car_idintegeryes–
top_ninteger––

No output schema declared.

No examples provided.

get_fipe_valuation ~41

Valor oficial da tabela FIPE deste carro e tendência recente. Use para perguntas sobre a FIPE.

NameTypeReqDescription
car_idintegeryes–

No output schema declared.

No examples provided.

get_listing_details ~49

Fatos do próprio anúncio (cor, portas, opcionais, vendedor, fonte, km, link). Use para perguntas diretas sobre este carro específico.

NameTypeReqDescription
car_idintegeryes–

No output schema declared.

No examples provided.

get_market_position ~63

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?'.

NameTypeReqDescription
car_idintegeryes–

No output schema declared.

No examples provided.

get_market_stats ~53

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_mileage_context ~48

Avalia se a quilometragem deste carro é alta ou baixa para o modelo/ano (mediana do mercado + km/ano).

NameTypeReqDescription
car_idintegeryes–

No output schema declared.

No examples provided.

get_price_distribution ~77

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

NameTypeReqDescription
car_idintegeryes–
year_toleranceinteger––

No output schema declared.

No examples provided.

get_similar_active_listings ~112

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

NameTypeReqDescription
car_idintegeryes–
cheaper_onlyboolean––
max_resultsinteger––

No output schema declared.

No examples provided.

get_technical_specs ~100

Ficha técnica completa (motor, potência, torque, câmbio, consumo, desempenho, dimensões, freios, pneus). `section` opcional restringe a uma seção: 'Motor', 'Transmissão', 'Consumo', 'Desempenho', 'Dimensões', 'Freios', 'Pneus', 'Suspensão'.

NameTypeReqDescription
car_idintegeryes–
section–––

No output schema declared.

No examples provided.

get_vehicle_by_id ~71

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.

NameTypeReqDescription
car_idintegeryes–

No output schema declared.

No examples provided.

list_brands ~64

List available vehicle brands (makes) with their catalog id and active listing count. Pass a brand's id as `brand_id` to search_vehicles/list_models for fast, exact filtering.

NameTypeReqDescription
body_style–––
categorystring––

No output schema declared.

No examples provided.

list_filter_options ~54

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_models ~57

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.

NameTypeReqDescription
brand–––
brand_id–––
categorystring––

No output schema declared.

No examples provided.

list_versions ~77

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.

NameTypeReqDescription
brand–––
categorystring––
model–––
model_id–––
year_max–––
year_min–––

No output schema declared.

No examples provided.

search_vehicles ~424

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). Tips for best results: - Free-text `query` matches the listing TITLE only (e.g. "Onix LTZ turbo"). - For exact brand/model/version filtering, resolve names to ids first with list_brands / list_models / list_versions and pass brand_id/model_id/ version_id — it is faster and more accurate than the text fields. - `location` is a 2-letter UF (e.g. "SP") or a city name. - `sort_by="newest"` (default) lists the most recently LISTED cars first — the date a listing first appeared on its source, not when we last saw it. - `sort_by="best_deal"` ranks by lowest price-to-FIPE ratio. - `per_page` is capped at 50. Use `page` (1-20) to paginate; past the first 20 pages, narrow the search with filters. `total_count` and `total_pages` are returned.

NameTypeReqDescription
body_style–––
brand–––
brand_id–––
categorystring––
fuel_type–––
location–––
mileage_max–––
mileage_min–––
model–––
model_id–––
pageinteger––
per_pageinteger––
price_max–––
price_min–––
query–––
sort_bystring––
source–––
transmission–––
version–––
version_id–––
year_max–––
year_min–––

No output schema declared.

No examples provided.

Common questions

What is the PegaRex MCP server?

PegaRex is an MCP server listed in the public MCP registry as br.com.pegarex/mcp. Search 1.8M+ live Brazilian used-car and motorcycle listings, with FIPE reference prices. This page covers its hosted endpoint (https://pegarex.com.br/api/mcp).

Is the PegaRex MCP server safe to use?

PegaRex scores 70 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the PegaRex MCP server expose?

PegaRex exposes 17 tools: search_vehicles, get_vehicle_by_id, get_market_stats, list_brands, list_models, and 12 more. Their descriptions and schemas cost roughly 1,538 tokens of context every time the server is loaded.

Does the PegaRex MCP server require authentication?

No. We connected to PegaRex without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the PegaRex MCP server still maintained?

PegaRex is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.