Is no.apier/mcp up? Live MCP status

Yes, it is up. It answered an MCP initialize with no credential and negotiated protocol 2025-11-25.

A stock client connected with no credential and negotiated 2025-11-25. Use it.

Outcomeusable
HTTP status200
Protocol version2025-11-25
Server says it isapier-no 2026.8.1
Answered in538 ms
Endpoint checkedhttps://www.apier.no/api/mcp
Checked

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 cardNot published (HTTP 410).
/.well-known/agent-card.json
MCP server card (SEP-2127)Not published (HTTP 404).
https://www.apier.no/api/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 directoryNot published (HTTP 404).
/.well-known/http-message-signatures-directory

Read at https://www.apier.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 25 tools: check_authorization, check_fullmakt, explain_compliance_error, get_altinn_migration_guidance, get_company_accounts, get_company_authority, get_company_context, get_company_deadlines, get_company_filing_history, get_company_obligations, get_company_profile, get_company_summary, get_company_verification, get_credit_balance, get_exchange_rate, get_pricing, get_public_deadlines, get_public_obligations, list_acting_capacity, list_changes, redeem_issuance_token, request_fullmakt, revoke_fullmakt, search_companies, validate_action.

Its tools changed between 2026-09 and 2026-10:

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 nameno.apier/mcp
TitleApier
DescriptionCompliance infrastructure API connecting AI agents to Norwegian government systems (Altinn, BRREG).
Endpointhttps://www.apier.no/api/mcp
Publisher repositoryhttps://github.com/PowerLaunch/apier-mcp
Version2026.8.1
Listing updated

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

Free, no key, no signup. Terms · Privacy