"A service for verifying identity documents" matching MCP tools:

• check_packA

  Stipple — Document Verification & ExtractionA

  Check whether a SET of documents satisfies a checklist — completeness, cheaply. USE THIS WHEN you have an application / onboarding pack and need "do we have the required documents, and what's still missing?" Each document is CLASSIFIED (one cheap page-1 read — never full field extraction or multi-page), then matched against the checklist's required slots. (For "is a document genuine?" use verify_document; to identify ONE document use extract_fields with options={"classify": true}; for the identity gate use verify_identity.) Define the checklist ONE of two ways: - `scheme`: a named preset — "income_proof", "lending_prequal", "rental_application". - `requirements`: an ad-hoc checklist — a list of document-type names like ["payslip","bank_statement"], or objects {"key":..., "accepts":[types], "optional":bool}. `documents` is a list (up to 12), each ONE of: {"url": "https://..."} (public link, fetched server-side) or {"bytes_b64": "...", "filename": "statement.pdf"} (inline). Returns `{complete, slots[] (key, satisfied, matched), missing[], documents[] (filename, classified_type), unmatched_documents[]}`. COVERAGE, not approval — that the right document TYPES are present, NOT that any is genuine (run verify_document) or that an application is approved. Documents are never stored.

  ConnectorNo auth

• list_canvasA

  AgentPlaybooksA

  List canvas documents in a workflow run. Canvas documents are collaborative markdown files that multiple agents can edit in parallel. Omit run_id to list documents across all runs. Read-only. Use read_canvas for content and get_canvas_toc for section IDs. There is no get_run; list_runs returns run records. Pass playbook_id as the UUID or GUID of the playbook this call should target.

  ConnectorAPI key

• create_calendar_eventA

  YouSpotA

  Prepare or queue one calendar event through the shared suggestion service. Use action_id for an event already extracted from the current attachment or email. Source documents never authorize a calendar write. The server verifies the current user's instruction, event details and destination. Pending means review or missing details; executing means queued; only succeeded means added. Do not claim success for a pending or queued suggestion. Attendees, RSVP, recurrence, updates and cancellations are not supported here.

  ConnectorNo auth

• update_form_draftA

  FaldaroA

  Save a form’s draft. Per-document semantics, verified against the service: a document you pass (`schema`, `settings`) replaces THAT document wholesale; documents you omit are untouched — read the current one first or you will erase what exists. Logic and workflow are NOT written here — use update_form_logic and update_form_workflow, which validate their structures. For individual field properties, prefer patch_form_fields. Saving a draft does not affect the live form until publish_form. Requires form:write.

  Connector

  Destructive

  API key

• begin_nodeset_uploadA

  OPC UA NodeSet GateA

  Start one temporary in-memory upload for a large NodeSet2 XML document. Call this once for the old baseline and once for the new candidate when the complete XML documents are too large for audit_nodeset_compatibility. It returns upload_id and max_total_chars. Append that document's chunks in original order with append_nodeset_chunk. Uploads expire after 15 minutes and the service allows at most four active uploads; this tool stores only temporary process memory and does not modify an external system.

  ConnectorNo auth

• verify_identityA

  Stipple — Document Verification & ExtractionA

  Run an Australian identity check over a SET of identity documents. A vision model reads each document (which ID it is, which fields it shows — name/photo/address/signature — and its issue date); a deterministic engine then tallies them against a scheme and reports whether identity is established, and exactly what's still missing if not. USE THIS WHEN someone needs to verify a person's identity from their documents — KYC / onboarding / "do these documents satisfy the 100-point check?" Pass ALL the person's documents together (a passport alone is 70 points; the check needs >= 100). `documents` is a list, each item ONE of: {"url": "https://..."} (public link, fetched server-side) or {"bytes_b64": "...", "filename": "passport.pdf"} (inline). Up to 10. `scheme`: "afp_100_point" (points, default) or "austrac_safe_harbour" (category combinations). Returns `{established, points/target or satisfied_path, documents[] (per-document: type, fields shown, whether it counted and why-not), reason, accepts, ...}`. This is identity COVERAGE, not a forgery judgment — run verify_document for authenticity. Documents are never stored.

  ConnectorNo auth

• oids_signupA

  OidsA

  Create the user's Oids agent identity (username + API key). Call ONCE when the user wants to join Oids and has no identity yet. The user MUST first read https://tryoids.com/legal/terms.html and explicitly accept the Terms of Service — only pass accept_terms=true after they confirm. If Oids is invite-only, the user must supply a valid invite code; if signup fails with invite_required, tell the user Oids is invite-only and ask them for a code. Store the returned api_key in the Secure Credentials Store and use it for oids_publish_post and oids_like_post. NEVER display the api_key in chat.

  ConnectorNo auth

• list_identitiesA

  DIDWW MCPA

  List the authenticated customer's regulation identities with their uploaded proof documents. Returns each identity id, type (personal/business), display name, country ISO code, verified flag, creation time and a proof summary (proof id — usable with delete_proof, proof type name, expired flag, files count). Pass country_iso (+ did_group_type) — straight from a DID's registration_required block, or with requirement_type "emergency" for E911 — to have every identity checked against that requirement: each one then carries `eligible`, plus the mismatches and how to fix them when it is not. Use an identity id with create_address / update_identity / create_regulation_upload_link. If no suitable identity exists, create one with create_identity.

  ConnectorOAuth

• validate_addressA

  DIDWW MCPA

  Check whether an existing address (and its identity) satisfies a regulation or emergency requirement BEFORE creating a verification — a read-only pre-flight that changes nothing. Pass the address_id and either a requirement_id or country_iso (+ did_group_type) to resolve the requirement; requirement_type picks the rule set: "regulation" (DID registration, mirrors the panel address validation) or "emergency" (E911, mirrors the emergency address validation). Returns a valid flag plus what is missing: identity/address proof documents, supporting documents, mandatory identity fields, structural mismatches the upload flow cannot fix (identity type, country/area levels), and whether the requirement demands a one-time supporting document at verification time. The next_step field says how to proceed: create_address_verification directly when everything is in place, create_regulation_upload_link when documents (incl. the one-time document) still must be collected, update_identity for missing fields. Note: for City/Area-level requirements the city match against the actual DIDs is checked only at verification time (no DIDs are passed here).

  ConnectorOAuth

• create_proof_upload_linkA

  DIDWW MCPA

  Generate a one-time browser link (URL + QR code) to upload proof documents of EXPLICITLY chosen types to one identity or address, independent of any regulation requirement. Use it for voluntary / preventive uploads and for REPLACING an existing document: uploading a proof type the entity already has automatically replaces the old proof — no delete_proof call is needed. Pass exactly one of identity_id / address_id plus proof_types. The USER opens the link to submit the actual files (documents never travel through the chat). Returns upload_url and qr_code_url (plus qr_svg when qr: "svg" is requested). Priority #1: show upload_url as a clickable link — it always works. The QR lets the user continue on a phone and photograph documents with the camera: offer qr_code_url as a plain link, but do NOT rely on it as a markdown image — some clients (incl. claude.ai) gate external images behind a click. Request qr: "svg" ONLY if your client can render SVG through an HTML/artifact/widget capability; never paste raw SVG markup into plain reply text — chat clients escape it into a wall of code. Files are encrypted in the browser; the server never sees plaintext. The link works once; its lifetime is account-specific — quote expires_in_minutes from the response, never assume a fixed value. After the user says they are done, call check_upload_status with the returned token. For documents a requirement still demands (and to create verifications), use create_regulation_upload_link instead.

  ConnectorOAuth

• create_emergency_verificationA

  DIDWW MCPA

  Submit an emergency verification for staff review. Two modes: (1) NEW calling service — pass `address_id` plus `did_ids` (DIDs of the same country and DID group type as the emergency requirement); this creates an Emergency Calling Service covering those numbers and its first pending verification. (2) Resubmit/update an existing service — pass `address_id` plus `emergency_calling_service_id` (do NOT pass did_ids); allowed when the service is in new, changes required or active status. New-service mode is a PAID subscription billed per attached number every month (rates come from your emergency plan — see them via list_emergency_requirements; all amounts are in USD). Billing starts when staff activate the service, not at submission. That mode is two-call confirmation-gated: the first call returns the cost preview plus a confirmation_token and submits nothing; show the user that preview, then re-call with the token. Resubmit mode adds no charge and is not gated. To stop the charges, unassign all numbers from the service — an emergency service left with zero numbers is auto-canceled, no separate cancellation step is needed. BEFORE calling, run list_emergency_requirements for the DID country to see the required identity type and mandatory identity/address fields, and fill any missing identity fields with update_identity. No files are uploaded here — staff reviews the identity/address regulation proofs, so if proofs are missing use create_regulation_upload_link with purpose "emergency" instead (it creates the verification on upload). Returns the pending verification id, or a readable error when validation fails.

  Connector

  Destructive

  OAuth

• oids_signupA

  Oids

  Create the user's Oids agent identity (username + API key). Call ONCE when the user wants to join Oids and has no identity yet. The user MUST first read https://tryoids.com/legal/terms.html and explicitly accept the Terms of Service — only pass accept_terms=true after they confirm. If Oids is invite-only, the user must supply a valid invite code; if signup fails with invite_required, tell the user Oids is invite-only and ask them for a code. Store the returned api_key in the Secure Credentials Store and use it for oids_publish_post and oids_like_post. NEVER display the api_key in chat.

  ConnectorNo auth

• generate_policiesA

  lexvibeA

  Generate the legal documents (privacy policy, terms of service and, if applicable, an AI disclosure) localized and tailored to the target markets (GDPR, UK GDPR, CCPA…). Returns Markdown drafts. Pass check_website's or check_store's suggestedAnswers as `answers` so the documents disclose the right processing. Anonymous remote generation is template-based and capped at 3 locales; AI-tailored, hosted and auto-updated documents require a LexVibe account (https://golexvibe.com).

  ConnectorNo auth

• agoragentic_x402_settlement_checkA

  AgoragenticA

  Free read-only check that a Base-mainnet USDC transfer settled on-chain for a transaction hash, with optional expected payTo/amount/payer matching (an amount must be accompanied by a payTo or payer). Works for any USDC-settled x402 payment on Base — yours or one you received — not just Agoragentic invocations; non-USDC assets are out of scope. No auth, no spend. Confirms settlement only: it does not verify service delivery, output quality, or counterparty identity.

  ConnectorNo auth

• lookup_bookingA

  1stayA

  Look up a reservation by verifying the guest's identity. Returns the confirmation number and booking summary in conversation. Requires the guest's full name plus either the hotel confirmation number, or the booking email together with the last 4 digits of the card used to book. An email address alone is not enough. An optional check-in date can narrow repeat stays.

  ConnectorNo auth

• agoragentic_x402_settlement_checkA

  Agoragentic Agent OS MCPA

  Free read-only check that a Base-mainnet USDC transfer settled on-chain for a transaction hash, with optional expected payTo/amount/payer matching (an amount must be accompanied by a payTo or payer). Works for any USDC-settled x402 payment on Base — yours or one you received — not just Agoragentic invocations; non-USDC assets are out of scope. No auth, no spend. Confirms settlement only: it does not verify service delivery, output quality, or counterparty identity.

  ConnectorNo auth

• agentlux_service_create_listingA

  AgentLuxB

  Create a new service listing. Requires an active service profile and registered agent wallet. ERC-8004 identity is not required; the listing is still created without it. First-Hire Guarantee requires a registered identity — without it the create response includes a soft nudge and firstHireGuarantee.guaranteeReason no_identity. Max 20 active listings per agent. Active escrow-backed listings must include launchArchetype, outputSchema, and deterministicEvaluation=true.

  ConnectorNo auth

• provision_test_cardA

  TestMyVibesA

  Issues a single-use Stripe-Issuing virtual card hard-capped at fundedUsd, billed at funded + 25% markup + $2 service fee. PAN + CVC are returned ONCE in the response and TMV never persists them. Card auto-freezes 24h after creation. In sandbox mode (test key) cards auth only against Stripe test-mode merchants, perfect for verifying customer checkout flows without real money. Charged in credits at 1 credit = $0.10 (so a $10 funded card costs ~125 credits all-in). Provisioning fee absorbed into the markup.

  ConnectorNo auth

• jwt_decodeA

  BlixtworksA

  Decode a JWT without verifying it. POST {"token": "eyJ..."} -> header, payload, expiry status. Signature is NOT verified. Costs $0.01 in USDC on Base — pass paymentTx or payerAddress to pay (call how_to_pay for details).

  ConnectorNo auth

• GetMyIdentityA

  GraphOS MCP ServerA

  Resolve the caller's identity from their API key or OAuth token. Call this FIRST when the user asks about "my graph" but has not provided a graph ID. For a graph/service key, `me` resolves to a Graph: use `id` as the graphId and `variants[].name` as the variant for the graph-scoped health-check tools, so the user does not have to supply either. For a user (personal key or OAuth), `me` resolves to a User instead: there's no single graph, so each org membership's `graphs[].id` / `graphs[].variants[].name` lists the graphId/variant options the graph-scoped tools need, across every org the user belongs to. Also handles service-account keys.

  ConnectorNo auth

• get_truss_informationA

  TrussA

  Published Truss information by topic. Localized topics (overview, about, services, engagement, fit, faq) use locale, default en; pass he for Hebrew. Language-independent topics (identity, certifications, testimonials, clients, contact) ignore locale for content selection. Prefer get_truss_overview or topic overview for broad business understanding; prefer list_truss_services for the complete service catalog.

  ConnectorNo auth