com.docimprint/api
REMOTE · API.DOCIMPRINT.COM
AI document intelligence: extract, summarize, claim-check, notarize, and signed action receipts.
Available components
Last scanned (12 hours ago)
Scores higher than 86% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Documents and Files
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
- Authorisation is enforced on tool calls, but the challenge carries 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 401, 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 & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability81
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 4847 tokens (~230/item across 21 items; 21 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 21 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 21 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 (12)
- TLS certificate
- Authorization
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
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 401, which proves neither a plaintext path nor enforcement.
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.
- 11 Nov 26 0
- Stability: 0.97 → pass security
- 10 Nov 26 0
- Stability: pass → 0.97 functional
- 6 Nov 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
- 5 Nov 26 0
- Stability: 0.97 → pass security
- 4 Nov 26 0
- Stability: pass → 0.97 functional
- 30 Oct 26 +14
- Stability: fail → pass ▲ security
- 30 Sept 26 0
- Stability: pass → fail ▼ security
- Tool “job.status” was removed ▼ security
- Tool “receipt.list” was removed ▼ security
- Tool “receipt.verify” was removed ▼ security
- Tool “account.quota” was removed ▼ security
- Tool “bundle.get” was removed ▼ security
- Tool “bundle.notarize” was removed ▼ security
- Tool “bundle.verify” was removed ▼ security
- Tool “collection.add_document” was removed ▼ security
- Tool “collection.ask” was removed ▼ security
- Tool “collection.create” was removed ▼ security
- Tool “collection.list” was removed ▼ security
- Tool “collection.search” was removed ▼ security
- Tool “document.check_claims” was removed ▼ security
- Tool “document.extract_structured” was removed ▼ security
- Tool “document.extract_tables” was removed ▼ security
- Tool “document.extract_text” was removed ▼ security
- Tool “document.parse_invoice” was removed ▼ security
- Tool “document.summarize” was removed ▼ security
- Tool “url.extract” was removed ▼ security
- Tool “url.qa” was removed ▼ security
- Tool “url.summarize” was removed ▼ security
- Tool “url.translate” was removed ▼ security
- Server version: 1.0.6 → 1.0.0 functional
- New tool “add_document_to_collection” functional
- New tool “ask_collection” functional
- New tool “check_claims” functional
- New tool “create_collection” functional
- New tool “extract_structured” functional
- New tool “extract_tables” functional
- New tool “extract_text” functional
- New tool “extract_url” functional
- New tool “get_bundle” functional
- New tool “get_job_status” functional
- New tool “get_quota” functional
- New tool “list_collections” functional
- New tool “notarize_bundle” functional
- New tool “parse_invoice” functional
- New tool “qa_url” functional
- New tool “search_collection” functional
- New tool “summarize_document” functional
- New tool “summarize_url” functional
- New tool “translate_url” functional
- New tool “verify_action_receipt” functional
- New tool “verify_bundle” functional
- 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
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://api.docimprint.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=docimprint.com | CN=WE1,O=Google Trust Services,C=US | 2 Oct 2026 | 31 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | b22802e140e03af10e585b102257451a |
| SANs: docimprint.com, api.docimprint.com, *.api.docimprint.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.docimprint.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| docimprint.com. | 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 tool calls |
| HTTP status | 200 |
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://api.docimprint.com/mcp | Verified | 200 | |
| http (plaintext) | http://api.docimprint.com/mcp | Inconclusive | 401 |
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 →
add_document_to_collection Add Document to Collection ~287
Add an evidence bundle to a collection and trigger async vector indexing. Use after create_collection to populate a collection with documents. Once indexed, documents become searchable via search_collection and ask_collection. Indexing is async — poll get_job_status with the returned job_id until status is "complete". PREREQUISITE: Bundle must have status "complete" (check with get_bundle). Collection must be owned by your API key. Returns: { collection_id, bundle_id, job_id (poll for indexing completion) } Example prompts: - "Add my contract bundle ev_550e8400 to the Q4 Contracts collection." - "Put this evidence bundle into my Due Diligence Docs collection for search." - "Add document [bundle_id] to collection [col_id] with a title."
| Name | Type | Req | Description |
|---|---|---|---|
| bundle_id | string | yes | Evidence bundle ID (ev_...) to add. Bundle must have status "complete". Example: "ev_550e8400-e29b-41d4-a716-446655440000" |
| collection_id | string | yes | Collection ID (col_...) returned by create_collection. Example: "col_550e8400-e29b-41d4-a716-446655440000" |
| title | string | – | Optional display title for the document in this collection. Example: "Q4 2025 Financial Report" |
| Name | Type | Req | Description |
|---|---|---|---|
| bundle_id | string | yes | – |
| collection_id | string | yes | – |
| job_id | string | yes | – |
| receipt | – | yes | – |
No examples provided.
ask_collection Ask Collection ~273
Answer a question using RAG over a document collection. Retrieves relevant chunks then synthesizes a cited answer with source attribution. Use when you need a direct answer grounded in your collection documents. For raw matching chunks (without synthesis), use search_collection instead. For single-document Q&A, use qa_url instead. PREREQUISITE: Collection must be populated via add_document_to_collection and indexed before results appear. Returns: { answer: string, sources: [{ bundle_id, chunk_id }], retrieval: [{ bundle_id, chunk_id, text, score }] } Example prompts: - "What are the key terms of the service agreement in my collection?" - "Based on my due diligence docs, what are the main risks?" - "Answer this question using all documents in the Q4 Contracts collection."
| Name | Type | Req | Description |
|---|---|---|---|
| collection_id | string | yes | Collection ID (col_...) returned by create_collection. Example: "col_550e8400-e29b-41d4-a716-446655440000" |
| max_chunks | number | – | Max chunks to retrieve for context (default 8). Increase for broad questions, decrease for precision. Example: 12 |
| question | string | yes | Natural language question to answer from collection documents. Example: "What are the key terms of the service agreement?" |
| Name | Type | Req | Description |
|---|---|---|---|
| answer | object | yes | – |
| retrieval | array | yes | – |
| sources | array | yes | – |
No examples provided.
check_claims Check Claims ~296
Verify a list of factual claims against document text. Uses a quality AI model with citation-level evidence. Use after extract_text or extract_url when you need to validate specific factual assertions. For open-ended questions about a document, use qa_url instead. For multi-document investigation, use ask_collection. Typical workflow: extract_text/extract_url → check_claims. Returns: { claims: [{ claim, status: "supported"|"contradicted"|"not_found", evidence: { quote, paragraphs[] }, confidence: "high"|"medium"|"low" }], truncated: boolean } Example prompts: - "Check whether this contract mentions a liability cap of $1M." - "Verify these claims against the document: [claims list]." - "Does the report actually say revenue grew 23%?"
| Name | Type | Req | Description |
|---|---|---|---|
| claims | array | yes | Factual statements to verify. Each claim is checked independently against the text. Example: ["Founded in 2010", "Revenue exceeded $1M"] |
| max_tokens | number | – | Input length cap (1 token ≈ 4 chars). Default ~3000 tokens. Truncates input text, not the output. Example: 4000 |
| text | string | yes | Document text to check claims against. Obtain via extract_text or extract_url. Example: "ACME Corp was founded in 2010. Revenue exceeded $1M in 2024." |
| Name | Type | Req | Description |
|---|---|---|---|
| claims | array | yes | – |
| truncated | boolean | yes | – |
No examples provided.
create_collection Create Collection ~168
Create a named document collection for cross-document semantic search and RAG-based Q&A. Free — no credits consumed. Use when you want to group related evidence bundles for unified search (search_collection) or question answering (ask_collection). NOTE: Collections start empty. Add evidence bundles with add_document_to_collection. Indexing is async — once complete, use search_collection or ask_collection. Returns: { collection_id: string (col_...), name: string } Example prompts: - "Create a collection called Q4 Contracts for my quarterly reports." - "Set up a new document group named Due Diligence Docs." - "Make a collection to organize my vendor agreements."
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Human-readable collection name. Example: "Q4 Contracts" or "Due Diligence Docs" |
| Name | Type | Req | Description |
|---|---|---|---|
| collection_id | string | yes | – |
| name | string | yes | – |
No examples provided.
extract_structured Extract Structured Data ~347
Extract typed fields from document text using a caller-defined schema. Uses a quality AI model with retry logic. Use when you need specific data points from a document rather than full text. For invoices with known fields, parse_invoice (prebuilt schema) may be simpler. For general summarization, use summarize_document instead. Schema format: { "field_name": "type hint or description" } — e.g. { "contract_date": "ISO date", "party_a": "string", "penalty_usd": "number" }. Returns: { data: { <field>: value }, data_cited: { <field>: { value, confidence: "high"|"medium"|"low", citations: [{ quote, paragraphs[] }] } } } Example prompts: - "Extract the contract date, parties, and penalty amount from this agreement." - "Pull the vendor name, PO number, and total from this document." - "Get me all named fields from this form using my custom schema."
| Name | Type | Req | Description |
|---|---|---|---|
| max_tokens | number | – | Input length cap (1 token ≈ 4 chars). Default ~2500 tokens. Truncates input, not output. Example: 3000 |
| schema | object | yes | Field map: describe each field you want extracted with a type hint. Example: { "total_usd": "number", "vendor": "string", "invoice_date": "ISO date YYYY-MM-DD" } |
| text | string | yes | Document text to extract from. Obtain via extract_text or extract_url. Example: "This Service Agreement is entered into on 2025-03-15 between ACME Corp and Beta Inc..." |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | – |
| data_cited | object | yes | – |
No examples provided.
extract_tables Extract Tables ~194
Extract tables and forms as Markdown from a PDF or image (base64-encoded). Use when the document contains structured tabular data such as financial statements, data sheets, or forms. For plain prose documents, use extract_text instead. Returns: { pages: number, text: string } — text contains Markdown-formatted tables. Example prompts: - "Extract the tables from this financial statement." - "Pull the data table from this PDF into Markdown format." - "Get the tabular data from this form document."
| Name | Type | Req | Description |
|---|---|---|---|
| document_base64 | string | yes | Base64-encoded PDF or image bytes (max ~15 MB). Example: "JVBERi0xLjcNJeLjz9MNCj..." (truncated PDF base64) |
| mime_type | string | yes | MIME type of the document. Example: "application/pdf" for PDF bank statements, "image/jpeg" for photo of a form. |
| Name | Type | Req | Description |
|---|---|---|---|
| pages | number | yes | – |
| text | string | yes | – |
No examples provided.
extract_text Extract Text ~191
Extract plain text from a PDF or image (base64-encoded). Use when you need raw text for downstream AI analysis (summarization, claim checking, structured extraction). For documents at a public URL, use extract_url instead (no base64 encoding needed). Returns: { pages: number, text: string } Example prompts: - "Extract the text from this scanned contract so I can search it." - "Give me the raw text from this PDF document." - "OCR this image and return the text content."
| Name | Type | Req | Description |
|---|---|---|---|
| document_base64 | string | yes | Base64-encoded PDF or image bytes (max ~15 MB). Example: "JVBERi0xLjcNJeLjz9MNCj..." (truncated PDF base64) |
| mime_type | string | yes | MIME type of the document. Example: "application/pdf" for PDFs, "image/png" for PNG screenshots. |
| Name | Type | Req | Description |
|---|---|---|---|
| pages | number | yes | – |
| text | string | yes | – |
No examples provided.
extract_url Extract Text from URL ~172
Fetch a public HTTPS URL and return extracted text and page metadata. Lean mode — no evidence bundle stored, no bundle_id returned. Use for raw text extraction from web pages and online documents. Use summarize_url for summaries, qa_url for Q&A, translate_url for translation, extract_text for base64 file uploads. Returns: { url, title, word_count, text, final_url (after redirects) } Example prompts: - "Extract the text from https://example.com/report.pdf for me." - "Get me the raw content of this web page: [URL]." - "Pull the text from this online article so I can analyze it."
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Public HTTPS URL to fetch and extract. Example: "https://example.com/report.pdf" or "https://blog.example.com/article" |
| Name | Type | Req | Description |
|---|---|---|---|
| final_url | string | – | – |
| text | string | yes | – |
| title | string | – | – |
| url | string | yes | – |
| word_count | number | – | – |
No examples provided.
get_bundle Get Evidence Bundle ~242
Retrieve metadata for an evidence bundle (ev_...) owned by your API key. Free — no credits consumed. Use for quick status/metadata lookups such as checking if a bundle is complete, finding its notarization status, or viewing retention/legal hold info. For deep cryptographic integrity verification (hash + signature + artifact checks), use verify_bundle instead. Returns: { bundle_id, source_url, mode, status: "pending"|"complete"|"failed", manifest_sha256, manifest_signature, signer_address, attestation_tx, attestation_at, eas_uid, parent_bundle_id, superseded_by, legal_hold: boolean, retention_until, created_at } Example prompts: - "Show me the metadata for bundle ev_550e8400." - "Check the status and notarization info of my evidence bundle." - "Get me the details of bundle [ev_id] — is it complete?"
| Name | Type | Req | Description |
|---|---|---|---|
| bundle_id | string | yes | Evidence bundle ID (ev_...) returned by extract or notarize_bundle. Example: "ev_550e8400-e29b-41d4-a716-446655440000" |
| Name | Type | Req | Description |
|---|---|---|---|
| attestation_at | – | yes | – |
| attestation_tx | – | yes | – |
| bundle_id | string | yes | – |
| created_at | string | yes | – |
| eas_uid | – | yes | – |
| legal_hold | boolean | yes | – |
| manifest_sha256 | – | yes | – |
| manifest_signature | – | yes | – |
| mode | string | yes | – |
| parent_bundle_id | – | yes | – |
| receipt | – | yes | – |
| retention_until | – | yes | – |
| signer_address | – | yes | – |
| source_url | string | yes | – |
| status | string | yes | – |
| superseded_by | – | yes | – |
No examples provided.
get_job_status Get Job Status ~266
Poll the status of an async job (extract, indexing, batch). Free — no credits consumed. Use after add_document_to_collection or async extract to check when processing completes. Poll this endpoint in a loop until status is "complete" or "failed". Completed jobs include the bundle_id or result_json in the response. Jobs are created when you POST /v1/extract with a webhook, or when add_document_to_collection triggers async indexing. Returns: { id, type: "extract"|"extract_batch"|"index_collection", status: "queued"|"processing"|"complete"|"failed"|"cancelled", progress_pct: number (0–100), progress_message, bundle_id (when complete), result_json (when complete), error (when failed), created_at, completed_at } Example prompts: - "Check the status of my indexing job job_550e8400." - "Is my async extract job done yet?" - "Poll job [job_id] — what is the current progress?"
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | Job ID (job_...) returned by async extract or add_document_to_collection. Example: "job_550e8400-e29b-41d4-a716-446655440000" |
| Name | Type | Req | Description |
|---|---|---|---|
| bundle_id | – | yes | – |
| collection_id | – | yes | – |
| completed_at | – | yes | – |
| created_at | string | yes | – |
| error | – | yes | – |
| id | string | yes | – |
| progress_message | – | yes | – |
| progress_pct | number | yes | – |
| result_json | – | yes | – |
| status | string | yes | – |
| type | string | yes | – |
No examples provided.
get_quota Get Quota ~132
Get current credit balance and plan details for your API key. Free — no credits consumed. Check this before running credit-consuming operations (extract, summarize, etc.) to avoid QUOTA_EXCEEDED errors. Returns plan tier, billing period, and usage breakdown. Returns: { plan_id, billing_period (YYYY-MM), credits_used, credits_limit, credits_remaining, status: "active"|"suspended" } Example prompts: - "How many credits do I have left this month?" - "Check my current quota and plan status." - "Am I going to hit my credit limit soon?"
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| billing_period | string | yes | – |
| credits_limit | number | yes | – |
| credits_remaining | number | yes | – |
| credits_used | number | yes | – |
| plan_id | string | yes | – |
| status | string | yes | – |
No examples provided.
list_collections List Collections ~134
List all document collections owned by your API key. Free — no credits consumed. Use before search_collection or ask_collection when you need the collection ID. Supports pagination with limit and offset. Returns: { collections: [{ id, name, created_at }] } Example prompts: - "List all my document collections." - "Show me the collections I have created." - "What collections do I own? List them."
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max collections to return (default 50, max 100). Example: 20 |
| offset | number | – | Pagination offset (default 0). Example: 0 |
| Name | Type | Req | Description |
|---|---|---|---|
| collections | array | yes | – |
No examples provided.
notarize_bundle Notarize Bundle On-Chain ~277
Notarize an evidence bundle on-chain by writing its manifest SHA-256 to the blockchain (Base/EVM). Creates a permanent, tamper-evident on-chain record of the document fingerprint. If the bundle is already notarized, returns the existing attestation immediately (idempotent). Use when you need an immutable on-chain timestamp proving a document existed at a point in time. For quick integrity checks without on-chain cost, use verify_bundle instead. PREREQUISITE: Bundle status must be "complete". Check status with get_bundle first. NOTE: Costs gas (ETH). The on-chain record is permanent and cannot be deleted even if the bundle is later purged. Returns: { bundle_id, attestation: { tx_hash, network, attested_at, key_id, eas_uid?, schema_uid? } } Example prompts: - "Notarize bundle ev_550e8400 on-chain so I have a permanent record." - "Put the fingerprint of my evidence bundle on the blockchain." - "Create an on-chain timestamp for this document bundle."
| Name | Type | Req | Description |
|---|---|---|---|
| bundle_id | string | yes | Evidence bundle ID (ev_...) to notarize. Bundle must have status "complete". Example: "ev_550e8400-e29b-41d4-a716-446655440000" |
| Name | Type | Req | Description |
|---|---|---|---|
| attestation | object | yes | – |
| bundle_id | string | yes | – |
| receipt | – | yes | – |
No examples provided.
parse_invoice Parse Invoice ~238
Parse a receipt or invoice document into structured fields. Uses a quality AI model for accuracy. Use when you need to extract line items, totals, and merchant info from financial documents. For general document text, use extract_text instead. Returns: { invoice: { merchant, date (YYYY-MM-DD), line_items[], subtotal, tax, total }, cited: { <field>: { value, confidence: "high"|"medium"|"low", citations: [{ quote, paragraphs[] }] } } } Example prompts: - "Parse this invoice and give me the line items and total." - "Extract the merchant, date, and amounts from this receipt." - "Read this scanned invoice and return structured data."
| Name | Type | Req | Description |
|---|---|---|---|
| document_base64 | string | yes | Base64-encoded PDF or image of the receipt/invoice (max ~15 MB). Example: "JVBERi0xLjcNJeLjz9MNCj..." (base64-encoded invoice PDF) |
| mime_type | string | yes | MIME type of the document. Example: "application/pdf" for scanned invoice PDF, "image/jpeg" for a receipt photo. |
| Name | Type | Req | Description |
|---|---|---|---|
| cited | object | yes | – |
| invoice | object | yes | – |
No examples provided.
qa_url Ask a Question About a URL ~230
Fetch a public HTTPS URL and answer a specific question about its content. Lean mode — no bundle stored. Use when you have a precise question about a web page. For a broad summary, use summarize_url. For multi-document Q&A, use ask_collection instead. Returns: { url, answer, answer_cited: { value, confidence, citations[] }, confidence: "high"|"medium"|"low", truncated } Example prompts: - "What is the refund policy at https://docs.example.com/policy?" - "Look at [URL] and tell me what the delivery terms are." - "Answer this question based on the content of [URL]: [question]."
| Name | Type | Req | Description |
|---|---|---|---|
| max_tokens | number | – | Input length cap (1 token ≈ 4 chars). Truncates fetched page content, not the answer. Example: 4000 |
| question | string | yes | Specific question to answer from the page content. Example: "What is the refund policy?" |
| url | string | yes | Public HTTPS URL to fetch and question. Example: "https://docs.example.com/policy" |
| Name | Type | Req | Description |
|---|---|---|---|
| answer | string | – | – |
| answer_cited | object | – | – |
| confidence | string | – | – |
| truncated | boolean | yes | – |
| url | string | yes | – |
No examples provided.
search_collection Search Collection ~246
Semantic (vector) search across documents in a collection. Returns ranked text chunks with relevance scores. Free — no credits consumed. Use when you need raw matching chunks from a collection. For a synthesized cited answer from the same context, use ask_collection instead. PREREQUISITE: Collection must be populated via add_document_to_collection and async indexing must complete (poll get_job_status) before results appear. Returns: { results: [{ bundle_id, chunk_id, text, score: number (0–1), title? }] } Example prompts: - "Search my Q4 Contracts collection for mentions of liability cap." - "Find the clause about data retention in my due diligence docs." - "Search for revenue numbers across my quarterly reports."
| Name | Type | Req | Description |
|---|---|---|---|
| collection_id | string | yes | Collection ID (col_...) returned by create_collection. Example: "col_550e8400-e29b-41d4-a716-446655440000" |
| limit | number | – | Max chunks to return (default 10, max 50). Example: 5 |
| query | string | yes | Natural language search query. Example: "What were the revenue numbers for Q4?" |
| Name | Type | Req | Description |
|---|---|---|---|
| results | array | yes | – |
No examples provided.
summarize_document Summarize Document ~258
Summarize document text into a prose summary and key points with citations. Use after extract_text or extract_url when you need a condensed understanding of a long document. For single-sentence Q&A, use qa_url instead. For extracting specific fields, use extract_structured. Typical workflow: extract_text/extract_url → summarize_document. Returns: { summary: string, key_points: string[], summary_cited: { value, confidence, citations[] }, key_points_cited: [{ text, citations[] }], truncated: boolean, strategy: "full"|"truncated"|"chunked" } Example prompts: - "Summarize this financial report and give me the key points." - "What are the main takeaways from this document?" - "Give me a concise summary of this 50-page report."
| Name | Type | Req | Description |
|---|---|---|---|
| max_tokens | number | – | Input length cap (1 token ≈ 4 chars). Default ~3000 tokens. Truncates input, not output. Example: 4000 |
| text | string | yes | Document text to summarize. Obtain via extract_text or extract_url. Example: "The Q4 2025 financial report shows revenue growth of 23% year-over-year..." |
| Name | Type | Req | Description |
|---|---|---|---|
| key_points | array | yes | – |
| key_points_cited | array | yes | – |
| strategy | string | yes | – |
| summary | string | yes | – |
| summary_cited | object | yes | – |
| truncated | boolean | yes | – |
No examples provided.
summarize_url Summarize URL ~198
Fetch a public HTTPS URL and return a prose summary with key points. Lean mode — no bundle stored. Use when you need a condensed understanding of a web page. For raw text, use extract_url. For asking a specific question about a page, use qa_url. Returns: { url, summary, key_points: string[], truncated: boolean, word_count } Example prompts: - "Summarize https://en.wikipedia.org/wiki/Artificial_intelligence for me." - "Give me the key points from this blog post: [URL]." - "What is this article about? Summarize [URL]."
| Name | Type | Req | Description |
|---|---|---|---|
| max_tokens | number | – | Input length cap (1 token ≈ 4 chars). Truncates fetched page content, not the output summary. Example: 4000 |
| url | string | yes | Public HTTPS URL to fetch and summarize. Example: "https://en.wikipedia.org/wiki/Artificial_intelligence" |
| Name | Type | Req | Description |
|---|---|---|---|
| key_points | array | – | – |
| summary | string | – | – |
| truncated | boolean | yes | – |
| url | string | yes | – |
| word_count | number | – | – |
No examples provided.
translate_url Translate URL ~219
Fetch a public HTTPS URL and return its content translated into a target language. Lean mode — no bundle stored. Use when you need to understand web content in a different language. For extracting raw untranslated text, use extract_url instead. Returns: { url, translated_text, target_lang, truncated } Example prompts: - "Translate https://example.de/artikel into English for me." - "Translate this German article into Spanish: [URL]." - "Fetch [URL] and give me the French translation."
| Name | Type | Req | Description |
|---|---|---|---|
| max_tokens | number | – | Input length cap (1 token ≈ 4 chars). Truncates fetched page content before translation. Example: 4000 |
| target_lang | string | yes | ISO 639-1 language code for the target language. Example: "es" for Spanish, "fr" for French, "de" for German, "ja" for Japanese, "zh" for Chinese |
| url | string | yes | Public HTTPS URL to fetch and translate. Example: "https://example.de/artikel" |
| Name | Type | Req | Description |
|---|---|---|---|
| target_lang | string | yes | – |
| translated_text | string | – | – |
| truncated | boolean | yes | – |
| url | string | yes | – |
No examples provided.
verify_action_receipt Verify Action Receipt ~242
Independently verify a signed action receipt (rcpt_...) returned by get_bundle, verify_bundle, notarize_bundle, or add_document_to_collection. Free — no credits consumed. Proves both that the receipt signature is authentic AND that the manifest_sha256 it was bound to still matches the bundle's current manifest — i.e. that the action was not performed against a stale or since-superseded document. Use for third-party audit of an agent's prior actions. Returns: { receipt_id, valid: boolean, signature_valid: boolean, manifest_matches_current: boolean, bundle_id, agent_id, action, manifest_sha256, signer_address, signed_at, tampered: string[] } Example prompts: - "Verify action receipt rcpt_550e8400 is authentic and still current." - "Was this receipt signed against the real document, or a stale copy?"
| Name | Type | Req | Description |
|---|---|---|---|
| receipt_id | string | yes | Action receipt ID (rcpt_...) returned in the receipt field of another tool's response. Example: "rcpt_550e8400-e29b-41d4-a716-446655440000" |
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| agent_id | string | yes | – |
| bundle_id | string | yes | – |
| manifest_matches_current | boolean | yes | – |
| manifest_sha256 | string | yes | – |
| receipt_id | string | yes | – |
| signature_valid | boolean | yes | – |
| signed_at | string | yes | – |
| signer_address | string | yes | – |
| tampered | array | yes | – |
| valid | boolean | yes | – |
No examples provided.
verify_bundle Verify Evidence Bundle ~237
Verify the cryptographic integrity of an evidence bundle (ev_...) owned by your API key. Checks manifest hash, EIP-191 signature, and R2 artifact hashes. Free — no credits consumed. Use when you need to confirm a bundle has not been tampered with. For quick metadata lookups (without full crypto verification), use get_bundle instead. Returns: { valid: boolean, bundle_id, manifest_sha256, checks: { status, manifest_hash, signature, artifacts: [{ name, ok }] }, tampered: string[], signer_address: string|null, attestation_tx: string|null, url: string, captured_at: string } Example prompts: - "Verify the cryptographic integrity of bundle ev_550e8400." - "Is this evidence bundle still valid and untampered?" - "Deep-check the manifest hash and signature of my bundle."
| Name | Type | Req | Description |
|---|---|---|---|
| bundle_id | string | yes | Evidence bundle ID (ev_...) returned by extract or notarize. Example: "ev_550e8400-e29b-41d4-a716-446655440000" |
| Name | Type | Req | Description |
|---|---|---|---|
| attestation_tx | – | – | – |
| bundle_id | string | yes | – |
| captured_at | string | – | – |
| checks | object | yes | – |
| manifest_sha256 | – | yes | – |
| receipt | – | yes | – |
| signer_address | – | – | – |
| tampered | array | yes | – |
| url | string | – | – |
| valid | boolean | yes | – |
No examples provided.
How do I install the com.docimprint/api MCP server?
com.docimprint/api is a hosted endpoint at https://api.docimprint.com/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 · api.docimprint.com
claude mcp add --transport http com-docimprint-api 'https://api.docimprint.com/mcp'
What is the com.docimprint/api MCP server?
com.docimprint/api is an MCP server listed in the public MCP registry as com.docimprint/api. AI document intelligence: extract, summarize, claim-check, notarize, and signed action receipts. This page covers its hosted endpoint (https://api.docimprint.com/mcp).
Is the com.docimprint/api MCP server safe to use?
com.docimprint/api scores 85 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 com.docimprint/api MCP server expose?
com.docimprint/api exposes 21 tools: extract_text, extract_tables, parse_invoice, check_claims, extract_structured, and 16 more. Their descriptions and schemas cost roughly 4,847 tokens of context every time the server is loaded.
Does the com.docimprint/api MCP server require authentication?
Yes. com.docimprint/api 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 com.docimprint/api MCP server still maintained?
com.docimprint/api 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 com.docimprint/api MCP server?
VerifyMCP ran 12 checks on com.docimprint/api, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about com.docimprint/api: HTTPS. 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.