Luca: books for AI spend and agent payments
REMOTE · SANDBOX.LUCA.NETWORK
See Luca close a month of AI spend and agent payments, with evidence. Read-only, no key.
Available components
Last scanned (14 hours ago)
Scores higher than 57% 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 Security74
- 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
- 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 & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability68
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 287 tokens (~71/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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.
- 20 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 16 Nov 26 70
First indexed and scored.
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://sandbox.luca.network/mcp/public
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=sandbox.luca.network | CN=Amazon RSA 2048 M01,O=Amazon,C=US | 18 Oct 2026 | 3 May 2027 | RSA 2048 | SHA256-RSA | a4f6f0fa5c1797993db57fabac632a0 |
| SANs: sandbox.luca.network | ||||||
| CN=Amazon RSA 2048 M01,O=Amazon,C=US (CA) | CN=Amazon Root CA 1,O=Amazon,C=US | 23 Aug 2022 | 23 Aug 2030 | RSA 2048 | SHA256-RSA | 77312380b9d6688a33b1ed9bf9ccda68e0e0f |
| CN=Amazon Root CA 1,O=Amazon,C=US (CA) | CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US | 25 May 2015 | 31 Dec 2037 | RSA 2048 | SHA256-RSA | 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of sandbox.luca.network. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| network. | DS published | 11416 | 8 | Verified |
| luca.network. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://sandbox.luca.network/mcp/public | Verified | 200 | |
| http (plaintext) | http://sandbox.luca.network/mcp/public | HTTPS enforced | 301 | https://sandbox.luca.network:443/mcp/public |
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 →
about_luca What Luca does ~50
What Luca does, who it is for, the rails it reads and ERPs it posts to, pricing, the security controls in place and what is planned, and links to everything. No key needed.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
see_luca_working See Luca working ~79
The live demo, refreshed daily: an AI-spend month-end close for a sample company with each requirement passed, failed or not tested and its evidence, five checks a buyer's agent asked for (authorization, settlement integrity, missing evidence, accounting, audit and ERP), and agent payments classified and checked against spending rules. No key needed.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
verify_record Check a record's signature ~50
Check the Ed25519 signature of one of the demo's records, by its id (LR-…). No key needed.
| Name | Type | Req | Description |
|---|---|---|---|
| record_id | string | yes | A record id from see_luca_working |
No output schema declared.
No examples provided.
what_can_be_tested What an evaluation can prove ~34
The requirements Luca can test in an AI-spend month-end close, with what each checks. No key needed.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the Luca: books for AI spend and agent payments MCP server?
Luca: books for AI spend and agent payments is a hosted endpoint at https://sandbox.luca.network/mcp/public, 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 · sandbox.luca.network
claude mcp add --transport http network-luca-luca-public 'https://sandbox.luca.network/mcp/public'
What is the Luca: books for AI spend and agent payments MCP server?
Luca: books for AI spend and agent payments is an MCP server listed in the public MCP registry as network.luca/luca-public. See Luca close a month of AI spend and agent payments, with evidence. Read-only, no key. This page covers its hosted endpoint (https://sandbox.luca.network/mcp/public).
Is the Luca: books for AI spend and agent payments MCP server safe to use?
Luca: books for AI spend and agent payments scores 72 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 Luca: books for AI spend and agent payments MCP server expose?
Luca: books for AI spend and agent payments exposes 4 tools: about_luca, see_luca_working, verify_record, what_can_be_tested. Their descriptions and schemas cost roughly 213 tokens of context every time the server is loaded.
Does the Luca: books for AI spend and agent payments MCP server require authentication?
No. We connected to Luca: books for AI spend and agent payments without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Luca: books for AI spend and agent payments MCP server still maintained?
Luca: books for AI spend and agent payments 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 Luca: books for AI spend and agent payments MCP server?
VerifyMCP ran 13 checks on Luca: books for AI spend and agent payments, 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.