# Loutre (remote · api.loutre.app)

Hosted mock APIs from OpenAPI, TypeScript or Postman: realistic data, errors and latency on demand.

- Trust score: 56/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `api.loutre.app`: 56/100 (this document), [markdown](https://verifymcp.io/servers/app-loutre-loutre/api.md), [page](https://verifymcp.io/servers/app-loutre-loutre/api)

## Channel facts

- Endpoint: `https://api.loutre.app/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 17 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 64/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 2389 tokens (~140/item across 17 items; 17 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 96/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 87% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "clear_rules" implies "remove" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 18 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Loutre MCP server?

Loutre is a hosted endpoint at https://api.loutre.app/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.

### Claude

```bash
claude mcp add --transport http app-loutre-loutre 'https://api.loutre.app/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "app-loutre-loutre": {
      "url": "https://api.loutre.app/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "app-loutre-loutre": {
      "type": "http",
      "url": "https://api.loutre.app/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.app-loutre-loutre]
url = "https://api.loutre.app/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "app-loutre-loutre": {
      "type": "remote",
      "url": "https://api.loutre.app/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add app-loutre-loutre --url 'https://api.loutre.app/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  app-loutre-loutre:
    url: "https://api.loutre.app/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "app-loutre-loutre": {
      "Transport": "http",
      "Url": "https://api.loutre.app/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add app-loutre-loutre -t streamable-http -u 'https://api.loutre.app/mcp'
```

### Other

```json
{
  "mcpServers": {
    "app-loutre-loutre": {
      "type": "http",
      "url": "https://api.loutre.app/mcp"
    }
  }
}
```

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

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 56, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-03 (score 55, +1)

- [functional improvement] Stability: unverified → 0.03
- [cosmetic] “create_mock” added an optional parameter “locale”
- [cosmetic] “regenerate_mock” added an optional parameter “locale”

### 2026-11-02 (score 54)

First indexed and scored.

## MCP tools (17)

### `create_mock` (~365 tokens)

Create a hosted mock from an OpenAPI 3.0/3.1 or Swagger 2.0 document (YAML or JSON), from TypeScript types (interfaces, types, enums: CRUD routes derived, or a route map type keyed like "GET /users") or from a Postman v2 collection, an Insomnia export (v4 JSON or v5 YAML), a Bruno collection (JSON export, or .bru files one after the other), a HAR file (headers and cookies are dropped, data is generated), a json-server db.json (records served as they are), curl commands, or a GraphQL schema (SDL or introspection JSON; Pro plan: queries, mutations and introspection answered on POST /graphql). OpenAPI 3.2 is read too. Give the document in `spec`, or its public address in `url` (then the mock re-reads it every six hours and follows changes). Returns the URL, the route list and an ownerToken to keep for later changes. Data is realistic and coherent, generated once. Without an account the mock lives seven days.

Input parameters:

- `auto` (boolean): With url: re-read every six hours (default true)
- `locale` (string): Language of names, addresses, texts and error messages (default: the request's language, else English)
- `seed` (string): Data seed, for reproducible data sets
- `slug` (string): Desired subdomain (Pro plan)
- `spec` (string): The full document, verbatim: OpenAPI, Swagger, TypeScript types, a Postman, Insomnia or Bruno collection, a HAR file, a db.json or curl commands
- `url` (string): Public URL of the document, instead of spec

### `list_mocks` (~28 tokens)

List the connected account's mocks (API token required), with their URL, routes and expiry.

### `get_mock` (~74 tokens)

Details of a mock: routes with identifiers, behaviour, lock, sample generated bodies per route.

Input parameters:

- `ownerToken` (string): Owner token received at creation (not needed when the account is connected with an API token)
- `slug` (string, required): Subdomain of the mock, e.g. "brisk-otter"

### `call_mock` (~262 tokens)

Call a route of the mock like an HTTP client would and return the status, the x-loutre-* headers and the body. The headers x-loutre-status, x-loutre-delay, x-loutre-count, x-loutre-message and x-loutre-seed are honoured; latency is not awaited, it is reported in delayMs. Writes (POST, PUT, PATCH, DELETE) are persisted when persistent state is on. For a GraphQL mock, POST to its GraphQL path with the body { "query": "…", "variables": { … } }; mutations are persisted the same way.

Input parameters:

- `accessKey` (string): Access key (lk_…) of a private mock you do not own
- `body`: JSON body for POST, PUT, PATCH
- `headers` (object): Request headers, including x-loutre-*
- `method` (string, required)
- `ownerToken` (string): Owner token received at creation (not needed when the account is connected with an API token)
- `path` (string, required): Path with its query string: "/users/42?expand=orders"
- `slug` (string, required): Subdomain of the mock, e.g. "brisk-otter"

### `set_behavior` (~125 tokens)

Change a mock's behaviour: default status, latency, jitter, error rate, persistent writes, and per route status, latency, hand-written bodies, rules. Merge semantics: missing keys are kept, null clears.

Input parameters:

- `ownerToken` (string): Owner token received at creation (not needed when the account is connected with an API token)
- `patch` (object, required): Same fields as PATCH /mocks/:slug/behavior: a missing key is kept, null clears
- `slug` (string, required): Subdomain of the mock, e.g. "brisk-otter"

### `set_response` (~122 tokens)

Set the JSON body a route returns for a given status (hand-written response); a null body restores the generated response.

Input parameters:

- `body` (required): JSON body, or null to go back to the generated response
- `ownerToken` (string): Owner token received at creation (not needed when the account is connected with an API token)
- `route` (string, required): Route identifier, lowercase method: "get:/users/{id}"
- `slug` (string, required): Subdomain of the mock, e.g. "brisk-otter"
- `status` (integer, required)

### `add_rule` (~179 tokens)

Add a conditional response to a route: when the request matches the conditions (query, header, path param, body field), the mock answers with this status, body and latency. Rules are evaluated in order, the first match wins; x-loutre-* headers keep priority.

Input parameters:

- `body`: JSON body of the response
- `latencyMs` (number)
- `name` (string): Human-readable label of the rule
- `ownerToken` (string): Owner token received at creation (not needed when the account is connected with an API token)
- `route` (string, required): Route identifier, lowercase method: "get:/users/{id}"
- `slug` (string, required): Subdomain of the mock, e.g. "brisk-otter"
- `status` (integer)
- `when` (object, required): Every condition must hold

### `clear_rules` (~82 tokens)

Remove every conditional rule of a route.

Input parameters:

- `ownerToken` (string): Owner token received at creation (not needed when the account is connected with an API token)
- `route` (string, required): Route identifier, lowercase method: "get:/users/{id}"
- `slug` (string, required): Subdomain of the mock, e.g. "brisk-otter"

### `regenerate_mock` (~130 tokens)

Generate a new data set (new seed), for the whole mock or for one route and the routes sharing its collection. A full new set forgets persisted writes.

Input parameters:

- `locale` (string): Switch the data language (whole mock only)
- `ownerToken` (string): Owner token received at creation (not needed when the account is connected with an API token)
- `routeId` (string): Route identifier, lowercase method: "get:/users/{id}"
- `seed` (string)
- `slug` (string, required): Subdomain of the mock, e.g. "brisk-otter"

### `get_requests` (~112 tokens)

The latest requests received by the mock, most recent first: method, path, query, status, headers and body as received (body cut at 8 KB), where the answer came from, latency. Each entry has an id for replay_request.

Input parameters:

- `limit` (integer)
- `ownerToken` (string): Owner token received at creation (not needed when the account is connected with an API token)
- `slug` (string, required): Subdomain of the mock, e.g. "brisk-otter"

### `replay_request` (~113 tokens)

Replay a request from the log exactly as it was received (same method, path, headers and body) against the mock as it is now, and return the answer. Useful after changing a rule, a body or a scenario.

Input parameters:

- `id` (string, required): Entry id from get_requests
- `ownerToken` (string): Owner token received at creation (not needed when the account is connected with an API token)
- `slug` (string, required): Subdomain of the mock, e.g. "brisk-otter"

### `clear_requests` (~62 tokens)

Empty the mock's request log.

Input parameters:

- `ownerToken` (string): Owner token received at creation (not needed when the account is connected with an API token)
- `slug` (string, required): Subdomain of the mock, e.g. "brisk-otter"

### `sync_mock` (~102 tokens)

Re-read the schema at the mock's source URL now and update the mock if it changed (routes, fields; settings kept, persisted writes forgotten). force regenerates even when the document is unchanged.

Input parameters:

- `force` (boolean)
- `ownerToken` (string): Owner token received at creation (not needed when the account is connected with an API token)
- `slug` (string, required): Subdomain of the mock, e.g. "brisk-otter"

### `set_domain` (~127 tokens)

Serve the mock under the account's own hostname (Pro): declares it at Cloudflare and returns the CNAME to create (hostname → target) plus the current status; call again without hostname to re-check, or with hostname null to remove it.

Input parameters:

- `hostname`: e.g. mock.acme.com; null removes; omitted re-checks the status
- `ownerToken` (string): Owner token received at creation (not needed when the account is connected with an API token)
- `slug` (string, required): Subdomain of the mock, e.g. "brisk-otter"

### `reset_state` (~76 tokens)

Forget persisted writes (POST, PUT, PATCH, DELETE): the generated collections come back as they were.

Input parameters:

- `ownerToken` (string): Owner token received at creation (not needed when the account is connected with an API token)
- `slug` (string, required): Subdomain of the mock, e.g. "brisk-otter"

### `set_access` (~100 tokens)

Lock a mock with a token (private) and/or restrict the allowed browser origins. Pro plan.

Input parameters:

- `origins`: Allowed origins (https://app.example.com); null to allow all
- `ownerToken` (string): Owner token received at creation (not needed when the account is connected with an API token)
- `private` (boolean)
- `slug` (string, required): Subdomain of the mock, e.g. "brisk-otter"

### `delete_mock` (~65 tokens)

Permanently delete a mock and its kept schema.

Input parameters:

- `ownerToken` (string): Owner token received at creation (not needed when the account is connected with an API token)
- `slug` (string, required): Subdomain of the mock, e.g. "brisk-otter"

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/app-loutre-loutre/api#diagnostics

## Score history

- 2026-11-05: 56
- 2026-11-04: 55
- 2026-11-03: 55
- 2026-11-02: 54

## Common questions

### What is the Loutre MCP server?

Loutre is an MCP server listed in the public MCP registry as app.loutre/loutre. Hosted mock APIs from OpenAPI, TypeScript or Postman: realistic data, errors and latency on demand. This page covers its hosted endpoint (https://api.loutre.app/mcp).

### Is the Loutre MCP server safe to use?

Loutre scores 56 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 Loutre MCP server expose?

Loutre exposes 17 tools: create_mock, list_mocks, get_mock, call_mock, set_behavior, and 12 more. Their descriptions and schemas cost roughly 2,124 tokens of context every time the server is loaded.

### Does the Loutre MCP server require authentication?

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

### Is the Loutre MCP server still maintained?

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

## Links

- Remote endpoint: https://api.loutre.app/mcp
- Website: https://loutre.app/docs#mcp
- Changelog RSS feed: https://verifymcp.io/servers/app-loutre-loutre/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/app-loutre-loutre/api.json
- HTML version of this page: https://verifymcp.io/servers/app-loutre-loutre/api