Home / MCP registry index / io.usefulapi/klippa-dochorizon
Doxis AI.dp (Klippa DocHorizon) MCP by usefulapi
io.usefulapi/klippa-dochorizon in the official MCP registry.
Endpoint https://klippa-dochorizon.usefulapi.io/mcp. Source: github.com/m190/usefulapi-mcp.
The registry describes it as: Capture invoices, receipts, IDs and bank statements with Doxis AI.dp; split, render, convert files.
We read its 30 tools on 2026-10-31. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Connect it
The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:
claude mcp add --transport http klippa-dochorizon https://klippa-dochorizon.usefulapi.io/mcp{
"mcpServers": {
"klippa-dochorizon": {
"url": "https://klippa-dochorizon.usefulapi.io/mcp"
}
}
}code --add-mcp '{"name":"klippa-dochorizon","type":"http","url":"https://klippa-dochorizon.usefulapi.io/mcp"}'Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.
Let Claude Code check servers as it adds them
With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.
claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-pluginsTools it advertises
dochorizon_get_key_info dochorizon_list_models dochorizon_list_configurations dochorizon_get_model_schema dochorizon_list_prompt_configurations dochorizon_get_prompt_schema dochorizon_capture_financial dochorizon_capture_identity dochorizon_capture_bank_statement dochorizon_capture_salary_slip dochorizon_capture_generic dochorizon_capture_einvoice dochorizon_capture_with_prompt dochorizon_submit_async_capture dochorizon_list_async_jobs dochorizon_get_async_job dochorizon_get_async_job_result dochorizon_get_async_job_logs dochorizon_delete_async_job dochorizon_document_info dochorizon_document_split dochorizon_document_render dochorizon_document_merge dochorizon_upload_file dochorizon_download_file dochorizon_validate_einvoice dochorizon_convert_einvoice dochorizon_list_einvoice_types dochorizon_search_peppol_directory dochorizon_lookup_peppol_participant
Tool changes
We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.
Fingerprint of its tools at our last full read (2026-10-31):
a324aa738ba2b703. A client can hash the tools it is served the same way and compare;
the full value and a hash per tool are in this page as JSON.
Run this server? Show the check in your README
The badge reflects the latest weekly read:
[](https://lazaretto.dev/mcp-registry/io-usefulapi-klippa-dochorizon)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.