allemannsdata.com

AIS ship traffic MCP server. Live vessel positions and historical tracks in Norwegian waters from BarentsWatch's AIS APIs (live.ais.barentswatch.no + historic.ais.barentswatch.no), which relay the Norwegian Coastal Administration's AIS network. Needs a free AIS-client (note: a separate client type from the ordinary API-client, chosen when registering at barentswatch.no/minside); credentials read from BARENTSWATCH_AIS_CLIENT_ID / BARENTSWATCH_AIS_CLIENT_SECRET in .env, token scope "ais". Place names ("off Bergen", "Oslofjorden") are resolved and vessel positions described through Kartverket's open stedsnavn API, so tools accept coordinates or Norwegian place names interchangeably. The server does the distance/bearing math, Douglas-Peucker track reduction and stop detection, returning ranked lists and summaries instead of raw coordinate streams. Mounted by main.py at /ais/mcp

Arkivverket / Nasjonalarkivet (National Archives of Norway) MCP server. Historical archive data from two open, keyless sources: 1. Digitalarkivet's 1910 census API (api.digitalarkivet.no/v1/census/1910) - the transcribed 1910 census (folketelling 1910), ~2.4M people recorded on 1 December 1910. Full-text and fielded person search, residence/property search including geo-proximity, and by-id detail with full household / resident listings and every recorded census field (kjønn, sivilstand, yrke, fødselsår, fødested, statsborgerskap, trossamfunn, ...). 2. Arkivportalen (arkivportalen.no) - the national archive catalogue aggregating fonds/series/units across Norwegian archive institutions. Full-text catalogue search: which archive holds what, at which repository, with digitized-document counts. This is catalogue *metadata*, not transcribed records. Not wrapped, because no public read API resolves for them: church books (kirkebøker - only scanned image viewer pages exist, no JSON/IIIF endpoint), census years other than 1910, and general transcribed-source search. The other documented Digitalarkivet APIs (bevaringstjeneste) are ingest/ preservation only. Complements the kulturarv server (Riksantikvaren heritage sites + DigitaltMuseum objects), which covers cultural heritage rather than genealogy/archives. Mounted by main.py at /arkivverket/mcp

Artskart MCP server. Norwegian species occurrence data from Artsdatabanken's Artskart ("species map") public API (artskart.artsdatabanken.no/publicapi), the national map service for verified species observations. Public, no API key. Search taxa by Norwegian popular name or scientific name, look up taxonomic detail and child taxa, and query observation records by species, county/ municipality, status and date range. Coordinates in observation results are WGS84 (EPSG:4326). County/municipality filters accept only the standard Norwegian fylkesnummer/kommunenummer codes, not county/municipality names. Mounted by main.py at /artskart/mcp

Avinor flight data MCP server. Real-time arrivals and departures for Norwegian airports from Avinor's open XML feed (asrv.avinor.no, documented at partner.avinor.no). Public, no API key. Avinor's terms require the label "Flight data from Avinor" with a link to www.avinor.no when the data is displayed. get_flights() returns scheduled times and live status (gate, belt, delays, cancellations) for flights to/from one airport in a time window around now. It covers Avinor's 43 airports fully; querying a foreign airport returns only its flights to/from Norway. lookup_airport() and lookup_airline() translate the IATA codes in flight data to names (cached 24h, per Avinor's recommended refresh rate). Flight status codes are a fixed set of five, embedded here rather than fetched from the flightStatuses feed: N=New info, E=New time, D=Departed, A=Arrived, C=Cancelled. A flight without a status is running as scheduled. Mounted by main.py at /avinor/mcp

Badetemperaturer (Yr bathing temperatures) MCP server. Measured bathing water temperatures for Norwegian swimming spots (lakes, rivers, fjords and lidos), from Yr's badetemperatur API (badetemperaturer.yr.no). Registrations come from municipalities, bathing sites and other providers; the "latest" endpoints only return temperatures measured within the last five days, so coverage is high in summer and thin off-season. Three tools: - get_water_temperatures: latest registrations across Norway, filterable by spot name, county or municipality. - get_nearest_water_temperatures: the nearest registrations within 50 km of a coordinate. - get_water_temperature_history: the last five registrations for one spot. Needs an API key (request from support@yr.no, see https://hjelp.yr.no/hc/no/articles/5949243432850); read from BADETEMP_API_KEY in .env and sent as the "apikey" header. Data: Badetemperaturer levert av Yr. Yr's terms require this attribution to be shown wherever the temperatures are displayed; every tool returns it. Mounted by main.py at /badetemp/mcp