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

REMOTE · OPPLEVAGENT.NO · 2 COMPONENTS · SCANNED SEP 21

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

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

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. How we score → Why this is hard to score →

Endpoint Security80
Transport & Reachability100
Schema Quality & AI Usability75
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 2810 tokens (~401/item across 7 items; 5 tools + 2 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
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 6 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
  • Supports UI / widget rendering.Pass
Install

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

io.github.slookisen/opplevagent-mcp is a hosted endpoint at https://opplevagent.no/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.

remote · opplevagent.no

# add to Claude Code
claude mcp add --transport http slookisen-opplevagent-mcp 'https://opplevagent.no/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "slookisen-opplevagent-mcp": {
      "url": "https://opplevagent.no/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "slookisen-opplevagent-mcp": {
      "type": "http",
      "url": "https://opplevagent.no/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.slookisen-opplevagent-mcp]
url = "https://opplevagent.no/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "slookisen-opplevagent-mcp": {
      "type": "remote",
      "url": "https://opplevagent.no/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add slookisen-opplevagent-mcp --url 'https://opplevagent.no/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  slookisen-opplevagent-mcp:
    url: "https://opplevagent.no/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "slookisen-opplevagent-mcp": {
      "Transport": "http",
      "Url": "https://opplevagent.no/mcp"
    }
  }
}
# add to Vellum
assistant mcp add slookisen-opplevagent-mcp -t streamable-http -u 'https://opplevagent.no/mcp'
// mcp.json
{
  "mcpServers": {
    "slookisen-opplevagent-mcp": {
      "type": "http",
      "url": "https://opplevagent.no/mcp"
    }
  }
}

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

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.

  • 19 Sept 26 +1
    • Tool “discover_gardssalg” rewrote its description, which is the text the model reads security
    • “discover_gardssalg” reworded the description of “producer_type” cosmetic
  • 17 Sept 26 −1
    • Tool “book_gardssalg” rewrote its description, which is the text the model reads security
    • Tool “discover_gardssalg” rewrote its description, which is the text the model reads security
    • Schema quality: 318 → 397 functional
    • “book_gardssalg” added an optional parameter “provider_query” cosmetic
    • “book_gardssalg” added an optional parameter “requested_weekday” cosmetic
    • “discover_gardssalg” added an optional parameter “query” cosmetic
    • “book_gardssalg” reworded the description of “provider_id” cosmetic
    • “book_gardssalg” made “provider_id” optional cosmetic
  • 7 Sept 26 0
    • Tool “book_gardssalg” rewrote its description, which is the text the model reads security
    • “book_gardssalg” added an optional parameter “confirm_outside_hours” cosmetic
  • 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
    • Stability: 0.97 → pass security
  • 24 Aug 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.

  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 31 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → 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 · Probed https://opplevagent.no/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=opplevagent.no CN=YE1,O=Let's Encrypt,C=US 16 Aug 2026 14 Nov 2026 ECDSA 256 ECDSA-SHA384 6a254d859b3f682c4107e9b7c2548b9de1b
SANs: opplevagent.no
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of opplevagent.no. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
no. present 38032 13 Verified
opplevagent.no. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains
content-security-policy default-src 'self';script-src 'self' 'unsafe-inline';style-src 'self' 'unsafe-inline' https://fonts.googleapis.com;font-src 'self' https://fonts.gstatic.com;img-src 'self' data: https:;connect-src 'self' https://rettfrabonden.com;frame-src 'none';object-src 'none';base-uri 'self';form-action 'self';frame-ancestors 'self';script-src-attr 'none';upgrade-insecure-requests
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy no-referrer

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://opplevagent.no/mcp Verified 200
http (plaintext) http://opplevagent.no/mcp HTTPS enforced 301 https://opplevagent.no/mcp
MCP tools · 5 exposed · ~2,739 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 ~1,126

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). 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…

NameTypeReqDescription
confirm_outside_hoursbooleanSet to true only when RETRYING after a previous call to this tool returned outside_hours:true and the requested time should be kept anyway, despite falling outside the producer's stated opening hours…
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_idstringThe gårdssalg producer's id — the `id` field of a discover_gardssalg result (NOT the profile slug). Example: '3f1b2c4d-...'. Either provider_id or provider_query is required; provider_id wins when bo…
provider_querystringAlternative to provider_id: the producer's name as the guest said it, optionally with a place, e.g. 'Fjordgard Bryggeri' or 'Egge gård Steinkjer'. Resolved to exactly ONE producer; if several match,…
requested_weekdaystringSafety check — the weekday the guest actually said, e.g. 'fredag' or 'Friday'. If slot_at does not fall on that weekday (Europe/Oslo) the tool returns weekday_mismatch:true with the nearest dates tha…
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 ~667

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. 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. Examples: 'hva kan vi finne på i Troms om vinteren?', 'outdoor activities in Oslo for 4 people', 'experiences within 50km of lat 69.65 / lng 18.95'.

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'
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ø)
max_priceintegerMaximum price per person in Norwegian kroner (NOK). Example: 500
radius_kmnumberMax distance from lat/lng in kilometers. Only applies when lat/lng are given. Example: 50
seasonstringSeason filter. Examples: 'summer', 'winter', 'spring', 'autumn'
sortstring'distance' — sort results ascending by distance from lat/lng. Already the default whenever lat/lng are given; this makes the request explicit.
weatherstringWeather suitability filter. 'rain'/'snow' prefers indoor + weather-independent experiences. Examples: 'rain', 'clear'

No output schema declared.

No examples provided.

discover_gardssalg ~688

Search opplevagent.no's gårdssalg (farm-sale) vertical — Brreg-registered Norwegian drink producers (bryggeri/cideri/vingård/destilleri/gårdskafé/mjød/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 id (the provider_id for book_gardssalg), name, location, producer type, and an honest booking status (live direct booking vs. a dark-launch 'coming soon' note — never overclaims booking availability). 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'.

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 — one of the six canonical drink venue kinds: 'bryggeri' (brewery), 'cideri' (cidery), 'vingård' (winery), 'destilleri' (distillery), 'gårdskafé' (farm café), 'mjød'/'mjøderi'…
querystringFree-text lookup of a specific producer by name and/or place, e.g. 'Fjordgard Bryggeri', 'Egge gård', 'sideri Hardanger'. Every word must match the producer's name, URL slug, place (poststed) or muni…
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 hosted endpoint (https://opplevagent.no/mcp).

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

io.github.slookisen/opplevagent-mcp scores 88 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 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 2,739 tokens of context every time the server is loaded.

Does the io.github.slookisen/opplevagent-mcp server require authentication?

No. We connected to io.github.slookisen/opplevagent-mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

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.