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.

fipeX MCP

REMOTE · API.FIPEX.COM.BR · SCANNED SEP 22

Brazilian FIPE vehicle reference prices: search, current price, history and comparison. Keyless.

Available components

remote · api.fipex.com.br 82
0 this week 82 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 Security66
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
Schema Quality & AI Usability74
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 650 tokens (~162/item across 4 items; 4 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 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 fipeX MCP server?

fipeX MCP is a hosted endpoint at https://api.fipex.com.br/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 · api.fipex.com.br

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

  • 2 Sept 26 0
    • Server version: 2.12.1 → 2.13.0 functional
  • 26 Aug 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
  • 25 Aug 26 0
    • Stability: 0.97 → pass security
  • 11 Aug 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
  • 31 Jul 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
  • 30 Jul 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
  • 28 Jul 26 0
    • DNSSEC: fail → pass ▲ security
  • 27 Jul 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
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 22 Sept 2026 · Probed https://api.fipex.com.br/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=fipex.com.br CN=WE1,O=Google Trust Services,C=US 29 Jul 2026 27 Oct 2026 ECDSA 256 ECDSA-SHA256 21fdf0395812105913d172f66ff2f14f
SANs: fipex.com.br, *.fipex.com.br
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of api.fipex.com.br. — Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
br. present 38298 13 Verified
com.br. present 2557 13 Verified
fipex.com.br. present 2371 13 Verified
api.fipex.com.br. Verified address RRset verified with the apex keys
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
Header Value
strict-transport-security max-age=0; includeSubDomains; preload
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy no-referrer

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.fipex.com.br/mcp Verified 200
http (plaintext) http://api.fipex.com.br/mcp HTTPS enforced 301 https://api.fipex.com.br/mcp
MCP tools · 4 exposed · ~650 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
compare_prices ~97

Compare the latest FIPE price and history of up to 10 vehicles side by side. Each spec is "model-slug,fuel-slug,year"; separate specs with semicolons.

NameTypeReqDescription
vehicle_specsstringyesup to 10 vehicles, each "model-slug,fuel-slug,year", separated by semicolons (e.g. "argo,flex,2022;onix,flex,2022")

No output schema declared.

No examples provided.

get_price ~180

Get the latest FIPE price for one vehicle, identified by model_slug + fuel_acronym + year, or by model_id + fuel_id + year. Year is "2022" (a model year) or "zero" (0 km / brand new).

NameTypeReqDescription
fuel_acronymstring–single-letter fuel acronym, e.g. "g" gasoline, "e" ethanol, "f" flex, "d" diesel
fuel_idstring–fuel UUID (alternative to fuel_acronym)
model_idstring–model UUID (alternative to model_slug)
model_slugstring–model slug, e.g. "argo" (pair with fuel_acronym)
yearstringyesmodel year like "2022", or "zero" for 0 km / brand new

No output schema declared.

No examples provided.

get_price_history ~107

Get the monthly FIPE price history for one vehicle, identified by model_id + fuel_id + year. Year is "2022" (a model year) or "zero" (0 km / brand new).

NameTypeReqDescription
fuel_idstringyesfuel UUID (from search_vehicles)
model_idstringyesmodel UUID (from search_vehicles)
yearstringyesmodel year like "2022", or "zero" for 0 km / brand new

No output schema declared.

No examples provided.

search_vehicles ~266

Search Brazilian FIPE vehicles by free-text query (make, model, year, fuel). Returns matching vehicles with their slugs and IDs — the entry point that resolves names into the identifiers get_price, get_price_history and compare_prices need.

NameTypeReqDescription
limitinteger–results per page, 1-50, defaults to 10
pageinteger–1-based page number, defaults to 1
price_maxnumber–maximum current price in BRL (reais), inclusive (e.g. 78000)
price_minnumber–minimum current price in BRL (reais), inclusive (e.g. 50000)
querystringyesfree-text search over make, model, year and fuel (e.g. "fiat argo 2022 flex"). Make names in the query are hard-filtered automatically
vehicle_typestring–filter by vehicle type: carro, moto or caminhao
year_maxinteger–maximum model year, inclusive
year_mininteger–minimum model year, inclusive (e.g. 2006). 0 km vehicles have no year and are excluded by year filters; search them with 'zero km' in the query

No output schema declared.

No examples provided.

Common questions

What is the fipeX MCP server?

fipeX MCP is listed in the public MCP registry as br.com.fipex/mcp. Brazilian FIPE vehicle reference prices: search, current price, history and comparison. Keyless. This page covers its hosted endpoint (https://api.fipex.com.br/mcp).

Is the fipeX MCP server safe to use?

fipeX MCP scores 82 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 fipeX MCP server expose?

fipeX MCP exposes 4 tools: compare_prices, get_price, get_price_history, search_vehicles. Their descriptions and schemas cost roughly 650 tokens of context every time the server is loaded.

Does the fipeX MCP server require authentication?

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

Is the fipeX MCP server still maintained?

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