Layerone MCP Server
layerone-mcp
npm
v1.0.0
Source verified
Published by golayerone — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.
Serveur MCP LayerOne — expose les API DocX (génération de documents, PDF, factures Factur-X) et Sign (signature électronique eIDAS/PAdES) aux agents IA (Claude, ChatGPT, Cursor…).
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 3 = 97. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −3 | capability blast radius (moderate) — client exposure if the model is manipulated |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Findings 1
medium Untrusted input can drive an external actionMTC-FLOW-005
Untrusted-input tools ([docx_download_template, docx_download_template_version, sign_download_signed_document]) co-exist with external-action tools ([sign_send_otp]). A prompt injection could cause unwanted external actions, though no direct sensitive-data leak path was found.
Evidence: untrusted [docx_download_template, docx_download_template_version, sign_download_signed_document] → sinks [sign_send_otp]
Fix: Require confirmation for state-changing/egress actions triggered after processing untrusted content.
Location: flow docx_download_template → sign_send_otp
Tools 20
Each tool and what it can reach — statically extracted from the published source.
docx_download_templateingests untrusted inputdocx_download_template_versioningests untrusted inputsign_download_signed_documentingests untrusted inputsign_send_otpnetwork egressdocx_delete_templateno sensitive capabilitydocx_get_usage_statsno sensitive capabilitydocx_list_template_versionsno sensitive capabilitydocx_list_templatesno sensitive capabilitydocx_render_documentno sensitive capabilitydocx_render_facturxno sensitive capability
Show 10 more tools ↓
docx_restore_template_versionno sensitive capabilitydocx_update_templateno sensitive capabilitydocx_upload_templateno sensitive capabilitysign_cancel_documentno sensitive capabilitysign_detect_fieldsno sensitive capabilitysign_get_audit_certificateno sensitive capabilitysign_get_document_statusno sensitive capabilitysign_send_for_signatureno sensitive capabilitysign_validate_signatureno sensitive capabilitysign_verify_otpno sensitive capability
Toxic flows 1
Cross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).
What this scan could not see
- Tools were statically extracted from the published source (20 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions 1
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v1.0.0 latest |
A 97/100 | 1 | 1.13.0 | 2026-09-08 |
Embed this score
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
Verify this score yourself
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan layerone-mcp --onlineMore in Finance & Commerce
<img src="./public/logo.png" alt="1Money Logo" width="200"/>
Signed verification attestations for agent decisions: business, price, freshness, claim checks.
Actual Budget MCP server exposing API functionality
MCP server for Actual Budget - query and manage your personal finances through Claude
The Adyen Model Context Protocol server allows you to integrate with Adyen APIs through LLMs function calling utilizing various Clients. It currently supports the following tools:
Trusted agent-commerce hub: discover, trust-check, and route x402 payments with failover.