eBilanz Fabrik
REMOTE · APP.EBILANZFABRIK.DE
E-Bilanz and Offenlegung for small German GmbH/UG: products, prices, eligibility.
Available components
Last scanned (12 hours ago)
Scores higher than 89% of remote servers
Reachable. Last reached 5 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 Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- 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 Usability78
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 460 tokens (~153/item across 3 items; 3 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 Management63
- Stability observed for 19 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 2 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.
- 31 Oct 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.
- 29 Oct 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.
- 27 Oct 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.
- 25 Oct 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.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Oct 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 5 Nov 2026 · Probed https://app.ebilanzfabrik.de/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=app.ebilanzfabrik.de | CN=YE1,O=Let's Encrypt,C=US | 27 Oct 2026 | 25 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 5f1b03113cc159462078e74fe7753444235 |
| SANs: app.ebilanzfabrik.de | ||||||
| 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 app.ebilanzfabrik.de. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| de. | DS published | 26755 | 8 | Verified |
| ebilanzfabrik.de. | DS published | 2371 | 13 | Verified |
| app.ebilanzfabrik.de. | Verified address RRset verified with the apex keys |
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=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| permissions-policy | accelerometer=(), autoplay=(), camera=(), display-capture=(), encrypted-media=(), fullscreen=(), geolocation=(), gyroscope=(), magnetometer=(), microphone=(), midi=(), payment=(), usb=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://app.ebilanzfabrik.de/mcp | Verified | 200 | |
| http (plaintext) | http://app.ebilanzfabrik.de/mcp | HTTPS enforced | 308 | https://app.ebilanzfabrik.de/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 →
ebf_check_eligibility Check eligibility ~236
Ask whether a given company can be served — legal form, size class, fiscal year — answered by the production engine, with the reasons if not. This endpoint only answers questions about eBilanz Fabrik's products, prices and whether a company's legal form, size class and financial year are in scope. It prepares nothing, never files, never takes payment, and never accepts an ELSTER certificate or PIN.
| Name | Type | Req | Description |
|---|---|---|---|
| groesse | string | yes | size class per § 267/267a HGB — Kleinst, klein, mittelgross, gross (case does not matter) |
| rechtsform | string | yes | legal form — GmbH, UG, UG (haftungsbeschränkt), AG, Aktiengesellschaft, SE, Societas Europaea, andere (case does not matter) |
| stichtag | string | yes | REQUIRED — balance sheet date as YYYY-MM-DD, e.g. 2024-12-31. Omitting it makes the engine treat the year as abweichend and answer eligible=false. |
| wirtschaftsjahr | string | – | the fiscal year, e.g. 2024 |
No output schema declared.
No examples provided.
ebf_get_pricing Current prices ~88
Current net prices per submission, read from the site's published Offer metadata. German VAT of 19 % is added at checkout. This endpoint only answers questions about eBilanz Fabrik's products, prices and whether a company's legal form, size class and financial year are in scope. It prepares nothing, never files, never takes payment, and never accepts an ELSTER certificate or PIN.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
ebf_get_products Products available now ~81
Which eBilanz Fabrik products can be bought right now, as the server itself reports. This endpoint only answers questions about eBilanz Fabrik's products, prices and whether a company's legal form, size class and financial year are in scope. It prepares nothing, never files, never takes payment, and never accepts an ELSTER certificate or PIN.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the eBilanz Fabrik MCP server?
eBilanz Fabrik is a hosted endpoint at https://app.ebilanzfabrik.de/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 · app.ebilanzfabrik.de
claude mcp add --transport http de-ebilanzfabrik-ebilanz-fabrik 'https://app.ebilanzfabrik.de/mcp'
What is the eBilanz Fabrik MCP server?
eBilanz Fabrik is an MCP server listed in the public MCP registry as de.ebilanzfabrik/ebilanz-fabrik. E-Bilanz and Offenlegung for small German GmbH/UG: products, prices, eligibility. This page covers its hosted endpoint (https://app.ebilanzfabrik.de/mcp).
Is the eBilanz Fabrik MCP server safe to use?
eBilanz Fabrik scores 84 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 eBilanz Fabrik MCP server expose?
eBilanz Fabrik exposes 3 tools: ebf_get_products, ebf_get_pricing, ebf_check_eligibility. Their descriptions and schemas cost roughly 405 tokens of context every time the server is loaded.
Does the eBilanz Fabrik MCP server require authentication?
No. We connected to eBilanz Fabrik without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the eBilanz Fabrik MCP server still maintained?
eBilanz Fabrik 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.
What did VerifyMCP test on the eBilanz Fabrik MCP server?
VerifyMCP ran 13 checks on eBilanz Fabrik, 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.