prisjakten-public
Registry code: 5640de21e06477bf
Prisjakten.no sammenligner registrerte priser fra norske nettbutikker. Bruk sok_produkter først for å finne riktig modell og variant; be om presisering ved flere mulige treff. Svar med produktnavn, NOK, tilgjengelige datoer og kildelenker. Hentet-dato er ikke datoen prisen sist ble sjekket. Pris og lagerstatus kan endres; frakt er ikke inkludert i vareprisen. Historiske lavpriser gjelder bare vår registrerte historikk. Denne tilkoblingen har bare offentlige leseverktøy, uten konto, ønskeliste, prisvarsler, kjøp eller betaling.
- endpoint
- https://mcp.prisjakten.no/mcp
- protocol
- http-sse ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is prisjakten-public live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 99% of checks over the last 30 days.
- Is prisjakten-public free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does prisjakten-public have?
- 4 tools: sjekk_pris, prishistorikk, sok_produkter, storste_prisfall.
- Is prisjakten-public safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 99.1%· all time 99.1%
last good check
of 4 tools
- degraded → live
- live → degraded· HTTP 530
- degraded → live
- unknown → live
- used for
- search norwegian product prices
- check store prices for a product
- get product price history
- list biggest price drops
- takes → gives
- text → data
- tools
- 4 reads
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
storste_prisfall reads open 10h ago
De største registrerte prisfallene i norske nettbutikker, målt i kroner spart mot forrige pris.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "properties": { "antall": { "type": "integer", "default": 5, "maximum": 10, "minimum": 1, "description": "Antall prisfall" } } }arguments 13 linessjekk_pris reads unknown 1h ago
Registrerte butikkpriser for ett produkt, frakt når oppgitt, sist sjekket og sammenligning med registrert prishistorikk. Inkluderer kjøpsråd basert på prishistorikk.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "produkt" ], "properties": { "produkt": { "type": "string", "maxLength": 200, "minLength": 2, "description": "Produktnavn eller merke + modell" } } }arguments 15 linesprishistorikk reads unknown 10h ago
Laveste og gjennomsnittlige pris siste 90 dager, 6 måneder og 12 måneder for ett produkt. Bruk dette når brukeren spør om prisen er god, om de bør vente, eller om et tilbud er ekte.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "produkt" ], "properties": { "produkt": { "type": "string", "maxLength": 200, "minLength": 2, "description": "Produktnavn eller merke + modell" } } }arguments 15 linessok_produkter reads unknown 10h ago
Søk i katalogen hos prisjakten.no. Vis registrerte varepriser og antall butikker. Bruk dette først for å finne riktig modell. Søketidspunktet er ikke tidspunktet prisene sist ble sjekket. Bruk sjekk_pris for frakt og kontrolltidspunkt.
{ "type": "object", "$schema": "https://json-schema.org/draft/2020-12/schema", "required": [ "sporring" ], "properties": { "antall": { "type": "integer", "default": 5, "maximum": 10, "minimum": 1, "description": "Antall treff" }, "sporring": { "type": "string", "maxLength": 200, "minLength": 2, "description": "Produktnavn, gjerne merke + modell" } } }arguments 22 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id5640de21e06477bf.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/5640de21e06477bf/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/5640de21e06477bf?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.