mcp MCP Resources

mcp offers 65 resources. A resource is data the server exposes for a client to attach as context — a file, a page, an API response — rather than an action. Each has its own page, per client.

• changelog
• concepts
• concepts/api-keys-and-sessions
• concepts/confidence-and-readings
• concepts/crypto-deposits
• concepts/data-retention-and-privacy
• concepts/how-recognition-works
• concepts/mrz-and-the-visual-zone
• concepts/reliability
• concepts/what-a-billed-scan-is
• errors/document_repeated
• errors/engine_unavailable
• errors/idempotency_conflict
• errors/idempotency_in_progress
• errors/idempotency_replay_unavailable
• errors/impersonation_read_only
• errors/insufficient_credits
• errors/internal_error
• errors/invalid_request
• errors/maintenance
• errors/not_found
• errors/payload_too_large
• errors/payment_driver_unavailable
• errors/rate_limited
• errors/rate_unavailable
• errors/registration_required
• errors/service_unavailable
• errors/topup_in_progress
• errors/unauthorized
• errors/unsupported_media_type
• errors/validation_failed
• guides
• guides/check-an-mrz
• guides/control-history-retention
• guides/get-results-without-webhooks
• guides/handle-errors
• guides/handle-non-latin-scripts
• guides/recognize-a-driver-licence
• guides/recognize-a-passport
• guides/recognize-an-id-card
• guides/retry-safely-with-idempotency
• guides/rotate-api-keys
• guides/top-up-with-crypto
• guides/track-usage-and-spend
• guides/use-the-mcp-server
• guides/work-with-result-images
• index
• reference
• reference/errors
• reference/fields
• reference/fields/languages
• reference/glossary
• reference/http-status-codes
• reference/idempotency
• reference/images
• reference/limits
• reference/mrz
• reference/response
• reference/scan-options
• reference/service-levels
• reference/versioning
• start
• start/first-recognition
• start/from-sandbox-to-live
• start/recognize-without-code

mcp also offers 4 prompts — things you invoke, where a resource is context you attach.

Read from the server itself, by connecting to it and calling resources/list on 24 September 2026. A listing does not declare its resources, so asking is the only way to know them, and this is what the server actually offers rather than what its listing claims. Names only are stored; connect the server for each resource's type and contents.