Factline Vehicles

by snefhewio.github.snefhew/factline-vehiclesv0.10.0

How the score works

Dutch licence plates: APK, recalls, odometer, history, model reliability. 5 checks a day free.

  • Remote endpoint

Uptime

Checked  · every day

100%from 7 days of checks

Up without downtime on 7 of 7 days with data.

  • No downtime
  • Degraded
  • Down over 5 minutes
  • No data
  • Not checked yet

Response time

Median 970 ms, slowest 5% 2150 ms for the handshake and the tool list, over 30 days.

2000 ms1000 ms0

How far each check got

  • Reached the address 100%
  • Completed the handshake 100%
  • Listed its tools 100%

3 tools at the last answer; the list changed on 6 Nov.

Every day
DayResultChecksMedian
6 Nov (today)No downtime1588 ms
5 NovNo downtime1of 1881 ms
4 NovNo downtime1of 1987 ms
3 NovNo downtime1of 11589 ms
2 NovNo downtime1of 1864 ms
1 NovNo downtime1of 11763 ms
31 OctNo downtime21310 ms

A failure counts as down time only when a second check five minutes later fails too. How we check

Connect to the publisher's own endpoint

Add to ~/.gemini/settings.json:

{
  "mcpServers": {
    "factline-vehicles": {
      "httpUrl": "https://factline.dev/mcp/vehicles"
    }
  }
}
For agents: the install prompt

Every step above as one Markdown text, for an assistant installing it for you.

# Install the MCP server Factline Vehicles (`io.github.snefhew/factline-vehicles`)

Its page: https://plug.directory/servers/io.github.snefhew/factline-vehicles

It runs on the publisher's servers; the client connects to its URL.

Use the section for the person's client.

## Claude Desktop

Paste into Settings › Connectors › Add custom connector:

```text
https://factline.dev/mcp/vehicles
```

## Claude Code

Run in a terminal:

```sh
claude mcp add --transport http factline-vehicles https://factline.dev/mcp/vehicles
```

## Cursor, Devin Desktop, LM Studio, oterm, Bob Shell, ECA, Kiro, Kiro CLI

Merge into the place for the person's client:

- Cursor: ~/.cursor/mcp.json
- Devin Desktop: ~/.config/devin/mcp_config.json
- LM Studio: mcp.json (Program › Install › Edit mcp.json)
- oterm: config.json in oterm's data folder (~/Library/Application Support/oterm on macOS, ~/.local/share/oterm on Linux, %APPDATA%\oterm on Windows)
- Bob Shell: ~/.bob/settings/mcp.json (global) or .bob/mcp.json (project)
- ECA: ~/.config/eca/config.json (global) or .eca/config.json in the project
- Kiro: ~/.kiro/settings/mcp.json (user) or .kiro/settings/mcp.json (workspace)
- Kiro CLI: ~/.kiro/settings/mcp.json (user) or .kiro/settings/mcp.json (workspace)

```json
{
  "mcpServers": {
    "factline-vehicles": {
      "url": "https://factline.dev/mcp/vehicles"
    }
  }
}
```

## VS Code

Merge into .vscode/mcp.json:

```json
{
  "servers": {
    "factline-vehicles": {
      "type": "http",
      "url": "https://factline.dev/mcp/vehicles"
    }
  }
}
```

## Zed

Merge into ~/.config/zed/settings.json:

```json
{
  "context_servers": {
    "factline-vehicles": {
      "url": "https://factline.dev/mcp/vehicles"
    }
  }
}
```

## Cline

Merge into cline_mcp_settings.json (MCP Servers › Configure › Configure MCP Servers):

```json
{
  "mcpServers": {
    "factline-vehicles": {
      "type": "streamableHttp",
      "url": "https://factline.dev/mcp/vehicles"
    }
  }
}
```

## Continue

Merge into ~/.continue/config.yaml:

```yaml
mcpServers:
  - name: "factline-vehicles"
    type: streamable-http
    url: "https://factline.dev/mcp/vehicles"
```

## Goose

Merge into ~/.config/goose/config.yaml:

```yaml
extensions:
  "factline-vehicles":
    type: streamable_http
    name: "factline-vehicles"
    enabled: true
    uri: "https://factline.dev/mcp/vehicles"
    headers: {}
    env_keys: []
    envs: {}
    timeout: 300
```

## Gemini CLI

Merge into ~/.gemini/settings.json:

```json
{
  "mcpServers": {
    "factline-vehicles": {
      "httpUrl": "https://factline.dev/mcp/vehicles"
    }
  }
}
```

## Codex

Run in a terminal:

```sh
codex mcp add factline-vehicles --url https://factline.dev/mcp/vehicles
```

## mcp-client-cli, TUUI, BoltAI

This server's endpoint speaks streamable HTTP, which this client's documentation does not list among its transports; use another client for it.

## Agenvoy

Merge into ~/.config/agenvoy/mcp.json:

```json
{
  "servers": {
    "factline-vehicles": {
      "url": "https://factline.dev/mcp/vehicles"
    }
  }
}
```

## Amp

Merge into ~/.config/amp/settings.json (user) or .amp/settings.json (workspace):

```json
{
  "amp.mcpServers": {
    "factline-vehicles": {
      "url": "https://factline.dev/mcp/vehicles"
    }
  }
}
```

## AnythingLLM

Merge into anythingllm_mcp_servers.json in the AnythingLLM storage plugins directory:

```json
{
  "mcpServers": {
    "factline-vehicles": {
      "type": "streamable",
      "url": "https://factline.dev/mcp/vehicles"
    }
  }
}
```

## Augment Code

Merge into Augment Settings Panel – MCP section – Import from JSON (VS Code extension):

```json
{
  "mcpServers": {
    "factline-vehicles": {
      "type": "http",
      "url": "https://factline.dev/mcp/vehicles"
    }
  }
}
```

Then restart the client, or reload its MCP servers, and ask it to list the server's tools to confirm it started.

From the publisher's entry in the Official MCP Registry (the registry entry). Report a problem