io.github.CedricKouma/facturx-toolkit
REMOTE · APIM-AGENTFORGE-6LFM33.AZURE-API.NET · 2 COMPONENTS
Validate, extract, repair and generate French Factur-X / EN16931 invoices via AgentForge API
Available components
Last scanned (16 hours ago)
Scores higher than 13% 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 Security71
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, but returns a challenge with no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 404, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
- Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified
Unverified: 6 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm. Claim this server and supply a read-only token to verify it and lift the score.
Checks we ran (4)
- TLS certificate
- Authorization
- HSTS header
- DNSSEC
Checks we could not complete (7)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 404, which proves neither a plaintext path nor enforcement.
- Transport in Transport & Reachability (scores 0 for this)Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema blocked by authentication: the endpoint requires auth we don't have to read it.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.
- Tool safety in Tool Safety (scores 0 for this)Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.
- Capabilities in Capabilities (scores 0 for this)Capabilities blocked by authentication: the endpoint requires auth we don't have to read them.
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.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 10 Aug 26 0
- Authorization: fail → unverified ▼ security
- HSTS header: fail → unverified ▼ security
- HTTPS: unverified → pass ▲ security
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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://apim-agentforge-6lfm33.azure-api.net/facturx/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.azure-api.net,O=Microsoft Corporation,L=Redmond,ST=WA,C=US | CN=Microsoft TLS G2 RSA CA OCSP 10,O=Microsoft Corporation,C=US | 29 Aug 2026 | 25 Feb 2027 | RSA 2048 | SHA384-RSA | 4900c98bdde4bfd703190594dd000000c98bdd |
| SANs: *.azure-api.net, *.portal.azure-api.net, *.management.azure-api.net, *.scm.azure-api.net, *.configuration.azure-api.net, *.regional.azure-api.net, *.developer.azure-api.net, *.data.azure-api.net, *.portal-editor.azure-api.net, *.unique.azure-api.net, *.unique.portal.azure-api.net, *.unique.management.azure-api.net and 6 more | ||||||
| CN=Microsoft TLS G2 RSA CA OCSP 10,O=Microsoft Corporation,C=US (CA) | CN=Microsoft TLS RSA Root G2,O=Microsoft Corporation,C=US | 1 Aug 2025 | 3 Jun 2029 | RSA 4096 | SHA384-RSA | 330000000f33206537ee42ae4f00000000000f |
| CN=Microsoft TLS RSA Root G2,O=Microsoft Corporation,C=US (CA) | CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US | 21 May 2025 | 19 Jun 2029 | RSA 4096 | SHA384-RSA | b0c6b2c466917b04773c647d4afc0c8 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of apim-agentforge-6lfm33.azure-api.net. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| net. | DS published | 37331 | 13 | Verified |
| azure-api.net. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
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 connection |
| HTTP status | 401 |
WWW-Authenticate challenge AzureApiManagementKey realm="https://apim-agentforge-6lfm33.azure-api.net/facturx",name="Ocp-Apim-Subscription-Key",type="header"
AzureApiManagementKey realm="https://apim-agentforge-6lfm33.azure-api.net/facturx",name="Ocp-Apim-Subscription-Key",type="header"| Header | Value |
|---|---|
| www-authenticate | AzureApiManagementKey realm="https://apim-agentforge-6lfm33.azure-api.net/facturx",name="Ocp-Apim-Subscription-Key",type="header" |
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://apim-agentforge-6lfm33.azure-api.net/facturx/mcp | Auth required | 401 | |
| http (plaintext) | http://apim-agentforge-6lfm33.azure-api.net/facturx/mcp | Inconclusive | 404 |
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 →
No tool schema has been captured from this endpoint yet.
How do I install the io.github.CedricKouma/facturx-toolkit MCP server?
io.github.CedricKouma/facturx-toolkit is a hosted endpoint at https://apim-agentforge-6lfm33.azure-api.net/facturx/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 · apim-agentforge-6lfm33.azure-api.net
claude mcp add --transport http cedrickouma-facturx-toolkit 'https://apim-agentforge-6lfm33.azure-api.net/facturx/mcp'
What is the io.github.CedricKouma/facturx-toolkit MCP server?
io.github.CedricKouma/facturx-toolkit is an MCP server listed in the public MCP registry as io.github.CedricKouma/facturx-toolkit. Validate, extract, repair and generate French Factur-X / EN16931 invoices via AgentForge API. This page covers its hosted endpoint (https://apim-agentforge-6lfm33.azure-api.net/facturx/mcp).
Is the io.github.CedricKouma/facturx-toolkit MCP server safe to use?
io.github.CedricKouma/facturx-toolkit scores 28 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.
Does the io.github.CedricKouma/facturx-toolkit MCP server require authentication?
Yes. io.github.CedricKouma/facturx-toolkit 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 io.github.CedricKouma/facturx-toolkit MCP server still maintained?
io.github.CedricKouma/facturx-toolkit 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 io.github.CedricKouma/facturx-toolkit MCP server?
VerifyMCP ran 4 checks on io.github.CedricKouma/facturx-toolkit, covering TLS certificate, Authorization, HSTS header and DNSSEC. 7 items could not be completed, a gap on our side rather than a finding about io.github.CedricKouma/facturx-toolkit: HTTPS, Transport, Schema quality, Stability and 3 more. 6 categories score 0 for that reason, because we only credit what we can confirm. 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.