Robin Saige we check the tools AI agents call

Firmaradar

no.firmaradar/mcp

Norwegian company intelligence: ownership, roles, financials, risk, KYC/AML/PEP (multi-source)

— the operator's own registry description reported

Publisher no.firmaradar · first seen 2026-08-12 · endpoint https://mcp.firmaradar.no/mcp

allow
verdict
rich-slow-solo
cluster
ok_tools
answers
36
tools served

Dependency rating derived

allow
allow — alive & usable · retrieval-public ● · V3 has answer key ◐
allow — because answers ●, 36 tools legible (band A) ●, no confirmed drift in 2 probes ●; not yet checked: truth (4 attempts unverifiable, 0 disagreements)

Cluster rich-slow-solo · distinctiveness 0.541 (moderate). Every figure is a percentile or class within the 11,094-server censussee the whole spectrum.

Does it answer? Q1 · observed
answersalive_tools
latency503 ms
vs populationslow
protocolcurrent
authopen
Can it be used? Q4 · observed
tools36
vs populationhigh
capabilities2
harnessA
Did it hold when checked? Q3–Q4 · derived
identitysolo
servers on its host1
verifiabilityunassessed
duplicate inventoryno
drift events0
answers true0/0 agree

🔏 Signed receipt rr_9ab59045a14c19ae45033e9a · ed25519 · key rs-rcpt-2026-08 — this rating is tamper-evident; an agent gets the full signature from check_server and can verify it against the published key.

Q1Does it answer?alive & usable — 2 probes ●evidence ↓
Q2What is it?retrieval-public ● evidence ↓
Q3Can it be checked?V3 has answer key ◐evidence ↓
Q4Did it hold?harness A · truth not yet run · no drift ●evidence ↓
Q5What company does it keep?rich-slow-solo · 1 on its host (context, not verdict) ◐evidence ↓

● observed · ◐ derived · ○ reported — the verdict synthesizes Q1–Q4; Q5 is context. Methodology →

History observed

Every probe we made, oldest → newest (2 shown, 2026-08-12 → 2026-08-14). Green answered · amber answered-but-walled · red no useful answer. A gap in our cadence is a gap in coverage, not evidence about the server.

changelog (1 events)
datetypewhat changed
2026-08-12outcomefirst probe: ok_tools

What kind of tools these are derived

Verification only means something relative to a tool's NATURE — an email-sender has no "true answer", a generator has no answer key. Classification evidence: classified from tool names/descriptions/annotations WE OBSERVED. What checking applies to each kind (the full methodology →):

naturetoolsmeaning what checking applies
retrieval-public28serves public factstruth-checkable against a public source — the V-ladder applies in full
action4changes the worldno true answer exists; we check the CONTRACT (destructive/read-only/idempotent declarations, error legibility) and never fire real actions
computational2deterministic transformsself-checkable by re-computation and known-answer tests
generative2creates contentno answer key exists; disclosure + stability checks, never truth verdicts

Tools last seen observed

firmaradar_add_company_monitoring firmaradar_check_aml_pep firmaradar_check_fiv_bulk firmaradar_check_foretak_i_vanskeligheter firmaradar_check_konkurs_eksponering firmaradar_compare_companies firmaradar_confirm_risk_score_disclaimer firmaradar_convert_nok firmaradar_delete_subscription firmaradar_find_related_companies firmaradar_find_shared_connections firmaradar_get_aml_report firmaradar_get_aml_score firmaradar_get_company firmaradar_get_company_announcements firmaradar_get_company_financials firmaradar_get_company_ip firmaradar_get_company_ownership firmaradar_get_company_roles firmaradar_get_company_signals firmaradar_get_konsernstotte firmaradar_get_person firmaradar_get_person_companies firmaradar_get_person_roles firmaradar_get_recent_changes firmaradar_get_regnskapsrapport firmaradar_get_risk_score firmaradar_get_risk_score_bulk firmaradar_list_companies_in_nace firmaradar_list_my_subscriptions firmaradar_list_nace_codes firmaradar_search_announcements firmaradar_search_companies firmaradar_search_persons firmaradar_start_aml_report firmaradar_subscribe_nace

Harness readiness observed

Can an agent's harness pick this tool and call it correctly? Graded on the three things an agent reads — name, description, typed parameters. Band A — an agent can pick and call these reliably.

legibility checktools passingok
name is clear & specific36/36
has a description36/36
description is substantive36/36
parameters are typed36/36
parameters are described24/3624/36

36 of 36 tools graded · 36 with a captured input schema. RS-008, Tier-1 — no domain knowledge, applies to any tool. “Alive” is not the same as “usable”.

Truth checks observed

Not yet confirmed — 4 attempt(s) currently unverifiable (rate limits, walls, or unmappable schemas — never counted against the server) · 0 disagreements.

claim classkeyverdictprimary source
fx-ratesEURUSDunverifiableecb-fx
OFAC SDN screening (vs the official list)ISLAMIC REVOLUTIONARY GUARD CORPSunverifiableofac-sdn
OFAC SDN screening (vs the official list)MAERSK LINEunverifiableofac-sdn
tariff-dutyunmappedunverifiableus-hts

Protocol conformance observed

2025-06-18
protocol version
session model
0.6.1
server version firmaradar-mcp

Capabilities: experimental tools

Drift observed

No confirmed drift on record. Baseline set 2026-08-14; changes appear here after human review.

raw probe records
probed (UTC) outcomehttpmsprotocol
2026-08-14T20:00:34Zok_tools2005032025-06-18
2026-08-12T05:35:50Zok_tools2005142025-06-18

Watch or embed this verdict

verdict badge

Operators: put the live verdict in your README — it updates with every census, links back here, and is a dated observation, never a warranty:

[![Robin Saige verdict](https://robinsaige.com/badge/no.firmaradar/mcp.svg)](https://robinsaige.com/s/no.firmaradar/mcp)

Depend on it? Subscribe to its change feed — outcome changes and confirmed drift, no account needed. Building on it? The full dossier as JSON — verdict, rating, truth checks, history — stable enough to gate CI on.

← overview