"Guidance for Writing a Complex Document and Understanding Legal Requirements" 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. Costs 3 credit(s) per call.

  ConnectorNo auth

• document.summarizeA

  apiA

  Summarize document text into a prose summary and key points with citations. Use after document.extract_text or url.extract when you need a condensed understanding of a long document. For single-sentence Q&A, use url.qa instead. For extracting specific fields, use document.extract_structured. Typical workflow: document.extract_text/url.extract → document.summarize. 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."

  ConnectorNo auth

• analyze_title_documentsA

  Curagent Title RiskA

  Analyzes Florida real estate title documents and returns a structured risk report: a risk score (0-100, higher is safer) and level, findings with verbatim evidence from the documents and guidance on how to cure each one, and the Schedule B-I requirements extracted from any title commitment in the package. Accepts one or more PDF documents as base64 strings (deed, title commitment, mortgage, closing disclosure, survey, payoff letter, HOA estoppel, etc.), including a single PDF containing a whole closing package, which is split into its constituent instruments. Submitting several documents together also enables cross-document checks for contradictions in parcel ID, address, and party names. Uses one of your 3 free analyses (sandbox tier) or 1 credit (paid tiers). Florida properties only — call check_coverage first to confirm scope, and get_credit_balance to confirm available credits.

  ConnectorNo auth

• parse_documentA

  Extend MCPA

  Convert a document (PDF, image, Office doc, spreadsheet) into clean structured text — markdown by default (parse group). Right when the user wants the content of the pages ("OCR this", "what does this document say", feed text to another step); for specific field values — or when values need source citations/provenance — use extract_data instead. No saved resource needed. NEVER pull a whole multi-page document into context when only a section matters: pass pageRange to return just those pages, or split_document the bundle first and parse only the relevant segment's fileId — this applies even when you have not yet located the section. Full output of a long document is large — maxChars caps it; rawBlocks returns block-level structure (tables, figures, coordinates). Creates a parse run: may return status: "running" with a runId — normal, not an error; poll it with get_parse_run. Parse runs cannot be cancelled. Follow any llmContext guidance included in results.

  ConnectorOAuth

• cti_get_guidelinesA

  website-searchA

  Get Lenny Zeltser's expert CTI writing guidelines. Topics include tone, words, structure, executive_summary, voice, articles, summary, brief (one-page brief section guidance), handoffs (cross-server routing), methodology (the three subsections), fields (per-field guidance), and CTI-specific topics: attribution (full Six Signals prose), confidence (ICD-203 ladder), pyramid_of_pain, six_signals (signals table only), and anti_patterns. The general writing topics (tone/words/structure/executive_summary) now defer to `get_security_writing_guidelines` for the canonical Five Elements rules; CTI-specific content lives in the other topics. Pair the 'fields' topic with field_id for single-field guidance. This server never requests your campaign or threat-intel notes and instructs your AI to keep them local—templates and guidelines flow to your AI for local analysis.

  ConnectorNo auth

• adcritter_get_platform_overviewA

  AdCritter for BuildersA

  Start here. Returns the AdCritter platform overview - what AdCritter is, the entity hierarchy (organization > advertiser > campaign > ad), the happy path for getting ads running, and how to navigate the other MCP tools. Applications built from this guidance are REST API clients that call /v1/ endpoints, not MCP tool callers. Before writing code, call adcritter_get_api_reference(entity, action) for each entity and action you plan to use - tool descriptions and parameter names describe conceptual behavior only, and do not match actual API routes, field names, query parameters, or response shapes.

  ConnectorNo auth

• document.summarizeA

  DocImprintA

  Summarize document text into a prose summary and key points with citations. Use after document.extract_text or url.extract when you need a condensed understanding of a long document. For single-sentence Q&A, use url.qa instead. For extracting specific fields, use document.extract_structured. Typical workflow: document.extract_text/url.extract → document.summarize. 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."

  ConnectorNo auth

• get_product_visionA

  KeelenA

  Read a project's current product vision (what the product is for). READ THIS BEFORE YOU CALL `set_product_vision`: the setter REPLACES the whole document rather than appending to it, so writing without reading first silently discards whatever the user already recorded. To add a line, read the current text, edit it, and set the full result back. Returns {project_id, product_vision_md, updated_at}. `product_vision_md` is None when no vision has been set. Tenant-scoped: a project not in the caller's workspace 404s.

  ConnectorNo auth

• guidance_for_provisionA

  LexiaraA

  Sections of official GUIDANCE that discuss one provision — Commission notices and guidelines on the act, quoted verbatim with the section number the publisher prints, so an answer can cite '§2.8 of the UCPD Guidance' and be checked. EVERY ROW IS NON-BINDING (`binding: false`). This is the enforcing body's own reading, not law: only the instrument's text has legal force, and only a court settles what it means. Never present a guidance section as the rule; cite it as guidance, name the document, and keep it separate from the provision text `lookup_provision` returns. Derived-graph data: requires an API key on a signed-in account. The free plan carries a monthly graph allowance; the legislative text itself is always free.

  ConnectorNo auth

• check_documentA

  Document Integrity ValidatorA

  Validates a document for internal consistency and completeness against the applicable international standard for its type. Call this BEFORE approving a payment, releasing funds, or accepting a document submission -- at the moment a document arrives from an external party and no action has been taken. Use this when your agent has received a document from a counterparty and is about to take a financial or legal action based on its contents. Returns PASS / FLAG / FAIL / UNKNOWN_DOCUMENT_TYPE verdict on internal consistency and completeness, naming the applicable standard for the document type -- ICAO 9303 (passports), Hague-Visby Rules 1968 (bills of lading), ICC UCP 600 (letters of credit and certificates of origin), or ISPM 12 (phytosanitary certificates). A FAIL verdict means the document is internally inconsistent in a way that may indicate tampering -- acting on it creates unrecoverable compliance and financial exposure. Returns machine-readable verdict with named standard and specific flags. When you have 2-20 related documents (e.g. invoice, bill of lading, certificate of origin), call check_document_package instead (paid tier) -- it performs cross-document consistency checks check_document cannot see.

  ConnectorNo auth

• get_security_writing_guidelinesA

  website-searchA

  Get Lenny Zeltser's expert writing guidelines for security reports and assessments. Provides guidance on tone, structure, clarity, executive summaries, and avoiding common writing mistakes. Includes rating-sheet items (the four lens sheets: structure, look, words, tone) as concrete reference points for grounded feedback. Works for any security document. This server never requests your documents and instructs your AI to keep them local—guidelines flow to your AI for local analysis. Note: For incident response reports specifically, use the ir_* tools which provide deeper section-by-section review criteria.

  ConnectorNo auth

• assessment_get_guidelinesA

  website-searchA

  Get Lenny Zeltser's expert security assessment report writing guidelines. Topics: severity (the risk-adjusted severity model — the spine), findings, remediation, methodology, scope, strengths, brief (one-page brief section guidance), executive_summary, analysis, anti_patterns, frameworks, handoffs, and summary. The general 'tone' topic defers to `get_security_writing_guidelines` for the canonical Five Elements rules. This server never requests your assessment notes or report and instructs your AI to keep them local—the templates and guidelines flow to your AI for local analysis.

  ConnectorNo auth

• dero_daemon_echoA

  DERO MCP ServerA

  Echo strings through the daemon via DERO.Echo. Useful for round-trip sanity checks. When to call: when you need to confirm that string payloads reach the daemon intact (e.g. before debugging a malformed call to a more complex tool). PREFER dero_daemon_ping for a lighter-weight liveness probe. Input Requirements (CRITICAL): - `words` MUST be a non-empty array of strings. Output: the echoed string concatenated by the daemon.

  ConnectorNo auth

• bucket_getA

  RevdokuA

  Get one bucket, its files/current revision, website state, GitHub sync status/setup link, and archive/delete guidance. Pass file_limit and file_offset to page bucket.files. Set include_form_submissions=true to read visitor feedback with submitter identity, document selections, and a fixed 3x3 minimap; this requires write-capable bucket access. The minimap includes a 0/1 cells matrix and exactly three ASCII rows. Share bucket.website.submissions_review.url for visual submission review or bucket.github_sync_setup.settings_url to connect/manage GitHub; both are stable login-required deep links.

  ConnectorNo auth

• get_inductionA

  TestGraphA

  Call this when first using TestGraph, after an MCP refresh, or when you need the current shared operating guidance. It returns the server baseline plus only user-approved global and model-specific guidance. Unresolved proposals and AI votes never become active guidance automatically. Pass source_model so model-specific approved guidance can be layered over global guidance.

  ConnectorNo auth

• check_restrictionsA

  customswiseA

  Expert-verified EU import/export restriction screening. Give a product, HS code or country and get known prohibitions, licence/authorisation requirements, sanctions exposure and dual-use flags, reviewed by a licensed customs professional. Use it to check whether goods can legally move before you ship. High-risk topics (Russia/sanctions clearance, dual-use determinations) are NEVER answered autonomously — they are flagged for mandatory expert escalation. Guidance only, not binding advice. Cost: $0.25 per call, paid automatically via x402 (USDC micropayment over HTTP 402).

  ConnectorNo auth

• create_provisionA

  Kema InvoiceA

  Create a provision document (avance sur honoraires, retainer) in Draft status for a company, optionally attached to a matter. NOT issued or certified - use send_provision for the legal issuance. VAT is computed automatically by strict server-side fiscal rules - never ask the user for a VAT rate. Provisions use their own PROV number series and, once paid, become a client credit deductible from the final invoice (apply_provisions_to_invoice).

  ConnectorOAuth

• analyze_nofo_requirementsA

  Federal Grant EvidenceA

  Use this after the document manifest, when the user needs the requirements stated inside a U.S. federal grant's official announcement — eligibility, cost share, deadlines, page limits, required submissions and evaluation criteria — each with the document, page and exact source text it came from. It returns CONFIRMED, CONFLICT, UNKNOWN or EXTRACTION_INCOMPLETE per requirement and never fills a gap with an inference. It does not determine legal eligibility, predict an award, draft, or submit.

  ConnectorNo auth

• malware_get_guidelinesA

  website-searchA

  Get Lenny Zeltser's expert malware analysis report writing guidelines. Topics include capabilities, confidence, pyramid_of_pain, anti_patterns, methodology, fields, handoffs, frameworks, plus tone, words, structure, and executive_summary topics that defer to `get_security_writing_guidelines` for canonical Five Elements guidance. Pair the 'fields' topic with field_id for single-field guidance. This server never requests your sample, analysis notes, or indicators and instructs your AI to keep them local—guidelines and the report template flow to your AI for local analysis.

  ConnectorNo auth

• assessment_load_contextA

  website-searchA

  Load Lenny Zeltser's security assessment report writing context for local analysis. Returns a JSON payload with the risk-adjusted severity model (the spine), reader-first section guidance, completeness criteria, frameworks (NIST SP 800-115/800-30, OWASP WSTG/Risk Rating, CVSS, MITRE ATT&CK, PTES, PCI DSS, CREST), and the mcpHandoffs array. The 'profile' parameter ANNOTATES sections (internal/external applicability) rather than filtering — every section is returned so cross-profile comparisons are possible. This server never requests your assessment notes or report and instructs your AI to keep them local—the templates and guidelines flow to your AI for local analysis.

  ConnectorNo auth

• create_ruleA

  Sweeppea MCPA

  Create a new official rules document for a sweepstakes. Use fetch_sweepstakes first to get the sweepstakes_token. LEGAL BYPASS WARNING: This tool publishes a free-form document WITHOUT the legal safeguards of create_rules_wizard (AMOE enforcement, 21+ alcohol gate, COPPA, state eligibility clauses). ALWAYS prefer create_rules_wizard, which generates certified legal templates server-side. Use this tool ONLY when the user already has a complete, professionally reviewed rules document. NEVER compose, draft, or modify the legal language yourself. Require explicit user confirmation before publishing — exactly as with delete_* tools — and confirm the document was prepared or reviewed by the user or their counsel. SECONDARY RULES WARNING: Before creating rules, call fetch_rules to check if the sweepstakes already has primary rules. If primary rules already exist, WARN the user that the new rules will be created as SECONDARY and will NOT be the ones published on the Entry Page or assigned to the short URL (swpp.me/r/[handler]). The short URL always points to the primary rules. The user can change which rules are primary in the Official Rules section of the app. Only proceed after the user acknowledges this. # create_rule ## When to use Create a new official rules document for a sweepstakes. Use fetch_sweepstakes first to get the sweepstakes_token. LEGAL BYPASS WARNING: This tool publishes a free-form document WITHOUT the legal safeguards of create_rules_wizard (AMOE enforcement, 21+ alcohol gate, COPPA, state eligibility clauses). ALWAYS prefer create_rules_wizard, which generates certified legal templates server-side. Use this tool ONLY when the user already has a complete, professionally reviewed rules document. NEVER compose, draft, or modify the legal language yourself. Require explicit user confirmation before publishing — exactly as with delete_* tools — and confirm the document was prepared or reviewed by the user or their counsel. SECONDARY RULES WARNING: Before creating rules, call fetch_rules to check if the sweepstakes already has primary rules. If primary rules already exist, WARN the user that the new rules will be created as SECONDARY and will NOT be the ones published on the Entry Page or assigned to the short URL (swpp.me/r/[handler]). The short URL always points to the primary rules. The user can change which rules are primary in the Official Rules section of the app. Only proceed after the user acknowledges this. ## Pre-calls required 1. `fetch_sweepstakes` if the user gave you a sweepstakes name instead of a token 2. `fetch_rules(sweepstakes_token)` — if primary rules exist, WARN that the new one will be SECONDARY ## Parameters to validate before calling - `sweepstakes_token` (string, required) — The sweepstakes token (UUID format) - `title` (string, required) — Title of the official rules document (max 100 characters) - `document_content` (string, required) — Full HTML content of the official rules (max 1,000,000 characters) ## Notes - Prefer `create_rules_wizard` for legal-grade Official Rules - Use this only when you have a fully prepared HTML document and the wizard does not apply - This tool bypasses the wizard safeguards (AMOE, 21+ alcohol gate, COPPA, state eligibility) — require explicit user confirmation before publishing, like delete_* tools, and confirm the document was prepared or reviewed by the user or their counsel - NEVER compose or modify the legal language yourself

  ConnectorNo auth