Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Revly

REMOTE · REVLY.NO

Revly kobler assistenter til revisjonsarbeid med firmastyrt tilgang og personlig samtykke.

Available components

75 Trust /100

Last scanned (7 hours ago)

Scores higher than 64% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Finance and Payments

Trust breakdown (7 categories)

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 Security80
Transport & Reachability100
Schema Quality & AI Usability77
  • 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 2472 tokens (~206/item across 12 items; 12 tools + 0 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 Management10
  • Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Changelog

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.

  • 4 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 3 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Stability: unverified → 0.03 ▲ functional
  • 2 Nov 26 74

    First indexed and scored.

Diagnostics

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://revly.no/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.revly.no CN=YR1,O=Let's Encrypt,C=US 26 Oct 2026 24 Jan 2027 RSA 2048 SHA256-RSA 693e1c870deec78e595a0ed06a1aea9ec14
SANs: *.revly.no, revly.no
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of revly.no. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
no. present 38032 13 Verified
revly.no. absent 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=63072000; includeSubDomains; preload
content-security-policy default-src 'self'; script-src 'self' 'unsafe-inline' 'wasm-unsafe-eval' https://va.vercel-scripts.com https://vercel.live; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; img-src 'self' data: blob: https:; font-src 'self' data: https://fonts.gstatic.com; connect-src 'self' https://*.supabase.co wss://*.supabase.co https://api.anthropic.com https://vitals.vercel-insights.com https://*.vercel-scripts.com; frame-ancestors 'none'; frame-src 'self' blob:; form-action 'self'; base-uri 'self'; object-src 'none'
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=(), interest-cohort=(), payment=(), tools=(self)

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://revly.no/mcp Verified 200
http (plaintext) http://revly.no/mcp HTTPS enforced 308 https://revly.no/mcp
MCP tools · 12 exposed · ~1,823 tokens

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 →

Tool Tokens
finn_oppdrag ~158

Søker etter klientnavn, organisasjonsnummer eller år i firmaet tilkoblingen gjelder. Uten søkeord listes firmaets aktive oppdrag. Hvert treff viser hvor mange forespørsler som venter på klienten og siden når, og lovfristene Revly utleder for revisjonsoppdrag. En frist uten grunnlag står som ukjent, aldri som en gjettet dato. Gir høyst åtte treff.

NameTypeReqDescription
grenseinteger–Maksimalt antall treff, fra 1 til 8.
sokstring–Klientnavn, organisasjonsnummer eller fire-sifret oppdragsår. Utelat for å liste aktive oppdrag.
NameTypeReqDescription
limitnumber|null–Maximum number of matches requested, from 1 to 8.
matches––Matching engagements, newest year first.
operation_idstringyesRevly operation ID for this read, recorded in the access log.
result_countnumber|null–Number of matches returned.
statusstringyesmatches, no_matches or truncated when more rows exist than the limit.
truncatedboolean|null–True when more matches exist than the limit.

No examples provided.

hent_avslutningsstatus ~207

Henter status for avslutningen av én eksplisitt oppdrags-ID: for hvert av de seks avslutningsstegene om det er markert utført og når, og for hvert dokumentasjonsfelt om det finnes tekst og hvor lang den er. I tillegg antall etterfølgende hendelser per status, hvor mange punkter i årsoppgjørssjekklisten som er tatt stilling til, arkiveringsstatus, og om fortsatt drift og analysekonklusjonen er vurdert. Teksten, konklusjonene og hvem som har markert er utelatt. Summen av ukorrigerte feil mot vesentlighet er ikke med. Manglende dokumentasjon betyr «ikke dokumentert», aldri «i orden». Dette er ikke en faglig godkjenning.

NameTypeReqDescription
oppdrag_idstringyesEksplisitt oppdrags-ID fra Revly. Oppslag uten ID er ikke tillatt.
NameTypeReqDescription
aarnumber|null–Engagement year.
analysekonklusjon_vurdertboolean|null–Whether the closing analytical conclusion is recorded. The conclusion is not returned.
antall_markert_utfortnumber|null–Steps marked done.
antall_stegnumber|null–Number of closing steps.
arkivering_statusstring|null–Archive status code, or null when not archived.
avsluttende_vurdering_finnesboolean|null–False when no closing record exists yet; then every step is «ikke dokumentert».
etterfolgende_hendelser–––
fortsatt_drift_vurdertboolean|null–Whether the going-concern assessment is recorded as done. The conclusion is not returned; null when unknown.
isa450–––
missing_sources––Sources with no record. Missing data stays visible and is never treated as a positive result.
operation_idstringyesRevly operation ID for this read, recorded in the access log.
oppdrag_idstring|null–Engagement ID, as text.
revly_urlstring|null–Link to the closing page in Revly.
sjekkliste–––
statusstringyesavailable for a visible engagement.
steg––The closing steps in working order.
truncatedboolean|null––

No examples provided.

hent_forespoersler ~148

Henter opptil 80 forespørsler til klienten på én eksplisitt oppdrags-ID: område, kategori, tilstand, sendt dato, svarfrist, svardato, antall purringer og om revisor har vurdert svaret. Tittel, beskrivelse, svartekst og mottaker er utelatt. Interne forespørsler er ikke med. «Ikke vurdert» betyr at ingen vurdering er registrert, ikke at svaret er tilstrekkelig.

NameTypeReqDescription
oppdrag_idstringyesEksplisitt oppdrags-ID fra Revly. Oppslag uten ID er ikke tillatt.
NameTypeReqDescription
aarnumber|null–Engagement year.
antallnumber|null–Number of client requests on the engagement, internal requests excluded.
evidence–––
forespoersler––Up to 80 requests, newest first. Titles, descriptions, answers and recipients are not included.
missing_sources––Sources with no record. Missing data stays visible and is never treated as a positive result.
operation_idstringyesRevly operation ID for this read, recorded in the access log.
oppdrag_idstring|null–Engagement ID, as text.
revly_urlstring|null–Link to the requests of the engagement in Revly.
sources––Sources that contributed to the result.
statusstringyesavailable for a visible engagement.
truncatedboolean|null–True when the engagement has more than 80 requests.

No examples provided.

hent_funn ~329

Henter granskningsfunn på én eksplisitt oppdrags-ID: kode, tittel, beløp, merking, status, gjeldende vurdering, spor og kildens etikett med revly_url. Dette er ikke feilinformasjonspostene i funn_rad og ikke antallene i activity.funn på hent_oppdrag_tilstand, som er feilinformasjon. Et innebygd agentverktøy med samme navn leser et annet register. Lang beskrivelse er utelatt. Fortrolige funn er med og merket fortrolig. «Mangler kilde» betyr at kilden mangler, aldri at funnet er i orden. Filteret vurdering lik ikke_vurdert tar også med funn uten vurderingsrad. Høyst 80 funn og 20 kilder per funn.

NameTypeReqDescription
endret_sidenstring–Bare funn endret, eller vurdert, etter dette tidspunktet.
mangler_kildeboolean–true: bare funn uten kilde. false: bare funn med minst én kilde.
merkingstring–Merking av kilden til funnet.
oppdrag_idstringyesEksplisitt oppdrags-ID fra Revly. Oppslag uten ID er ikke tillatt.
spor_idstring–Bare funn i dette sporet.
vurderingstring–Gjeldende vurdering. ikke_vurdert tar også med funn uten vurderingsrad.
NameTypeReqDescription
evidence–––
funn––Granskningsfunn, at most 80.
funn_antallnumber|null–Matching findings. Zero is an empty register, not an unavailable one.
inneholder_fortroligboolean|null–True when any matching finding is marked confidential, including rows past the cap.
missing_sources––Sources with no record. Missing data stays visible and is never treated as a positive result.
operation_idstringyesRevly operation ID for this read, recorded in the access log.
oppdrag_idstring|null–Engagement ID, as text.
revly_urlstring|null–Link to the granskningsfunn page.
sources––Sources that contributed to the result.
statusstringyesResult status. not_found_or_unavailable means the engagement is not visible to this connection and the call is an error.
truncatedboolean|null–True when findings or their sources were cut.

No examples provided.

hent_funnvurderinger ~186

Henter vurderingsloggen for granskningsfunn på én eksplisitt oppdrags-ID: funnkode, status, kommentar, tidspunkt, navn og rolle. E-post, personnummer og fødselsdato er ikke med. siden gir bare vurderinger etter tidsstempelet, eldste først. Er truncated true, kall igjen med siden satt til siste opprettet_at. Dette setter ingen vurdering og endrer ikke funnstatus. Høyst 80 rader.

NameTypeReqDescription
oppdrag_idstringyesEksplisitt oppdrags-ID fra Revly. Oppslag uten ID er ikke tillatt.
sidenstring–Eksklusivt tidspunkt. Rader på nøyaktig dette tidspunktet gjentas ikke.
statusstring–Bare vurderinger med denne statusen, for eksempel trenger_mer.
NameTypeReqDescription
evidence–––
missing_sources––Sources with no record. Missing data stays visible and is never treated as a positive result.
operation_idstringyesRevly operation ID for this read, recorded in the access log.
oppdrag_idstring|null–Engagement ID, as text.
revly_urlstring|null–Link to the granskningsfunn page.
sidenstring|null–Exclusive timestamp the caller sent. Rows at that exact time are not repeated.
sources––Sources that contributed to the result.
statusstringyesResult status. not_found_or_unavailable means the engagement is not visible to this connection and the call is an error.
truncatedboolean|null–True when more assessments exist. Call again with siden set to the last opprettet_at.
vurdering_antallnumber|null–Matching assessments. Zero means none recorded after the filter.
vurderinger––Assessments after siden, oldest first, at most 80.

No examples provided.

hent_handlinger ~284

Henter revisjonshandlingene på én eksplisitt oppdrags-ID. Svaret har alltid en eksakt oppsummering per revisjonsområde: antall, utført, i arbeid, ikke aktuell og gjennomgått, for delår og årsslutt hver for seg, planlagte forslag som venter, og områdesignering. Områder med arbeidspapir telles fra arbeidspapiret, ellers fra de eldre handlingene, som i områdeoversikten. Oppgi omraade for å få handlingene i ett område: status, om den er utført og gjennomgått med dato, handlingstype, bevismetode, påstander og ISA-nummer, høyst 100 handlinger og 30 forslag. Handlingstekst, notater, konklusjoner, begrunnelser og hvem som har utført eller signert er utelatt. Et område uten handlinger betyr «ingen registrert», aldri «ferdig». Dette er arbeidsstatus, ikke en faglig godkjenning.

NameTypeReqDescription
omraadestring–Områdekode fra per_omraade, for eksempel S for salg. Utelat for bare oppsummeringen.
oppdrag_idstringyesEksplisitt oppdrags-ID fra Revly. Oppslag uten ID er ikke tillatt.
NameTypeReqDescription
aarnumber|null–Engagement year.
detalj_antallnumber|null–Procedures in the requested area; more than the rows returned when truncated.
detalj_modell––Model of the procedure rows.
evidence–––
handlinger––Procedures of the requested area, at most 100. Null when no area was requested.
missing_sources––Sources with no record. Missing data stays visible and is never treated as a positive result.
omraadestring|null–The area the procedure rows belong to, when one was requested.
operation_idstringyesRevly operation ID for this read, recorded in the access log.
oppdrag_idstring|null–Engagement ID, as text.
per_omraade––Exact roll-up per audit area over every procedure, never cut.
planlagte_handlinger––Proposed procedures in the requested area waiting for the auditor, at most 30.
revly_urlstring|null–Link to the engagement in Revly.
sources––Sources that contributed to the result.
statusstringyesavailable for a visible engagement.
truncatedboolean|null–True when the procedure rows or proposals were cut at their bound. The roll-up is never cut.

No examples provided.

hent_oppdrag_tilstand ~82

Henter avgrenset oppdragsstatus og statusantall for én eksplisitt oppdrags-ID. Fritekst, klientmeldinger og jobbinnhold er utelatt.

NameTypeReqDescription
oppdrag_idstringyesEksplisitt oppdrags-ID fra Revly. Oppslag uten ID er ikke tillatt.
NameTypeReqDescription
aarnumber|null–Engagement year.
activity––Bounded status counts. No free text or job content.
budsjett––Budget and phase reservations. Null when nothing is registered. Missing figures are null, never a fake 0.
evidence–––
fasestring|null–Engagement phase.
klient––Client for this engagement.
missing_sources––Sources with no record. Missing data stays visible and is never treated as a positive result.
operation_idstringyesRevly operation ID for this read, recorded in the access log.
oppdrag_idstring|null–Engagement ID, as text.
oppdrag_statusstring|null–Engagement status.
revly_urlstring|null–Link to the engagement in Revly.
sources––Sources that contributed to the result.
statusstringyesavailable for a visible engagement.
truncatedboolean|null–True when the result was cut short.

No examples provided.

hent_portefolje ~200

Lister alle aktive oppdrag i firmaet tilkoblingen gjelder, 50 per side, med totalt antall og antall sider. Hvert oppdrag har de samme feltene som finn_oppdrag: klient, organisasjonsnummer, år, fase, forespørsler som venter på klienten, lovfristene Revly utleder, og i tillegg nærmeste svarfrist og antall svarfrister som er passert. Bruk side for å hente resten når listen er avkortet, og aar for å avgrense til ett oppdragsår. En frist uten grunnlag står som ukjent, aldri som en gjettet dato. Tekst i forespørslene er utelatt.

NameTypeReqDescription
aarinteger–Fire-sifret oppdragsår. Utelat for alle år.
sideinteger–Side som skal hentes, fra 1.
NameTypeReqDescription
aarnumber|null–Engagement-year filter, or null for all years.
matches––Active engagements on this page, newest year first, then client name.
operation_idstringyesRevly operation ID for this read, recorded in the access log.
result_countnumber|null–Engagements on this page.
sidenumber|null–Page returned, from 1.
side_stoerrelsenumber|null–Engagements per page (50).
sidernumber|null–Number of pages for the same filter.
statusstringyesmatches, no_matches, truncated when more pages follow, or side_utenfor when the page is past the last one (not an empty result).
total_countnumber|null–Active engagements matching the filter across all pages.
truncatedboolean|null–True when more pages follow. Fetch them before saying anything about the whole portfolio.

No examples provided.

hent_signoff_status ~84

Henter avgrenset områdesignering, EQCR-, partnergjennomgangs- og beretningsstatus for én eksplisitt oppdrags-ID. Dette er ikke en faglig godkjenning.

NameTypeReqDescription
oppdrag_idstringyesEksplisitt oppdrags-ID fra Revly. Oppslag uten ID er ikke tillatt.
NameTypeReqDescription
aarnumber|null–Engagement year.
beretning––Report draft status.
eqcr––EQCR status. This is not a professional approval.
evidence–––
missing_sources––Sources with no record. Missing data stays visible and is never treated as a positive result.
omraade_signeringer––Area signatures, at most 50 groups.
operation_idstringyesRevly operation ID for this read, recorded in the access log.
oppdrag_idstring|null–Engagement ID, as text.
partnergjennomgang––Partner review summary.
revly_urlstring|null–Link to the engagement in Revly.
sources––Sources that contributed to the result.
statusstringyesavailable, or not_recorded when no signature, review or report exists.
truncatedboolean|null–True when the area list was cut short.

No examples provided.

hent_vesentlighet ~78

Henter registrerte vesentlighetsgrenser og en begrenset begrunnelse for én eksplisitt oppdrags-ID. Manglende vurdering forblir synlig.

NameTypeReqDescription
oppdrag_idstringyesEksplisitt oppdrags-ID fra Revly. Oppslag uten ID er ikke tillatt.
NameTypeReqDescription
aarnumber|null–Engagement year.
assessment_statusstring|null–available or not_assessed. not_assessed is never a positive conclusion.
begrunnelsestring|null–Rationale, bounded to 2000 characters. Null when not recorded, including an empty or blank stored value.
begrunnelse_avkortetboolean|null–True when the rationale was cut to 2000 characters.
begrunnelse_status––mangler when no rationale text is recorded, even if thresholds are set. Never read a missing rationale as an assessment.
evidence–––
grenser––Registered materiality thresholds.
missing_sources––Sources with no record. Missing data stays visible and is never treated as a positive result.
operation_idstringyesRevly operation ID for this read, recorded in the access log.
oppdrag_idstring|null–Engagement ID, as text.
revly_urlstring|null–Link to the engagement in Revly.
sources––Sources that contributed to the result.
statusstringyesavailable for a visible engagement.
truncatedboolean|null–True when the result was cut short.

No examples provided.

revly_health ~25

Returnerer den offentlige, lesende helsestatusen for Revly.

Input schema present but exposes no named parameters.

NameTypeReqDescription
checked_atstringyes–
statusstringyes–

No examples provided.

revly_kontekst ~42

Viser firmaet tilkoblingen gjelder (ID og navn), rollen din, den registrerte assistenten og verktøyene du har tilgang til.

Input schema present but exposes no named parameters.

NameTypeReqDescription
allowed_tools––Read tools this connection may call.
client––Assistant registered for this connection.
firma_idstring|null–ID of the firm this connection is for, as text.
firma_navnstring|null–Name of the firm this connection is for.
firma_rollestring|null–Your role in the firm, for example partner.
operation_idstringyesRevly operation ID for this read, recorded in the access log.
statusstringyesavailable when the connection is valid.

No examples provided.

Install

How do I install the Revly MCP server?

Revly is a hosted endpoint at https://revly.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 · revly.no

# add to Claude Code
claude mcp add --transport http no-revly-revly 'https://revly.no/mcp'
Common questions

What is the Revly MCP server?

Revly is an MCP server listed in the public MCP registry as no.revly/revly. Revly kobler assistenter til revisjonsarbeid med firmastyrt tilgang og personlig samtykke. This page covers its hosted endpoint (https://revly.no/mcp).

Is the Revly MCP server safe to use?

Revly scores 75 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 Revly MCP server expose?

Revly exposes 12 tools: revly_health, revly_kontekst, finn_oppdrag, hent_oppdrag_tilstand, hent_vesentlighet, and 7 more. Their descriptions and schemas cost roughly 1,823 tokens of context every time the server is loaded.

Does the Revly MCP server require authentication?

No. We connected to Revly without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Revly MCP server still maintained?

Revly 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.