Is the Com Fipex MCP server down?

mcp-registry/br.com.fipex/mcp · v2.18.2

healthy
Last checked 2026-10-23 16:12 UTC · handshake 603ms

As of 2026-10-23 16:12 UTC, the Com Fipex MCP server is up with a Glimind reliability score of 80/100 (grade B). Over the last 30 days it answered 99.7% of Glimind's liveness checks. It had 28 outages in 90 days, with a median recovery of 5 minutes.

uptime (30d checks)
99.7%
checks observed
4,430
outages (90d)
28
tools
4

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

Install Com Fipex MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http com-fipex-mcp-server https://api.fipex.com.br/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "com-fipex-mcp-server": {
      "type": "http",
      "url": "https://api.fipex.com.br/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: B (84/100)

B (84/100): 0 error(s), 2 warning(s) across 4 tool(s); ~880 tokens of tool definitions.
Scores higher than 44% of 15,589 MCP servers Glimind has audited.
Its tool list costs an agent ~880 tokens per session — lighter than 80% of servers.
84 → 84 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions100
Safety hints30
Token cost100
Client compatibility70
Protocol100
Reliability85
Stability100

What to fix (3)

4 of 4 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: compare_prices, get_price, get_price_history, search_vehicles

Handshake + tools/list takes ~1,801 ms.

Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Auto-fix: 4 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fbr.com.fipex%2Fmcp/fixes

compare_prices 1 change
{
  "name": "compare_prices",
  "description": "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.",
  "inputSchema": {
    "type": "object",
    "required": [
      "vehicle_specs"
    ],
    "properties": {
      "vehicle_specs": {
        "type": "string",
        "description": "up to 10 vehicles, each \"model-slug,fuel-slug,year\", separated by semicolons (e.g. \"argo,flex,2022;onix,flex,2022\")"
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  }
}
get_price 1 change
{
  "name": "get_price",
  "description": "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).",
  "inputSchema": {
    "type": "object",
    "required": [
      "year"
    ],
    "properties": {
      "year": {
        "type": "string",
        "description": "model year like \"2022\", or \"zero\" for 0 km / brand new"
      },
      "fuel_id": {
        "type": "string",
        "description": "fuel UUID (alternative to fuel_acronym)"
      },
      "model_id": {
        "type": "string",
        "description": "model UUID (alternative to model_slug)"
      },
      "model_slug": {
        "type": "string",
        "description": "model slug, e.g. \"argo\" (pair with fuel_acronym)"
      },
      "fuel_acronym": {
        "type": "string",
        "description": "single-letter fuel acronym, e.g. \"g\" gasoline, \"e\" ethanol, \"f\" flex, \"d\" diesel"
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  }
}
get_price_history 1 change
{
  "name": "get_price_history",
  "description": "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).",
  "inputSchema": {
    "type": "object",
    "required": [
      "model_id",
      "fuel_id",
      "year"
    ],
    "properties": {
      "year": {
        "type": "string",
        "description": "model year like \"2022\", or \"zero\" for 0 km / brand new"
      },
      "fuel_id": {
        "type": "string",
        "description": "fuel UUID (from search_vehicles)"
      },
      "model_id": {
        "type": "string",
        "description": "model UUID (from search_vehicles)"
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/br.com.fipex/mcp"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/br.com.fipex/mcp"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fbr.com.fipex%2Fmcp.svg)](https://glimind.com/server/mcp-registry%2Fbr.com.fipex%2Fmcp?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fbr.com.fipex%2Fmcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fbr.com.fipex%2Fmcp.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fbr.com.fipex%2Fmcp.svg
   :target: https://glimind.com/server/mcp-registry%2Fbr.com.fipex%2Fmcp?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:0024cbac3574eac2…, first seen 2026-10-17, included at leaf 627 of 52,991. Version history · verify what your client received.

Tools (4)

Compare: most reliable data servers · most reliable search servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Com Fipex MCP server down right now?

As of 2026-10-23 16:12 UTC, the Com Fipex MCP server is up with a Glimind reliability score of 80/100 (grade B). Over the last 30 days it answered 99.7% of Glimind's liveness checks. It had 28 outages in 90 days, with a median recovery of 5 minutes.

How many tools does Com Fipex MCP server provide?

Com Fipex MCP server advertises 4 tools, including compare_prices, get_price, get_price_history, search_vehicles.

How do I install Com Fipex MCP server?

Point your MCP client at this streamable-http endpoint: https://api.fipex.com.br/mcp

Is the Com Fipex MCP server safe to connect to an AI agent?

Glimind scanned all 4 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Com Fipex MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve