mcpbeat Sign in

Opplevagent MCP Server

answering

Opplevagent MCP is answering right now. Last checked 8 min ago. 52 installs a week from npm. It exposes 5 tools. Last commit 8 Nov 2026.

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

Installs per day peak 11 · avg 5 · -9% w/w
a month agotoday
Uptime history 91 days of history · worst day 84%
91 days agonow
100.0%
Uptime 24h
91 of 91 checks
5
Tools
read from the server
156 ms
Response time
average over 24h
52
Installs / week
npm and PyPI

What changed 23

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 6 September 2026. No other catalogue keeps this.

6 Nov 5 tool descriptions were rewritten book_gardssalg, discover_experiences, discover_gardssalg and 2 more
12 Oct 2 tool descriptions were rewritten3 times that day discover_experiences, discover_gardssalg
12 Oct a tool changed the parameters it asks for discover_experiences
10 Oct a tool description was rewritten discover_experiences
10 Oct a tool changed the parameters it asks for discover_experiences
3 Oct 2 tools changed the parameters they ask for discover_experiences, discover_gardssalg
3 Oct a tool description was rewritten discover_experiences
25 Sep a tool changed the parameters it asks for discover_experiences
18 Sep a tool description was rewritten discover_gardssalg
18 Sep a tool changed the parameters it asks for discover_gardssalg
and 7 more, back to 6 September 2026

What the code does

We read the source, 8 h ago · tools taken from the live server · rules 995398eba69f

Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

Package points at a different repository slookisen/lokal
пакет opplevagent-mcp ссылается на slookisen/opplevagent-mcp
In the project's build, not in the package

Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.

…if(this._events&&(n=this._events[t]))if(1===arguments.length){if(this._firingCount)for(o=0,s=n.length;o<s;o++)n[o].fn=u;delete this._events[t]}else"function"!=typeof e?console.warn("wrong listener type: "+typeof e):!1!==(e=this._listens(t,e,i))&&(i=n[e],this._firingCount&&(i.fn=u…
  const out = execFileSync(
  await page.screenshot({ path: path.join(DIR, name), fullPage: true });

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

This code can reach further than it looks

We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 8 min ago.

run in your terminal
claude mcp add opplevagent-mcp --transport http https://opplevagent.no/mcp
Settings → Connectors → Add custom connector, then paste this address
https://opplevagent.no/mcp
~/.codex/config.toml
[mcp_servers.opplevagent-mcp]
url = "https://opplevagent.no/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "opplevagent-mcp": {
      "url": "https://opplevagent.no/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "opplevagent-mcp": {
      "type": "http",
      "url": "https://opplevagent.no/mcp"
    }
  }
}

Available tools 5

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

discover
discover_experiences
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'.
discover_gardssalg
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'.
experience
get_experience
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'.
list_experience_categories
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?'.
book
book_gardssalg
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 '[email protected]'.

Endpoints

URLTransportStateLatencyChecked
https://opplevagent.no/mcp streamable-http answering 132 ms 8 min ago

Alternatives to Opplevagent MCP

same job, measured the same way
Thailand Fun Experiences
by thailandfunexperiences

Phuket activity search with live weather, sea state, transfer times and party-fit filtering.

2 tools answering
Mu
by micro

News, web search, mail, markets, weather, places, files, calendar, contacts. 67 tools, one endpoint.

173 tools answering
Nephyr Weather
by clm-studios

GFS ensemble weather signals for prediction market edge detection across 12 cities

59 installs/wk local only
dumaguete.uk places
by dumaguete

Dumaguete City places: name, category, coordinates, OSM reference. Nearby search by coordinate.

5 tools answering
Prediction Market Rule Check MCP
by donniertf-hub

Risk-scores Polymarket/Kalshi settlement rules; Kalshi weather settlements. Not advice.

12 tools answering
Arc Research
by getarcresearch

Commodities research MCP: knowledge graph, COT, NG storage/weather, quotes, and stories.

answering
Kartverket MCP
by 3121n

Norwegian address geocoding, places, properties, buildings & elevation from Kartverket.

49 installs/wk local only
Noaa Swpc
by pipeworx-io

NOAA SWPC MCP — space weather.

323 installs/wk 51 tools answering

Opplevagent MCP — questions

Answers built from our own checks of this server.

What can Opplevagent MCP do?
It exposes 5 tools, read directly from the server on our last check. Among them: book_gardssalg, discover_experiences, discover_gardssalg, get_experience, list_experience_categories. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
What is Opplevagent MCP mostly used for?
Its tools cluster around experience and discover. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is Opplevagent MCP working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 156 ms. The bar chart above shows every period we have measured.
How do I connect Opplevagent MCP?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Opplevagent MCP need an API key?
No. Opplevagent MCP completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 5 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Opplevagent MCP?
It answers our handshake in 156 ms on average, which is faster than 81% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.
How many people use Opplevagent MCP?
The npm package opplevagent-mcp was installed 52 times in the last week. Week over week that is -9%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is Opplevagent MCP open source?
The code is open source: it is published under the MIT licence, written in TypeScript and 2 stars on GitHub. The licence covers the code in the repository, not the hosted service at opplevagent.no, which runs on its operator's own terms.