Skip to content

opplevagent-mcp server

io.github.slookisen/opplevagent-mcpslookisenstreamable-httpv0.4.0Scanned

Norwegian experiences marketplace MCP: activities by county, category, weather, season, group size.

5 tools: 1 can delete or cancel things, 1 change things and 3 only read.

Tools: 1 delete, 0 irreversible, 1 write, 3 read.
  • Reads private data · 0
  • Reads text others write · 1
  • Can send data out · 0
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here can delete or cancel things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

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 opplevagent-mcp server can do

The opplevagent-mcp server is published by the GitHub account slookisen. It has 5 tools. It can delete or cancel things (1 tool: book_gardssalg) and create or change data (1 tool: discover_gardssalg). 3 tools only read.

1 tool brings in text other people can write (book_gardssalg).

The fixed checks matched 1 finding (long-description). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 20, 2026, version 0.4.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.

5 tools

Deletes or cancels 1Claude Code: deny
  • book_gardssalgUse this to request a visit or tasting (besøk, smaking) at a Norwegian gårdssalg drink producer found with discover_gardssalg or named by the guest; it sends a visit request and do…Reads text others write1 finding

    Why it is in this group

    • The description's first verb is "request": a word for a change.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Info

      The description is 2,607 characters long, over the 2,000 this check looks for.

      Matched text

      description ends: "...fredag', party_size 4, guest_name 'Kari Nordmann', guest_email 'kari@example.no'."

      What this check looks for
    Description, as the server wrote it
    Use this to request a visit or tasting (besøk, smaking) at a Norwegian gårdssalg drink producer found with discover_gardssalg or named by the guest; it sends a visit request and does not sell or order products. Send inn en reservasjonsforespørsel for et gårdssalg-besøk. IMPORTANT: this NEVER creates a confirmed booking — it creates a PENDING request, exactly like the producer's own website form. The PRODUCER reviews the request and responds (confirms, proposes another time, or declines); guest_email only receives a read-only status link, never anything that can finalize the booking. No payment is involved (pickup/visit, pay on arrival, as today). Only producers with an active booking status (see discover_gardssalg's booking.live field) can be booked — a paused/not-yet-onboarded producer is rejected with a clear message, never a silent failure. VIKTIG: oppretter ALDRI en bekreftet booking — kun en avventende forespørsel; produsenten mottar forespørselen og svarer (bekrefter, foreslår nytt tidspunkt eller avslår). ONE-SENTENCE FLOW («book et møte hos X fredag 20. oktober kl. 10 for 4 personer»): call this ONCE with provider_query='X' (the producer's name — no discover_gardssalg round-trip needed), slot_at, party_size, guest_name, guest_email and requested_weekday='fredag'. The tool resolves X to exactly one producer (or returns candidates / not-found with NO booking created), checks that the date really is a Friday (or returns weekday_mismatch:true with the nearest Fridays, NO booking created), then submits the request and notifies the producer by email. guest_name and guest_email are the HUMAN guest's own — ask the guest for them if you do not have them; never invent or reuse someone else's. Required: provider_id OR provider_query, slot_at (requested date/time, 'YYYY-MM-DDTHH:MM' Europe/Oslo), party_size, guest_name, guest_email. Optional: requested_weekday, experience_id, guest_phone, notes, confirm_outside_hours. The requested slot_at is ALWAYS hard-rejected if it's in the past or too far ahead. If the producer has stated opening hours and slot_at falls outside them, this returns outside_hours:true (not an error) and creates no booking — retry once with confirm_outside_hours:true if the exact requested time should be kept anyway. On success the response carries the resolved producer (provider.navn) and slot_at_local (e.g. 'fredag 23. oktober 2026 kl. 10:00') — read both back to the guest. Example: provider_query 'Fjordgard Bryggeri', slot_at '2026-10-23T10:00', requested_weekday 'fredag', party_size 4, guest_name 'Kari Nordmann', guest_email 'kari@example.no'.

    Annotations the server declares

    • title: Request a gårdssalg booking
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: true
Changes things 1Claude Code: ask
  • discover_gardssalgUse this to plan a visit or tasting at a Norwegian drink producer (brewery, cidery, winery, distillery, meadery, farm café) and find ones that accept visit requests; it does not se…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Use this to plan a visit or tasting at a Norwegian drink producer (brewery, cidery, winery, distillery, meadery, farm café) and find ones that accept visit requests; it does not sell or order products. It searches opplevagent.no's gårdssalg (farm-sale) vertical of Brreg-registered drink producers to visit (besøk, smaking) (bryggeri/sideri/vingård/destilleri/mjøderi/gårdskafé/seltzeri). Finn norske gårdssalg-produsenter (drikkeprodusenter som selger direkte fra gården) etter fylke, kommune og produsenttype. / Filter by county (fylke), municipality (kommune), and producer type. Also supports near-me search via lat/lng (+ optional radius_km): when given, results include a rounded distance_km and are sorted nearest-first, and rows with no geocoded location are excluded (never a fabricated distance). Returns id (the provider_id for book_gardssalg), name, location, producer type, profile_url, and an honest booking status (live direct booking vs. a dark-launch 'coming soon' note — never overclaims booking availability). Include each returned producer's profile_url as a clickable link when available; when booking is paused, tell the user to contact the producer via that profile page. To look up ONE specific producer by name (e.g. when the guest says 'book hos Fjordgard Bryggeri'), pass `query`. Examples: 'gårdssalg i Vestland', 'cideri near lat 60.4 / lng 5.3', 'bryggeri med booking', query: 'Fjordgard Bryggeri'.

    Annotations the server declares

    • title: Discover gårdssalg producers
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 3Show 3 read-only tools
  • discover_experiencesSearch Opplevagent's published catalogue of experiences in Norway, including food and drink tastings and producer visits (smaking, besøk hos drikkeprodusenter).No findings

    Why it is in this group

    • The description's first verb is "search": a word for reading.
    Description, as the server wrote it
    Search Opplevagent's published catalogue of experiences in Norway, including food and drink tastings and producer visits (smaking, besøk hos drikkeprodusenter). Filtrer på fylke (county), kategori, vær, sesong, innendørs/utendørs, gruppestørrelse, pris og varighet. / Filter by county, category, weather, season, indoor/outdoor, group size, price, and duration. Also supports near-me search via lat/lng (+ optional radius_km): when given, results include a rounded distance_km and a geo_precision flag ('address' = exact, 'kommune' = approximate municipality centroid) and are sorted nearest-first. Returns title, category, location (fylke/kommune), description, and booking URL if available. Only verified experiences from active providers (Brreg-checked) are returned. Covers Norway only: pass the user's request in `query`; for a place outside Norway (e.g. Kenya) the tool returns no experiences, and the answer is that Opplevagent only covers Norway. Food-product shopping such as buying stockfish is outside this tool's scope. Pass that intent in query; an out_of_scope response must not be retried as a general discovery search. Examples: 'hva kan vi finne på i Troms om vinteren?' (fylke='Troms', season='winter'), 'wildlife experiences' (category='dyreliv_safari'), 'outdoor activities in Oslo for 4 people', 'experiences within 50km of lat 69.65 / lng 18.95'.

    Annotations the server declares

    • title: Discover Norwegian experiences
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_experienceFetch the full details of one experience in Opplevagent's catalogue, such as a tasting or a producer visit, by its UUID.No findings

    Why it is in this group

    • The name "get_experience" says "get": a word for reading.
    Description, as the server wrote it
    Fetch the full details of one experience in Opplevagent's catalogue, such as a tasting or a producer visit, by its UUID. Henter fullstendig informasjon om en opplevelse via UUID. Returns title, full description, category, location (fylke/kommune/meeting point), indoor/outdoor, season, weather suitability, group size limits, age suitability, price, duration, languages, booking URL, and booking type. Obtain the UUID from discover_experiences results. Example: id 'a1b2c3d4-e5f6-7890-abcd-ef1234567890'.

    Annotations the server declares

    • title: Get experience details
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_experience_categoriesList the experience categories in Opplevagent's catalogue for Norway, such as food and drink (mat og drikke), with the number of verified experiences in each category.No findings

    Why it is in this group

    • The name "list_experience_categories" says "list": a word for reading.
    Description, as the server wrote it
    List the experience categories in Opplevagent's catalogue for Norway, such as food and drink (mat og drikke), with the number of verified experiences in each category. Henter alle kategorier med antall verifiserte opplevelser. Use this to understand what kinds of experiences are available before calling discover_experiences with a specific category filter. Example question: 'hvilke typer opplevelser finnes i Norge?', 'what categories are available?'.

    Annotations the server declares

    • title: List experience categories
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

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 or outbound.

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 out0
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.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:11 UTC, unchanged since Nov 13, 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
2
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 2 tools that change things (1 destructive, 1 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://opplevagent.no/mcp: tools/list returned 5 tools to an anonymous client, including book_gardssalg (destructive), discover_gardssalg (write)

    What this check looks for

Posture changes

  1. Nov 13, 2026
    • Tools that change things, listed without credentials: 1 to 2

Findings

Matches of fixed checks, with the text they matched.

1 info
  • The description is 2,607 characters long, over the 2,000 this check looks for.

    Matched text

    description ends: "...fredag', party_size 4, guest_name 'Kari Nordmann', guest_email 'kari@example.no'."

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools5 changed.~5 changedView diff
  2. PostureRemote posture changed. Tools that change things, listed without credentials: 1 -> 2.View diff
    • Tools that change things, listed without credentials: 1 to 2

Install

Pinned to version 0.4.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http opplevagent https://opplevagent.no/mcp
claude mcp add --transport http opplevagent https://opplevagent.no/mcp

Run 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.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__opplevagent__discover_experiences",
      "mcp__opplevagent__list_experience_categories",
      "mcp__opplevagent__get_experience"
    ],
    "ask": [
      "mcp__opplevagent__discover_gardssalg"
    ],
    "deny": [
      "mcp__opplevagent__book_gardssalg"
    ]
  }
}

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 opplevagent. Review it before you use it.

Capability tags behind 1 rule
  • mcp__opplevagent__book_gardssalg 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/io.github.slookisen/opplevagent-mcp/verify?hash=d2d275331bf678108614047f80316932be0205a3a9d0f72800807951889a0765" | jq -e '.changed == false'

Pinned hash d2d275331bf6, from Nov 20, 2026, 13:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.slookisen/opplevagent-mcp/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.slookisen/opplevagent-mcp
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.slookisen/opplevagent-mcp.svg)](https://radar.anlyon.com/servers/io.github.slookisen/opplevagent-mcp)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:49 UTC.

opplevagent-mcp server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the opplevagent-mcp server safe?

No scan can promise that. What its definitions show: 5 tools, 2 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the opplevagent-mcp server delete data?

Yes. 1 tool can delete, cancel or revoke something: book_gardssalg.

Can the opplevagent-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 opplevagent-mcp server have?

5 tools: 1 destructive, 1 write, 3 read. book_gardssalg, discover_gardssalg, discover_experiences, list_experience_categories and get_experience.

Does the opplevagent-mcp server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the opplevagent-mcp server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the opplevagent-mcp server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 20, 2026. Every change is on this page and in its Atom feed.