io.github.slookisen/opplevagent-mcp
REMOTE · OPPLEVAGENT.NO · 2 COMPONENTS
Norwegian experiences marketplace MCP: activities by county, category, weather, season, group size.
Available components
Last scanned (11 hours ago)
Scores higher than 84% of remote servers
Reachable. Last reached 5 Nov 2026.
Category E-commerce
Recent critical change
Authorization (26 Sept 2026). See the changelog before you install this server.
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (book_gardssalg). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
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 3561 tokens (~356/item across 10 items; 5 tools + 5 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 7 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
Checks we ran (14)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
- Capabilities
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 15 Oct 26 0
- Resource “experience-detail” now points somewhere else: ui://opplevagent/experience-detail-2026-10-12 → ui://opplevagent/experience-detail-2026-10-14 security
- New resource “experience-detail-adult-price” functional
- 13 Oct 26 0
- Resource “experience-detail” now points somewhere else: ui://opplevagent/experience-detail → ui://opplevagent/experience-detail-2026-10-12 security
- Resource “experiences-list” now points somewhere else: ui://opplevagent/experiences-list → ui://opplevagent/experiences-list-2026-10-12 security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “discover_gardssalg” rewrote its description, which is the text the model reads security
- Schema quality: 493 → 393 ▲ functional
- New resource “experience-detail-legacy” functional
- New resource “experiences-list-legacy” functional
- 12 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “discover_experiences” rewrote its description, which is the text the model reads security
- “discover_experiences” reworded the description of “query” cosmetic
- 10 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “discover_experiences” rewrote its description, which is the text the model reads security
- “discover_experiences” added an optional parameter “query” cosmetic
- 4 Oct 26 0
- Tool “discover_experiences” rewrote its description, which is the text the model reads security
- “discover_experiences” reworded the description of “category” cosmetic
- “discover_experiences” reworded the description of “season” cosmetic
- “discover_experiences” reworded the description of “weather” cosmetic
- “discover_gardssalg” reworded the description of “query” cosmetic
- 2 Oct 26 81
- Transport: fail → pass ▲ security
- 1 Oct 26 0
- Transport: pass → fail ▼ security
- 28 Sept 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
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 5 Nov 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=YE2,O=Let's Encrypt,C=US | 15 Oct 2026 | 13 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 6ec190f8a58228df756223a4ce136107143 |
| SANs: opplevagent.no | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| 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. | DS published | 38032 | 13 | Verified |
| opplevagent.no. | No DS | 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' https://challenges.cloudflare.com;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 https://challenges.cloudflare.com;frame-src https://challenges.cloudflare.com;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 |
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 →
book_gardssalg Request a gårdssalg booking (pending — email confirmation required) ~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…
| Name | Type | Req | Description |
|---|---|---|---|
| confirm_outside_hours | boolean | – | Set 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_id | string | – | Optional experience UUID if this booking is for a specific listed experience rather than a general gårdssalg visit. |
| guest_email | string | yes | Guest'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_name | string | yes | Full name of the person the reservation is for. Example: 'Kari Nordmann' |
| guest_phone | string | – | Optional guest phone number. |
| notes | string | – | Optional free-text note to the producer (e.g. dietary needs, arrival details). |
| party_size | number | yes | Number of people in the group (1-50). Example: 4 |
| provider_id | string | – | The 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_query | string | – | Alternative 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_weekday | string | – | Safety 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_at | string | yes | Requested 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 Discover Norwegian experiences ~1,097
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. 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'.
| Name | Type | Req | Description |
|---|---|---|---|
| age | integer | – | Age of the youngest participant. Filters out experiences with a minimum-age requirement above this. Example: 8 |
| category | string | – | Experience category slug — one of: 'kultur_historie' (culture/history, museums), 'natur_friluft' (nature/outdoors), 'adrenalin_action', 'sightseeing_transport' (sightseeing, cruises, cable cars), 'ov… |
| duration_max | integer | – | Maximum duration in minutes. Example: 120 (2 hours) |
| fylke | string | – | Norwegian county (fylke). Examples: 'Oslo', 'Vestland', 'Troms', 'Rogaland' |
| group_size | integer | – | Number of people in the group. Used to filter experiences by min/max group capacity. Example: 4 |
| indoor_outdoor | string | – | Indoor/outdoor preference. Examples: 'indoor', 'outdoor', 'both' |
| kommune | string | – | Norwegian municipality (kommune). Examples: 'Tromsø', 'Bergen', 'Stavanger' |
| language | string | – | Required language for the experience. Examples: 'no', 'en' |
| lat | number | – | Origin latitude for a near-me search (decimal degrees). Must be given together with lng. Example: 69.65 (Tromsø) |
| limit | number | – | Max results (default 20, max 50) |
| lng | number | – | Origin longitude for a near-me search (decimal degrees). Must be given together with lat. Example: 18.95 (Tromsø) |
| max_price | integer | – | Maximum price per person in Norwegian kroner (NOK). Example: 500 |
| query | string | – | The user's request in a few words, including any place they named — e.g. 'safari lodge in Kenya', 'northern lights in Tromsø'. Opplevagent only covers Norway: when this names a place outside Norway a… |
| radius_km | number | – | Max distance from lat/lng in kilometers. Only applies when lat/lng are given. Example: 50 |
| season | string | – | Season filter: 'summer', 'winter', 'spring' or 'autumn' (the Norwegian words sommer/vinter/vår/høst work too). Year-round experiences are always included. Use this (not category or weather) when the… |
| sort | string | – | 'distance' — sort results ascending by distance from lat/lng. Already the default whenever lat/lng are given; this makes the request explicit. |
| weather | string | – | Today's weather, not the season: 'rain'/'snow' prefers indoor + weather-independent experiences. Examples: 'rain', 'clear'. For 'in winter' use season instead. |
No output schema declared.
No examples provided.
discover_gardssalg Discover Norwegian farm-sale drink producers (gårdssalg) ~753
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, 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'.
| Name | Type | Req | Description |
|---|---|---|---|
| booking_live | boolean | – | When true, only return producers that currently accept direct bookings. Omit to include producers regardless of booking status. |
| fylke | string | – | Norwegian county (fylke) of the producer. Examples: 'Oslo', 'Vestland', 'Troms', 'Rogaland' |
| kommune | string | – | Norwegian municipality (kommune) of the producer. Examples: 'Tromsø', 'Bergen', 'Stavanger' |
| lat | number | – | Origin latitude for a near-me search (decimal degrees). Must be given together with lng. Example: 69.65 (Tromsø) |
| limit | number | – | Max results (default 20, max 50) |
| lng | number | – | Origin longitude for a near-me search (decimal degrees). Must be given together with lat. Example: 18.95 (Tromsø) |
| producer_type | string | – | Type 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'… |
| query | string | – | Free-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_km | number | – | Max distance from lat/lng in kilometers. Only applies when lat/lng are given. Example: 50 |
No output schema declared.
No examples provided.
get_experience Get full details for a Norwegian 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'.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | UUID of the experience to fetch. Example: 'a1b2c3d4-e5f6-7890-abcd-ef1234567890' |
No output schema declared.
No examples provided.
list_experience_categories List Norwegian 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.
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
claude mcp add --transport http slookisen-opplevagent-mcp 'https://opplevagent.no/mcp'
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 81 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 3,234 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 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the io.github.slookisen/opplevagent-mcp server?
VerifyMCP ran 14 checks on io.github.slookisen/opplevagent-mcp, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.