Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.slookisen/opplevagent-mcp

NPM · OPPLEVAGENT-MCP · 2 COMPONENTS · SCANNED SEP 21

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

0 this week 68 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability63
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1821 tokens (~364/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability check failed: the tool surface changed between 0.1.0 and 0.2.0: 3 tool removals, 0 breaking changes, 5 additions. See how to fix → Fail
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the io.github.slookisen/opplevagent-mcp server?

io.github.slookisen/opplevagent-mcp runs locally as an npm package, launched with npx -y opplevagent-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · opplevagent-mcp

# add to Claude Code
claude mcp add slookisen-opplevagent-mcp -- npx -y opplevagent-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "slookisen-opplevagent-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "opplevagent-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "slookisen-opplevagent-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "opplevagent-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add slookisen-opplevagent-mcp -- npx -y opplevagent-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "slookisen-opplevagent-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "opplevagent-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add slookisen-opplevagent-mcp --command npx --arg -y --arg opplevagent-mcp
# ~/.hermes/config.yaml
mcp_servers:
  slookisen-opplevagent-mcp:
    command: "npx"
    args: ["-y", "opplevagent-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "slookisen-opplevagent-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "opplevagent-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add slookisen-opplevagent-mcp -t stdio -c npx -a -y opplevagent-mcp
// mcp.json
{
  "mcpServers": {
    "slookisen-opplevagent-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "opplevagent-mcp"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 3 Sept 26 −17
    • Stability: pass → unverified security
    • Tool safety: pass → unverified security
    • Stability: pass → fail security
    • Schema quality: 148 → 364 functional
    • Capabilities: pass → unverified functional
    • Tool coverage: 100 → unverified functional
    • Stability: pass → 0.80 functional
    • Package version: 0.1.0 → 0.2.0 functional
  • 2 Sept 26 0
    • Stability: 0.97 → pass security
  • 1 Sept 26 +1

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

  • 30 Aug 26 +1

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

  • 28 Aug 26 +1

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

  • 27 Aug 26 −3
    • Stability: pass → 0.80 functional
  • 26 Aug 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 26 0
    • Security disclosure: unverified → fail functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Sept 2026 · Analysed npm/opplevagent-mcp@0.2.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 96 packages
Packages resolved 96
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 5 exposed · ~1,821 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
book_gardssalg ~592

Submit a booking REQUEST for a Norwegian gårdssalg (farm-sale) producer discovered via discover_gardssalg. 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). Required: provider_id (from discover_gardssalg), slot_at (requested date/time), party_size, guest_name, guest_email. Optional: experience_id, guest_phone, notes. Example: book a table for 4 at provider '3f1b2c4d-...' for '2026-08-15T13:00' for 'Kari Nordmann' <kari@example.no>.

NameTypeReqDescription
experience_idstringOptional experience UUID if this booking is for a specific listed experience rather than a general gårdssalg visit.
guest_emailstringyesGuest's email address — REQUIRED. Receives a confirmation-of-request email plus a read-only status link; the booking stays pending until the PRODUCER responds (confirms, proposes another time, or dec…
guest_namestringyesFull name of the person the reservation is for. Example: 'Kari Nordmann'
guest_phonestringOptional guest phone number.
notesstringOptional free-text note to the producer (e.g. dietary needs, arrival details).
party_sizenumberyesNumber of people in the group (1-50). Example: 4
provider_idstringyesThe gårdssalg producer's id, from a discover_gardssalg result (NOT the profile slug). Example: '3f1b2c4d-...'
slot_atstringyesRequested visit date/time, local (Europe/Oslo), format 'YYYY-MM-DDTHH:MM'. Example: '2026-08-15T13:00'. This is a REQUEST — the producer may confirm, suggest another time, or decline.

No output schema declared.

No examples provided.

discover_experiences ~459

Search the opplevagent.no curated marketplace of Norwegian experiences and activities. 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. Returns title, category, location (fylke/kommune), description, and booking URL if available. Only verified experiences from active providers (Brreg-checked) are returned. Examples: 'hva kan vi finne på i Troms om vinteren?', 'outdoor activities in Oslo for 4 people'.

NameTypeReqDescription
ageintegerAge of the youngest participant. Filters out experiences with a minimum-age requirement above this. Example: 8
categorystringExperience category slug. Examples: 'natur_friluft', 'dyreliv_safari', 'mat_drikke', 'vinter'
duration_maxintegerMaximum duration in minutes. Example: 120 (2 hours)
fylkestringNorwegian county (fylke). Examples: 'Oslo', 'Vestland', 'Troms', 'Rogaland'
group_sizeintegerNumber of people in the group. Used to filter experiences by min/max group capacity. Example: 4
indoor_outdoorstringIndoor/outdoor preference. Examples: 'indoor', 'outdoor', 'both'
kommunestringNorwegian municipality (kommune). Examples: 'Tromsø', 'Bergen', 'Stavanger'
languagestringRequired language for the experience. Examples: 'no', 'en'
limitnumberMax results (default 20, max 50)
max_priceintegerMaximum price per person in Norwegian kroner (NOK). Example: 500
seasonstringSeason filter. Examples: 'summer', 'winter', 'spring', 'autumn'
weatherstringWeather suitability filter. 'rain'/'snow' prefers indoor + weather-independent experiences. Examples: 'rain', 'clear'

No output schema declared.

No examples provided.

discover_gardssalg ~512

Search opplevagent.no's gårdssalg (farm-sale) vertical — Brreg-registered Norwegian drink producers (bryggeri/cideri/vingård/destilleri/mjøderi/seltzeri) selling directly from the farm. 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 name, location, producer type, and an honest booking status (live direct booking vs. a dark-launch 'coming soon' note — never overclaims booking availability). Examples: 'gårdssalg i Vestland', 'cideri near lat 60.4 / lng 5.3', 'bryggeri med booking'.

NameTypeReqDescription
booking_livebooleanWhen true, only return producers that currently accept direct bookings. Omit to include producers regardless of booking status.
fylkestringNorwegian county (fylke) of the producer. Examples: 'Oslo', 'Vestland', 'Troms', 'Rogaland'
kommunestringNorwegian municipality (kommune) of the producer. Examples: 'Tromsø', 'Bergen', 'Stavanger'
latnumberOrigin latitude for a near-me search (decimal degrees). Must be given together with lng. Example: 69.65 (Tromsø)
limitnumberMax results (default 20, max 50)
lngnumberOrigin longitude for a near-me search (decimal degrees). Must be given together with lat. Example: 18.95 (Tromsø)
producer_typestringType of drink producer. Examples: 'bryggeri' (brewery), 'cideri' (cidery), 'vingård' (vineyard), 'destilleri' (distillery), 'mjøderi' (meadery), 'seltzeri'
radius_kmnumberMax distance from lat/lng in kilometers. Only applies when lat/lng are given. Example: 50

No output schema declared.

No examples provided.

get_experience ~166

Fetch complete details for a single experience from opplevagent.no 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'.

NameTypeReqDescription
idstringyesUUID of the experience to fetch. Example: 'a1b2c3d4-e5f6-7890-abcd-ef1234567890'

No output schema declared.

No examples provided.

list_experience_categories ~92

List all experience categories available on opplevagent.no, along 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?'.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Common questions

What is the io.github.slookisen/opplevagent-mcp server?

io.github.slookisen/opplevagent-mcp is listed in the public MCP registry as io.github.slookisen/opplevagent-mcp. Norwegian experiences marketplace MCP: activities by county, category, weather, season, group size. This page covers its npm package (opplevagent-mcp).

Is the io.github.slookisen/opplevagent-mcp server safe to use?

io.github.slookisen/opplevagent-mcp scores 68 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. It declares no install or post-install scripts. 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 io.github.slookisen/opplevagent-mcp server expose?

io.github.slookisen/opplevagent-mcp exposes 5 tools: discover_experiences, list_experience_categories, get_experience, discover_gardssalg, book_gardssalg. Their descriptions and schemas cost roughly 1,821 tokens of context every time the server is loaded.

Is the io.github.slookisen/opplevagent-mcp server still maintained?

io.github.slookisen/opplevagent-mcp is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.slookisen/opplevagent-mcp server under?

io.github.slookisen/opplevagent-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.