Is no.firmaradar/mcp up? Live MCP status
Not checked just now. The live check did not run for this request (more than 120 status pages asked for a fresh check in the last minute). Reload in a minute; the monthly census result is below.
| Endpoint | https://mcp.firmaradar.no/mcp |
|---|---|
| Page built |
One MCP handshake with the listed endpoint (server/discover at 2026-07-28, then initialize for a server on the older revision), with no credential and no retry, identifying itself as agentwares-mcp-liveness/0.1 (+https://agentwares-agentcheck.vercel.app/bot). It runs when this page is requested and the result is reused for 10 minutes, so the time above is when it was taken.
Live status every few hours: Wellknown
Email me when this server changes
That was one look. To hear when it stops answering or its tools change, leave an address.
Free, no password or GitHub: one confirmation email first, then a check every hour and an email when it stops answering or its tools change. Every email has a link to stop. More about it.
Monthly census, 6 October 2026
The census sends the same request to every remote listing in the official registry once a month. On 6 October 2026 this one answered a stock client with no credential. Every listing’s result: index.ndjson (what the files hold: index.meta.json).
Agent discovery documents at this origin
| A2A agent card | Not published (HTTP 404)./.well-known/agent-card.json |
|---|---|
| MCP server card (SEP-2127) | Could not tell (HTTP 401).https://mcp.firmaradar.no/mcp/server-card |
| MCP server card (SEP-1649 location) | Not published (HTTP 404)./.well-known/mcp/server-card.json — SEP-1649, a draft superseded by SEP-2127 on 21 January 2026 |
| Web Bot Auth key directory | Not published (HTTP 404)./.well-known/http-message-signatures-directory |
Read at https://mcp.firmaradar.no with the monthly census on 9 October 2026: one GET each, no credential, never a signed request. A2A against v1.0.1, the server card against the MCP Server Card schema (SEP-2127), the card at SEP-1649’s location against the shape it has, the key directory against the Web Bot Auth draft of 1 September 2026. Who publishes them.
Tool changes between snapshots
In the 2026-10 snapshot it listed 36 tools: 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.
Its tools changed between 2026-09 and 2026-10:
firmaradar_check_fiv_bulk: output schema changedfirmaradar_get_risk_score_bulk: description, output schema changedfirmaradar_subscribe_nace: description, output schema changed
Which tools were added or removed, and whose description or schemas changed, from content hashes in the monthly snapshots. Per tool, as JSON: /v1/drift.
The listing
| Registry name | no.firmaradar/mcp |
|---|---|
| Endpoint | https://mcp.firmaradar.no/mcp |
| Publisher repository | not known: the registry did not return this listing within 4 seconds |
Also
The full check by name, as JSON (on a 401 it also follows the OAuth discovery chain) · Watch it · Check another server · llms.txt