PegaRex
REMOTE · PEGAREX.COM.BR
Search 1.8M+ live Brazilian used-car and motorcycle listings, with FIPE reference prices.
Available components
Last scanned (2 hours ago)
Scores higher than 7% of remote servers
Reachable. Last reached 22 Nov 2026.
Category E-commerce
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 410. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Checks we ran (5)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
Checks we could not complete (6)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 14 Nov 26 −13
- Endpoint reachability: behind authorisation → not serving MCP ▼ security
- Transport: unverified → fail ▼ security
- Authorization: pass → unverified ▼ security
- Tool safety: Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list. security
- Tool coverage: Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list. functional
- Capabilities: Capabilities not yet verified: we couldn't read the endpoint's capabilities. functional
- Schema quality: Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list. functional
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 17 Oct 26 0
- Endpoint reachability: reachable → behind authorisation ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: 0.70 → unverified ▼ security
- Transport: pass → unverified ▼ security
- Authorization: partial → pass ▲ security
- First check of Authorization: partial security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 14 Oct 26 0
- Tool “search_vehicles” rewrote its description, which is the text the model reads security
- 2 Oct 26 0
- MCP protocol: Implements a current MCP spec version (2026-07-28). functional
- MCP protocol version: 2025-11-25 → 2026-07-28 functional
- Server version: 1.28.0 → 1.0.0 functional
- 28 Sept 26 0
- 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 0
- 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 0
First indexed and scored.
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 22 Nov 2026 · Probed https://pegarex.com.br/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=pegarex.com.br | CN=YE1,O=Let's Encrypt,C=US | 18 Nov 2026 | 16 Feb 2027 | ECDSA 256 | ECDSA-SHA384 | 6d876966723a5106a7c171003153dca5e9f |
| SANs: pegarex.com.br, www.pegarex.com.br | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| 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. | DS published | 38298 | 13 | Verified |
| com.br. | DS published | 41748 | 13 | Verified |
| pegarex.com.br. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 410 |
| Header | Value |
|---|---|
| content-security-policy | frame-ancestors 'self' |
| x-frame-options | SAMEORIGIN |
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 | HTTP error | 410 | |
| http (plaintext) | http://pegarex.com.br/api/mcp | HTTPS enforced | 301 | https://pegarex.com.br/api/mcp |
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 →
get_alternative_models 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.)
| Name | Type | Req | Description |
|---|---|---|---|
| car_id | integer | yes | – |
| max_results | integer | – | – |
No output schema declared.
No examples provided.
get_avg_days_to_sell Average 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.
| Name | Type | Req | Description |
|---|---|---|---|
| car_id | integer | yes | – |
| granularity | string | – | – |
No output schema declared.
No examples provided.
get_cheapest_states 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.)
| Name | Type | Req | Description |
|---|---|---|---|
| car_id | integer | yes | – |
| top_n | integer | – | – |
No output schema declared.
No examples provided.
get_fipe_valuation FIPE valuation ~91
Valor oficial da tabela FIPE deste carro e tendência recente. Use para perguntas sobre a FIPE. `fipe_year` é o ano FIPE usado; 32000 é como a FIPE escreve "0 km" (carro novo) — mostre `fipe_year_label` ("0 km"), nunca "32000".
| Name | Type | Req | Description |
|---|---|---|---|
| car_id | integer | yes | – |
No output schema declared.
No examples provided.
get_listing_details 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.
| Name | Type | Req | Description |
|---|---|---|---|
| car_id | integer | yes | – |
No output schema declared.
No examples provided.
get_market_position Market position vs FIPE ~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?'.
| Name | Type | Req | Description |
|---|---|---|---|
| car_id | integer | yes | – |
No output schema declared.
No examples provided.
get_market_stats 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 Mileage context ~48
Avalia se a quilometragem deste carro é alta ou baixa para o modelo/ano (mediana do mercado + km/ano).
| Name | Type | Req | Description |
|---|---|---|---|
| car_id | integer | yes | – |
No output schema declared.
No examples provided.
get_price_distribution 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.)
| Name | Type | Req | Description |
|---|---|---|---|
| car_id | integer | yes | – |
| year_tolerance | integer | – | – |
No output schema declared.
No examples provided.
get_similar_active_listings Similar 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.)
| Name | Type | Req | Description |
|---|---|---|---|
| car_id | integer | yes | – |
| cheaper_only | boolean | – | – |
| max_results | integer | – | – |
No output schema declared.
No examples provided.
get_technical_specs 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'.
| Name | Type | Req | Description |
|---|---|---|---|
| car_id | integer | yes | – |
| section | – | – | – |
No output schema declared.
No examples provided.
get_vehicle_by_id Get listing 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.
| Name | Type | Req | Description |
|---|---|---|---|
| car_id | integer | yes | – |
No output schema declared.
No examples provided.
list_brands 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.
| Name | Type | Req | Description |
|---|---|---|---|
| body_style | – | – | – |
| category | string | – | – |
No output schema declared.
No examples provided.
list_filter_options 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 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.
| Name | Type | Req | Description |
|---|---|---|---|
| brand | – | – | – |
| brand_id | – | – | – |
| category | string | – | – |
No output schema declared.
No examples provided.
list_versions 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.
| Name | Type | Req | Description |
|---|---|---|---|
| brand | – | – | – |
| category | string | – | – |
| model | – | – | – |
| model_id | – | – | – |
| year_max | – | – | – |
| year_min | – | – | – |
No output schema declared.
No examples provided.
search_vehicles Search vehicle listings ~554
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). A car listed on several sites comes back once (vehicle_sites says how many sites carry it); filtering by `source` returns that site's own ads instead. price_kind is set when the asking price is not the car's sale price ("installment": a monthly installment or down payment posted as the price; "equity": ágio, the buyer takes over a financing; "suspect" / "outlier_high": check the ad) — never present such a price as a bargain. Tips for best results: - Free-text `query` matches the listing TITLE only (e.g. "Onix LTZ turbo"). It needs at least one word of 3+ characters: "Ford Ka", not "Ka" alone. - 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.
| Name | Type | Req | Description |
|---|---|---|---|
| body_style | – | – | – |
| brand | – | – | – |
| brand_id | – | – | – |
| category | string | – | – |
| fuel_type | – | – | – |
| location | – | – | – |
| mileage_max | – | – | – |
| mileage_min | – | – | – |
| model | – | – | – |
| model_id | – | – | – |
| page | integer | – | – |
| per_page | integer | – | – |
| price_max | – | – | – |
| price_min | – | – | – |
| query | – | – | – |
| sort_by | string | – | – |
| source | – | – | – |
| transmission | – | – | – |
| version | – | – | – |
| version_id | – | – | – |
| year_max | – | – | – |
| year_min | – | – | – |
No output schema declared.
No examples provided.
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
claude mcp add --transport http br-com-pegarex-mcp 'https://pegarex.com.br/api/mcp'
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 23 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,718 tokens of context every time the server is loaded.
Does the PegaRex MCP server require authentication?
Its publisher declares no required credentials for PegaRex. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the PegaRex MCP server still maintained?
PegaRex is still listed as active in the MCP registry. We last reached this channel on 22 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the PegaRex MCP server?
VerifyMCP ran 5 checks on PegaRex, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 1 more. 6 items could not be completed, a gap on our side rather than a finding about PegaRex: Authorization, Schema quality, Stability, Tool coverage and 2 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.