JaKonto
REMOTE · JAKONTO.DK
Danish accounting data from e-conomic and Billy: invoices, VAT by quarter, P&L. Read-only.
Available components
Last scanned (20 hours ago)
Scores higher than 79% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Finance and Payments
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 Security91
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability63
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 361 tokens (~60/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management53
- Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage87
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 60% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 21 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Nov 26 0
- Tool “vat_by_quarter” rewrote its description, which is the text the model reads security
- Schema quality: fair → good functional
- 11 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
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 21 Nov 2026 · Probed https://jakonto.dk/api/v1/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=jakonto.dk | CN=YE1,O=Let's Encrypt,C=US | 26 Oct 2026 | 24 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 51a6e971ea64e790025f963dbf733f8b34c |
| SANs: jakonto.dk, www.jakonto.dk | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of jakonto.dk. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| dk. | DS published | 16874 | 13 | Verified |
| jakonto.dk. | DS published | 20513 | 13 | Verified |
| jakonto.dk. | Verified address RRset verified with the apex keys |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="jakonto"
Bearer realm="jakonto" | Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | No resource metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://jakonto.dk/api/v1/mcp | Verified | 200 | |
| http (plaintext) | http://jakonto.dk/api/v1/mcp | HTTPS enforced | 301 | https://jakonto.dk/api/v1/mcp |
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 →
create_proposals ~55
Scan for anomalies and file them as DRAFT proposals in JaKonto for a human to approve. Never writes to the accounting system. Idempotent per open finding.
| Name | Type | Req | Description |
|---|---|---|---|
| connection_id | string | yes | Id from list_connections |
No output schema declared.
No examples provided.
list_connections ~33
The accounting systems this API key can read (e-conomic, Dinero, Billy …): id, system, company.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_invoices ~57
One page of invoices from the accounting system, canonical model (amounts in øre). Pass next_cursor back as cursor for the next page.
| Name | Type | Req | Description |
|---|---|---|---|
| connection_id | string | yes | Id from list_connections |
| cursor | string | – | – |
No output schema declared.
No examples provided.
list_proposals ~40
Bookkeeping proposals waiting for (or past) human review.
| Name | Type | Req | Description |
|---|---|---|---|
| connection_id | string | yes | Id from list_connections |
| status | string | – | – |
No output schema declared.
No examples provided.
profit_and_loss ~61
Resultatopgørelse (profit and loss) for a period: revenue and expense lines, result (øre).
| Name | Type | Req | Description |
|---|---|---|---|
| connection_id | string | yes | Id from list_connections |
| date_from | string | yes | – |
| date_to | string | yes | – |
No output schema declared.
No examples provided.
vat_by_quarter ~82
Output VAT, input VAT and VAT payable per quarter (øre). From the VAT ledger accounts (incl. input VAT) when journal entries are synced, otherwise from sales invoices only — each quarter says which in `source` (ledger | invoices).
| Name | Type | Req | Description |
|---|---|---|---|
| connection_id | string | yes | Id from list_connections |
| year | integer | – | Default: this year |
No output schema declared.
No examples provided.
How do I install the JaKonto MCP server?
JaKonto is a hosted endpoint at https://jakonto.dk/api/v1/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 · jakonto.dk
claude mcp add --transport http dk-jakonto-jakonto 'https://jakonto.dk/api/v1/mcp'
What is the JaKonto MCP server?
JaKonto is an MCP server listed in the public MCP registry as dk.jakonto/jakonto. Danish accounting data from e-conomic and Billy: invoices, VAT by quarter, P&L. Read-only. This page covers its hosted endpoint (https://jakonto.dk/api/v1/mcp).
Is the JaKonto MCP server safe to use?
JaKonto scores 81 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 JaKonto MCP server expose?
JaKonto exposes 6 tools: list_connections, list_invoices, vat_by_quarter, profit_and_loss, list_proposals, create_proposals. Their descriptions and schemas cost roughly 328 tokens of context every time the server is loaded.
Does the JaKonto MCP server require authentication?
Yes. JaKonto asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the JaKonto MCP server still maintained?
JaKonto is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the JaKonto MCP server?
VerifyMCP ran 13 checks on JaKonto, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.