Leseorientert tilgang til norske politihendelser og aggregater fra Politiloggen. Endepunktet krever ingen autentisering og støtter ti verktøy over Streamable HTTP.
Hendelsesdata er read-only. MCP-serveren kan ikke endre, opprette eller slette politihendelser.
Transporten oppretter kortlivede sesjoner og rate-limit-tellere. Dette er driftsmetadata, ikke endringer i hendelsesdata.
Kilden er Politiloggen. Gjenbruk skjer under NLOD 2.0 med attribusjon til Politiet.
Politipuls er en uavhengig tjeneste og er ikke tilknyttet Politiet eller en nødetat.
Dette er ikke en nødkanal. Ring 112 ved akutt fare.
Bruk og personvern
Ingen innlogging eller Politipuls-konto er nødvendig. Send bare de eksplisitte parametrene verktøyet trenger, som kommune, kategori, tidsrom eller hendelses-ID. Hele samtalen er ikke nødvendig; ikke send samtalehistorikk eller sensitive personopplysninger.
Politipuls behandler tekniske sesjonsdata, pseudonymiserte rate-limit-tellere og aggregert bruksstatistikk. Se personvernerklæringenfor opplysninger om lagring og sletting. Dokumentert API- og MCP-bruk er tillatt innenfor bruksgrensene og vilkårene. AI-klientens behandling av samtalen følger klientleverandørens egne vilkår.
Koble til
Send JSON-RPC 2.0 til https://politipuls.no/api/mcp. Serveren svarer påinitialize med headeren MCP-Session-Id. Bruk samme header i resten av sesjonen. Send også den forhandlede protokollversjonen i MCP-Protocol-Version på etterfølgende kall. Eldre klienter uten denne headeren bruker versjonen som allerede er lagret i sesjonen; en annen verdi avvises.
Vanlige MCP-klienter kobler til fra en server eller lokal prosess og påvirkes ikke av nettleser-CORS. Nettleserkall støttes bare fra Politipuls sine egne origins og lokale Capacitor-origins. Avslutt en sesjon med DELETE, MCP-Session-Id ogContent-Type: application/json. Innholdstypen kreves også når DELETE-kallet ikke har en body, fordi Astro sin globale CSRF-port ellers avviser forespørselen før MCP-ruten.
Denne listen rendres fra det samme manifestet som brukes av tools/list og discovery-endepunktene.
list_incidents
List recent Politipuls incidents, including authoritative GeoJSON and separate display-anchor semantics when available, with optional district, category, municipality, and active-only filters. Municipality is the requested incident area; never request the user’s precise location. Preserve the clickable source attribution supplied with the result when presenting its data.
Fetch one Politipuls incident by id, including authoritative GeoJSON and separate display-anchor semantics when available. Preserve the clickable source attribution supplied with the result when presenting its data.
Fetch available districts, municipalities, and categories for Politipuls filtering. Preserve the clickable source attribution supplied with the result when presenting its data.
Count incidents grouped by category. Use this for category bar/pie charts. Returns rows ordered by count desc. Preserve the clickable source attribution supplied with the result when presenting its data.
Count incidents grouped by district. Use this for district leaderboards or maps. Returns rows ordered by count desc. Preserve the clickable source attribution supplied with the result when presenting its data.
Top N municipalities by incident count. Optional district filter. Use for ranking visualizations. Preserve the clickable source attribution supplied with the result when presenting its data.
Time-bucketed incident counts (daily, weekly, or monthly) from nightly pre-aggregated stats. Use for trend lines and time-series charts. For totals and averages, use the server-computed summary rather than summing buckets yourself. Label averagePerReturnedBucket as an average per returned day/week/month according to granularity, not per requested day; missing buckets are not zero-filled. Optional district/category filter. Time-series buckets are materialized nightly. Each query selects one canonical aggregation level so incidents are not double-counted. Later source edits, removals, and the currently open bucket can cause a small difference from live incident aggregates over nominally similar periods. Preserve the clickable source attribution supplied with the result when presenting its data.
List incidents with documented physical points within a geographic bounding box, including authoritative GeoJSON when available. Incidents represented only by a technical anchor or non-point geometry abstain rather than being treated as point hits. north/south are latitudes, east/west are longitudes. Bounds describe the requested incident area; never request the user’s GPS location or address. Preserve the clickable source attribution supplied with the result when presenting its data.
Month-over-month trend per (district, category) — current vs previous month with percent change. Use for trend dashboards. Preserve the clickable source attribution supplied with the result when presenting its data.
Politipuls is independent and is not an official police or emergency service.
Locations are derived from public incident text and may be approximate or absent.
Incidents can be delayed, corrected, deactivated, or removed by the source.
Time-series buckets are materialized nightly. Each query selects one canonical aggregation level so incidents are not double-counted. Later source edits, removals, and the currently open bucket can cause a small difference from live incident aggregates over nominally similar periods.
The endpoint does not support SSE or MCP resources and prompts.
Results reflect the latest successfully ingested Politiloggen snapshot; delays and later source edits can occur.