Skip to content
ProtocolProbe

MCP servers › io.github.CSOAI-ORG › delboy-mcp

MCP server · registry snapshot 2026-10-04 · last tested 2026-10-08

io.github.CSOAI-ORG/delboy-mcp

DELBOY companion-MCP — neutral provenance/attestation layer for agentic finance. Witness only: signs — the publisher's description

Topic: finance-and-payments · AI-classifiedversion 1.0.1Apache-2.0standard input/output5 tools

Summary

io.github.CSOAI-ORG/delboy-mcp is a local MCP server listed in the official MCP registry at version 1.0.1. On 2026-10-08 ProtocolProbe started its published package in an isolated sandbox in read-only mode and read its inventory: 5 tools, 0 resources and 0 prompts. This test round was read-only, so its tools were not called. 2 of the 12 checks that apply to it were exercised. Results of the checks are published only after we have verified them and told the publisher.

Not probed (read-only run)

We started the package in an isolated sandbox and read what it declares, but this test round was read-only, so its tools were not called. No security score is given; a check we did not run is never counted as passed.

Key facts

Runs
local package
Transport
standard input/output
Package
PyPI · listed version behind the latest release
License
Apache-2.0
Dependencies
no known high or critical advisories
Topic
finance-and-paymentsAI-classified
Last tested
2026-10-08
The 18 checks at a glanceour test · 2026-10-08
  1. Inventory: exercised
  2. Hidden instructions: exercised
  3. Real execution: not run · our policy
  4. Secret leak: not run · nothing to check it against
  5. Internal addresses: not run · our policy
  6. Unconfirmed changes: not run · our policy
  7. Bad input: not run · our policy
  8. Model requests: not run · nothing to check it against
  9. Sensitive questions: not run · nothing to check it against
  10. Folder boundary: not run · our policy
  11. Log leaks: not run · nothing to check it against
  12. Hidden content: not run · nothing to check it against
  13. Fake assistant turns: not applicable
  14. Token passthrough: not applicable
  15. Token audience: not applicable
  16. Sign-in redirect: not applicable
  17. Consent handling: not applicable
  18. Sign-in metadata: not applicable

2 exercised10 not run (reason given)6 not applicable

Worth knowing before you connect it

  • The registry lists 1.0.1; 1.0.2 is newer (1 release).

Each line comes from a section below, with its source and date.

How fresh this is

Live-tested
yes, a real session (not a text-only review)
Last tested
2026-10-08
Mode
read-only (no tool calls)
Registry data
snapshot 2026-10-04
Package and repository
checked 2026-10-06
Engine
mcp-runtime-engine@0.1.0 · sdk@1.32.0

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 2 of the 12 checks that apply to it were exercised. Results of the checks are published only after we have verified them and told the publisher.

Exercised · 2
  • 1Inventory
    tool-list    Reads the declared tools, resources and prompts.exercised
  • 2Hidden instructions
    description-poisoning    Looks for hidden instructions in tool descriptions.exercised
Not run, with the reason · 10
  • 3Real execution
    real-execution    Calls a tool and checks what really happens.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
  • 4Secret leak
    canary-leak    Plants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 5Internal addresses
    ssrf    Checks whether a tool can be steered to internal addresses.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
  • 6Unconfirmed changes
    write-without-confirmation    Checks whether tools that change data act without asking.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
  • 7Bad input
    error-handling    Sends bad input and watches how the server answers.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
  • 8Model requests
    sampling    Checks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 9Sensitive questions
    elicitation-sensitive-data    Checks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 10Folder boundary
    root-boundary    Checks whether the server reaches outside the folders it was given.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy
  • 11Log leaks
    logging-side-channel    Checks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 12Hidden content
    audience-hiding    Checks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against
Does not apply to this server · 6
  • 13Fake assistant turns
    fake-assistant-turn    Checks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable
  • 14Token passthrough
    token-passthrough    Checks whether the server forwards a user's token to other services.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
  • 15Token audience
    token-audience-validation    Checks whether tokens meant for another service are accepted.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
  • 16Sign-in redirect
    open-redirect    Checks the sign-in redirect for abuse.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
  • 17Consent handling
    confused-deputy    Checks consent handling when one service acts for another.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
  • 18Sign-in metadata
    oauth-url-scheme    Checks the published sign-in metadata for unsafe URLs.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable

Source: our own test in an isolated sandbox, 2026-10-08, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

  1. 0 msStarted the published package in an isolated sandbox (read-only mode)
  2. 9,532 msConnected after 0 redirects.
  3. Read the inventory: 5 tools, 0 resources, 0 prompts.
  4. 18,184 msFinished: 2 checks exercised.

What it is

What does this server offer?

Observed inventory
5tools
0resources
0prompts
  • attest_pending_action
  • attest_completed_action
  • attest_terminal
  • verify_chain
  • delboy_info

Tool names are chosen by the publisher.

Does the registry listing match what we found?

Feature #6

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.

Registry saysWe foundResultSource · date
Published package can be startedStarted and answeredmatchesour test · 2026-10-08
Version 1.0.1 on PyPIExists and can be installedmatchesPyPI · 2026-10-06

Can it be installed, and is it up to date?

Version pin · advisories

Listed version

Registry lists
1.0.1
Latest stable
1.0.2
Status
behind the latest release (1 releases, 9 days)
Withdrawn
no

Source: pypi.org · 2026-10-06. About the version the registry lists; a manual install may resolve to a different one.

Dependency advisories

critical0high0moderate0low0

Counted in the full dependency tree as resolved on 2026-10-08 (OSV.dev). Bars share one scale. The package itself has no known vulnerability (OSV.dev).

Integrity, provenance, license

Integrity
sha256-ce44451ec973e49ba…
License
Apache-2.0

Source: the package registry · 2026-10-06.

Usage

Downloads
317 in the last month

Source: pypistats.org · 2026-10-06.

Choosing

Common questions about io.github.CSOAI-ORG/delboy-mcp

Answered from the data above

Has io.github.CSOAI-ORG/delboy-mcp been security tested?

Partly. 2 of the 12 checks that apply to it were exercised. We started the package in an isolated sandbox and read what it declares, but this test round was read-only, so its tools were not called. No security verdict is published before verification.

Is the listed version current?

No. The registry lists 1.0.1; the latest stable release on PyPI is 1.0.2.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified
finance-and-payments
AI-classified · 2026-10-08
Pricing modelAI-classified
not checked
no website in the registry entry
Programming language
does not apply
no existing GitHub repository (server declares no repository link, so there is nothing to fetch)
Hosting type
local package
registry · 2026-10-04
MCP capability
logging, prompts, resources, tools
our test · 2026-10-08
Transport
standard input/output
registry · 2026-10-04
Required credentials
none declared
registry · no declaration is not a guarantee
Package registry
pypi
registry · 2026-10-04
Freshness
0–30 days
registry updatedAt · 2026-10-04
Lifecycle status
active
registry · 2026-10-04
License class
permissive
package registry · 2026-10-06
Integrity hash
declared (sha256)
package registry · 2026-10-06
Signature / provenance
does not apply
PyPI publishes no registry signature or attestation equivalent to npm dist.signatures
Dependency advisories
none known
OSV.dev · 2026-10-08
Popularity
317 downloads a month
package registry · 2026-10-06
Publisher signals
not stated
no readable GitHub owner to describe
Maintenance
does not apply
server declares no repository link, so there is nothing to fetch
Environment
your machine
where it runs, from the hosting type

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “io.github.CSOAI-ORG/delboy-mcp: MCP server record.” Data checked 2026-10-08. https://protocolprobe.com/mcp/servers/io.github.CSOAI-ORG/delboy-mcp

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can authorize a full test.

Write to hello@protocolprobe.com · corrections log · methodology