Loutre MCP server
app.loutre/loutreloutre.appstreamable-httpv1.0.0Scanned
Hosted mock APIs from OpenAPI, TypeScript or Postman: realistic data, errors and latency on demand.
17 tools: 2 can delete or cancel things, 12 change things and 3 only read.
- Reads private data · 0
- Reads text others write · 1
- Can send data out · 1
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
2 tools here can delete or cancel things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Loutre MCP server can do
The Loutre MCP server is published by loutre.app, a domain the MCP Registry verified. It has 17 tools. It can delete or cancel things (2 tools: clear_rules and delete_mock) and create or change data (12 tools: create_mock, call_mock, set_behavior, set_response and 8 more). 3 tools only read.
1 tool brings in text other people can write (list_mocks); 1 tool can send data out of your system (create_mock).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 15, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
17 tools
Deletes or cancels 2Claude Code: deny
clear_rulesRemove every conditional rule of a route.No findings
Why it is in this group
- The description's first verb is "remove": a word for removing or ending something.
Description, as the server wrote it Remove every conditional rule of a route.
delete_mockPermanently delete a mock and its kept schema.No findings
Why it is in this group
- The name "delete_mock" says "delete": a word for removing or ending something.
- The description says "Permanently delete".
Description, as the server wrote it Permanently delete a mock and its kept schema.
Changes things 12Claude Code: ask
add_ruleAdd 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.No findings
Why it is in this group
- The name "add_rule" says "add": a word for a change.
Description, as the server wrote it 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.
call_mockCall a route of the mock like an HTTP client would and return the status, the x-loutre-* headers and the body.No findings
Why it is in this group
- The name "call_mock" says "call": a word for a change.
Description, as the server wrote it 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.
clear_requestsEmpty the mock's request log.No findings
Why it is in this group
- The name "clear_requests" says "request": a word for a change.
Description, as the server wrote it Empty the mock's request log.
create_mockCreate 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…Can send data outNo findings
Why it is in this group
- The name "create_mock" says "create": a word for a change.
What it can reach
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Description, as the server wrote it 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.
regenerate_mockGenerate a new data set (new seed), for the whole mock or for one route and the routes sharing its collection.No findings
Why it is in this group
- The description's first verb is "generate": a word for a change.
Description, as the server wrote it 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.
replay_requestReplay 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.No findings
Why it is in this group
- The name "replay_request" says "request": a word for a change.
Description, as the server wrote it 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.
reset_stateForget persisted writes (POST, PUT, PATCH, DELETE): the generated collections come back as they were.No findings
Why it is in this group
- The name "reset_state" says "reset": a word for a change.
Description, as the server wrote it Forget persisted writes (POST, PUT, PATCH, DELETE): the generated collections come back as they were.
set_accessLock a mock with a token (private) and/or restrict the allowed browser origins.No findings
Why it is in this group
- The name "set_access" says "set": a word for a change.
Description, as the server wrote it Lock a mock with a token (private) and/or restrict the allowed browser origins. Pro plan.
set_behaviorChange a mock's behaviour: default status, latency, jitter, error rate, persistent writes, and per route status, latency, hand-written bodies, rules.No findings
Why it is in this group
- The name "set_behavior" says "set": a word for a change.
Description, as the server wrote it 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.
set_domainServe 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 hos…No findings
Why it is in this group
- The name "set_domain" says "set": a word for a change.
Description, as the server wrote it 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.
set_responseSet the JSON body a route returns for a given status (hand-written response); a null body restores the generated response.No findings
Why it is in this group
- The name "set_response" says "set": a word for a change.
Description, as the server wrote it Set the JSON body a route returns for a given status (hand-written response); a null body restores the generated response.
sync_mockRe-read the schema at the mock's source URL now and update the mock if it changed (routes, fields; settings kept, persisted writes forgotten).No findings
Why it is in this group
- The name "sync_mock" says "sync": a word for a change.
Description, as the server wrote it 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.
Only reads 3Show 3 read-only tools
get_mockDetails of a mock: routes with identifiers, behaviour, lock, sample generated bodies per route.No findings
Why it is in this group
- The name "get_mock" says "get": a word for reading.
Description, as the server wrote it Details of a mock: routes with identifiers, behaviour, lock, sample generated bodies per route.
get_requestsThe 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.No findings
Why it is in this group
- The name "get_requests" says "get": a word for reading.
Description, as the server wrote it 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.
list_mocksList the connected account's mocks (API token required), with their URL, routes and expiry.Reads text others writeNo findings
Why it is in this group
- The name "list_mocks" says "list": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "list" and "url": it reads web pages, which anyone can write.
Description, as the server wrote it List the connected account's mocks (API token required), with their URL, routes and expiry.
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 17, 2026, 15:22 UTC, unchanged since Nov 3, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 14
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 14 tools that change things (2 destructive, 12 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://api.loutre.app/mcp: tools/list returned 17 tools to an anonymous client, including clear_rules (destructive), delete_mock (destructive), create_mock (write), call_mock (write), set_behavior (write) and 9 more
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools2 changed.~2 changedView diff
- Changed:create_mockChanges thingsinputSchema
- Changed:regenerate_mockChanges thingsinputSchema
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http loutre https://api.loutre.app/mcpclaude mcp add --transport http loutre https://api.loutre.app/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__loutre__list_mocks",
"mcp__loutre__get_mock",
"mcp__loutre__get_requests"
],
"ask": [
"mcp__loutre__create_mock",
"mcp__loutre__call_mock",
"mcp__loutre__set_behavior",
"mcp__loutre__set_response",
"mcp__loutre__add_rule",
"mcp__loutre__regenerate_mock",
"mcp__loutre__replay_request",
"mcp__loutre__clear_requests",
"mcp__loutre__sync_mock",
"mcp__loutre__set_domain",
"mcp__loutre__reset_state",
"mcp__loutre__set_access"
],
"deny": [
"mcp__loutre__clear_rules",
"mcp__loutre__delete_mock"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as loutre. Review it before you use it.
Capability tags behind 2 rules
- mcp__loutre__create_mock outbound
- mcp__loutre__list_mocks untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/app.loutre/loutre/verify?hash=1e03aabd0d87fa6c492381deae3884c307e0b2f664e519b7caa90e55421889e2" | jq -e '.changed == false'Pinned hash 1e03aabd0d87, from Nov 15, 2026, 22:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/app.loutre/loutre/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/app.loutre/loutre)Source: MCP Registry. Synced Nov 2, 2026, 16:17 UTC.
Loutre MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Loutre MCP server safe?
- No scan can promise that. What its definitions show: 17 tools, 14 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Loutre MCP server delete data?
- Yes. 2 tools can delete, cancel or revoke something: clear_rules and delete_mock.
Can the Loutre MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Loutre MCP server have?
- 17 tools: 2 destructive, 12 write, 3 read. clear_rules, delete_mock, create_mock, call_mock, set_behavior, set_response, add_rule, regenerate_mock and 9 more.
Does the Loutre MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Loutre MCP server send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): create_mock.
Has the Loutre MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 15, 2026. Every change is on this page and in its Atom feed.