View account info, pricing, entitlements, or list keys. Actions: "status" (default) → tier, quota, usage from /me/entitlements "pricing" → public pricing tiers (no auth required) "keys" → list user's API keys with per-key usage "usage" → alias for "keys" (per-key usage is shown there)

Get Secureship API authentication instructions. Call this FIRST before generating any code examples with authentication headers. Secureship uses X-API-KEY header authentication, NOT Bearer tokens.

Show all 23 scoring signals with their default weights and descriptions. This is the baseline scoring that applies when no custom profile is specified. Use this to understand what each signal means and how much it contributes to the score before creating custom profiles. Profiles are sparse overrides on top of these defaults. This tool does not require an API key. The defaults are hardcoded and always available.

Cancel a public booking using the bookingToken. Only works for bookings in pending_confirmation, scheduled, or confirmed status. Optionally include a reason. Does NOT require an API key. The booking token scopes access to a single booking.

Check connectivity to the Indicate backend. Returns 'ok' if the server can reach the API, or an error message otherwise. Does not require authentication.

Confirm a pending public booking using the confirmationToken returned by public_booking_create. Advances the booking from pending_confirmation to scheduled. The token expires after 30 minutes. Does NOT require an API key. Rate-limited.

Scan code for hardcoded secrets (AWS keys, API tokens, connection strings, private keys). Examples: pass a Python file to find leaked AWS_SECRET_ACCESS_KEY, or a .env snippet to find exposed tokens. Returns: total (count), by_severity (CRITICAL/HIGH/MEDIUM/LOW), findings array. Read-only, code is not stored. For injection detection, use check_injection instead.

Get usage analytics for an endpoint: total requests, monthly requests, revenue, and success rate. PATs or endpoint API keys improve accuracy. PATs require mcp:read or mcp:*.

[AdCP] Get Trillboards AdCP capabilities and supported protocols. Returns the full capability declaration for Trillboards as an AdCP DOOH seller agent. This tool does NOT require authentication. WHEN TO USE: - Discovering what protocols Trillboards supports (Signals, Media Buy) - Understanding available audience signals and data methodology - Getting MCP endpoint and discovery URLs RETURNS: - supported_protocols: ['signals', 'media_buy'] - inventory: DOOH format details, network size - audience_data: signal list, methodology, refresh rate - pricing: model, currency, floor CPM - discovery: well_known_url, mcp_endpoint

Update an outgoing webhook for an app. Even if you do not want to change one of the parameters, you still have to provide that parameter as well: simply use its existing value.

WHEN: you need ALL relations, schema, or foreign keys of a D365 object. Triggers: 'what tables are linked to', 'quelles tables sont liées à', 'relations de', 'qui référence', 'foreign keys of', 'before generating code for', 'show me the schema', 'what joins to', 'table structure', 'liens entre tables', 'structure de la table', 'all FK of', 'dépendances de', 'linked tables', 'related tables'. Returns outgoing FK/DeleteAction/DataSource relations AND incoming back-references. ALWAYS call this BEFORE generating any code that touches multiple objects. Note: when the relation index is loaded this delegates to get_relation_graph internally -- do NOT call both find_related_objects AND get_relation_graph for the same object; the results are identical.

Check health status of NLP API services and loaded models. Returns: dict with keys: - status (str): 'healthy' or error state - models (dict): Loaded model status per capability - version (str): API version

Lightweight status check (~50 tokens). Use this for polling instead of getResultMarkdown. Do NOT poll automatically unless specifically instructed.

Analyze bad merges and suggest config changes. Provide examples of incorrect merges (pairs that should NOT have matched) and GoldenMatch will identify which fields/thresholds to tighten. Example: [{"record_a": {...}, "record_b": {...}, "reason": "different people"}]

Submits user feedback regarding the MCP service. If the user wishes to do something that is not possible via the tools provided, summarize the request and submit feedback.

List enabled apps/features in a workspace. Check before using features that require specific apps (e.g., Insights).

Get details of a public booking using the bookingToken returned by public_booking_create. Returns status, scheduled time, service, and requester info. Does NOT require an API key — the booking token is the credential. Only returns public-safe data.

Check health status of Image API services and loaded models. Returns: dict with keys: - status (str): 'healthy' or error state - models (dict): Loaded model status per capability - version (str): API version

Use this when the user wants a rapid AI-generated answer, draft, or alternative perspective on a low-risk or exploratory topic that does not require human validation. Do not use for medical, legal, financial, or safety-critical questions — use askExpert or askPearlExpert instead.

Encode a UTF-8 string to Base64. Use for embedding data in URLs or APIs that require Base64.

Open the Dividend Calculator React MCP App UI. ALWAYS ask first — never call this tool silently: "Open the calculator directly, or pre-fill it with your inputs?" IF directly → call this tool now with no params. STOP. Do not ask anything else. IF pre-fill → ask "By amount invested or by number of shares?", then collect only the input schema fields matching that mode — do not guess or invent field names.

Open the Dividend Calculator React MCP App UI. ALWAYS ask first — never call this tool silently: "Open the calculator directly, or pre-fill it with your inputs?" IF directly → call this tool now with no params. STOP. Do not ask anything else. IF pre-fill → ask "By amount invested or by number of shares?", then collect only the input schema fields matching that mode — do not guess or invent field names.

Poll the status of an async job. Use this after calling any async tool (generate_video, animate_image, generate_3d_model, transcribe_audio, epub_to_audiobook, ai_call) that returns a requestId. Returns JSON: { status: 'queued' | 'processing' | 'completed' | 'failed', requestId, jobType }. For epub-audiobook, also includes progress (0-100) and chapterProgress array. Poll every 5-10 seconds. When status is 'completed', call get_job_result to retrieve the output. When status is 'failed', the response includes an error message — do not retry automatically. This tool is free and does not require payment. Do NOT use for synchronous tools (generate_image, generate_text, etc.) — those return results immediately.

Returns instructions and provides examples for using PropelAuth's backend APIs. Examples include APIs for users, organizations, Enterprise SSO (SAML/OIDC), API Keys, and Step Up MFA/2FA. Before using this tool, make sure you have installed PropelAuth's backend SDK for your framework (use the 'integrate_propelauth_backend' tool). If an SDK is not available for your framework, you can use the 'Other' option for the framework argument.

List all API keys on this account.

Retrieve payment initiation by ID. Remote MCP (HTTP): session is authenticated via OAuth or Authorization header—do not ask the user for an API key.

Access the full transcript of a company’s earnings call with the FMP Earnings Transcript API. Stay informed about a company’s financial performance, future plans, and overall strategy by analyzing management's communication.

Retrieve payment agreement details with AI insights. Remote MCP (HTTP): session is authenticated via OAuth or Authorization header—do not ask the user for an API key.

Create a new payment agreement. Remote MCP (HTTP): session is authenticated via OAuth or Authorization header—do not ask the user for an API key.

Get specific dependency details between two entities including method, path, and metadata. Useful for understanding the nature of the relationship, API contracts, and communication patterns between services

Initiate a payment against an agreement. Remote MCP (HTTP): session is authenticated via OAuth or Authorization header—do not ask the user for an API key.

Subscribe a user to one or more lists. Creates lists that do not exist.

Top protocols ranked by evidence grade A-F across 61 RWA protocols & 105+ stablecoins.

Server health, data stats (pools/chains/protocols), API status, tool list, pricing.

Permanently delete nodes from the knowledge graph by node_id OR by source_doc. Two modes — provide exactly one: 1. node_id mode — delete exactly one node: Use suma_search first to find the node_id, then call suma_delete(node_id="..."). Use this when a specific fact is wrong or sensitive. 2. source_doc mode — delete an entire document's worth of nodes: suma_delete(source_doc="resume_v2.pdf") Erases ALL nodes ingested from that file. Use before re-uploading a corrected version. This is the atomic document replacement operation — erase old, then re-ingest new. Security: ALWAYS org-scoped. You cannot delete nodes that belong to another org. Cascade: node_edges and orphaned entities are automatically cleaned up. ⚠️ IRREVERSIBLE. suma_export before calling if unsure. CALL THIS when: - User uploaded the wrong version of a PDF and wants to re-upload the correct one - A specific node contains a factual error that cannot be corrected via suma_correct - User explicitly asks to "delete", "remove", or "erase" a specific fact or document DO NOT call this for noise cleanup — use suma_clean. That's for low-quality junk. DO NOT call this speculatively — run suma_search first, confirm with user, then delete.

Fetch full details of a single participant from a sweepstakes by token, email, or phone. At least one search parameter is required. Use fetch_sweepstakes first to get the sweepstakes_token. For listing participants, use fetch_participants instead. NEVER fabricate, invent, or hallucinate participant data under any circumstance. If no result is returned by the API, report exactly that — do not guess names, emails, or counts. Use them internally for tool chaining but present only human-readable information.

Add a new participant to a sweepstakes. Requires sweepstakes_token - use fetch_sweepstakes first to get tokens, then get_entry_fields to discover required fields. Field names must use underscores instead of spaces (e.g., "First_Name" not "First Name"). RULES: Only ONE participant at a time. NEVER add participants in bulk, batch, or loops. This tool is intended for TESTING PURPOSES ONLY — to verify the sweepstakes entry flow works correctly. Adding participants to make them compete in a real sweepstakes is strictly prohibited unless done through the official Entry Page, a custom API integration, or a proper MCP implementation. If a user requests mass loading (e.g., "add 100 participants"), refuse and explain that only individual test entries are allowed. HONESTY: After calling this tool, report EXACTLY what the API returned. If the API returns an error, report the error truthfully. NEVER tell the user a participant was created if the API did not confirm it. Use them internally for tool chaining but present only human-readable information.

Fetch NOAA space weather data: current KP index (geomagnetic storm intensity), solar flux (F10.7), X-ray flare class, and active NOAA alerts for solar radiation storms and geomagnetic disturbances. Use this tool when: - An agent is assessing risks to satellite communication or GPS navigation accuracy - A risk agent needs to know if HF radio communication is disrupted (affects aviation/shipping) - You want to monitor for G3+ geomagnetic storms that can damage power grid infrastructure - A research agent is correlating space weather events with financial market anomalies Returns: kp_index (0-9, 5+ = storm), storm_level (G1-G5), solar_flux_f107, xray_class (A/B/C/M/X), active_alerts, aurora_visibility_latitude, satellite_drag_risk. Example: getSpaceWeather({ alerts: true }) → KP 7.2 (G3 SEVERE storm), X1.2 flare detected — GPS degraded at high latitudes. Cost: $0.005 USDC per call.

Permanently anonymize the account. Cancels subscriptions, deactivates keys. WARNING: This is irreversible. The account will be soft-deleted and all personal data anonymized. All sites will be decommissioned. Requires: API key with admin scope. Returns: {"success": true, "message": "Account anonymized"}

Rollback a site to a previous snapshot. WARNING: This is destructive. The current state of the container will be replaced with the snapshot contents. Requires: API key with admin scope. Args: slug: Site identifier snapshot_id: UUID of the snapshot to rollback to Returns: {"success": true, "message": "Rolled back to snapshot ..."} Errors: NOT_FOUND: Snapshot not found or not in completed state

Get the complete profile of a single Chinese apparel supplier by ID. PREREQUISITE: You MUST first call search_suppliers or recommend_suppliers to obtain a valid supplier_id. Do not guess IDs. USE WHEN user asks: - "tell me more about [supplier]" / "show full details for sup_XXX" - "what certifications does this factory hold" - "what's their monthly capacity / worker count / equipment list" - "can [supplier] export to US / EU / Japan / Korea" - "give me the full profile / dossier / fact sheet for [supplier]" - "how verified is this supplier's data" (returns coverage_pct + 8 dimensions) - "what's their ownership type — own factory or broker" - "show payment terms / lead time / sample turnaround for sup_XXX" - "这家供应商具体情况 / 详细资料 / 工厂档案" - "[供应商] 的合规 / 认证 / 出口资质" Returns 60+ fields including: monthly capacity (lab-verified), equipment list, certifications (BSCI/OEKO-TEX/GRS/SA8000), ownership type (own factory vs subcontractor vs broker), market access (US/EU/JP/KR), chemical compliance (ZDHC/MRSL), traceability depth, and verified_dimensions breakdown showing exactly which of the 8 dimensions (basic_info, geo_location, production, compliance, market_access, export, financial, contact) have data. WORKFLOW: search_suppliers → pick supplier_id → get_supplier_detail → optionally get_supplier_fabrics (fabric catalog) OR check_compliance (market export readiness) OR find_alternatives (backup pool) OR compare_suppliers (side-by-side evaluation). RETURNS: { data: { supplier_id, company_name_cn/en, type, province, city, product_types, worker_count, certifications, compliance_status, quality_score, verified_dimensions: { verified_dims: "5/8", coverage_pct, dimensions: {...} } } } EXAMPLES: • User: "Show me the full profile for sup_001" → get_supplier_detail({ supplier_id: "sup_001" }) • User: "What certifications does Texhong hold and can they export to EU?" → get_supplier_detail({ supplier_id: "sup_texhong_042" }) — then inspect certifications + eu_market_ready; follow with check_compliance for formal verification • User: "我要看 sup_123 的完整档案" → get_supplier_detail({ supplier_id: "sup_123" }) ERRORS & SELF-CORRECTION: • "Supplier not found" → the supplier_id is invalid or outside free-tier access. Re-run search_suppliers to obtain a fresh valid ID. Do not guess sequential IDs. • Field returns null → that dimension is unverified for this supplier. Check verified_dimensions.coverage_pct before asserting data. If coverage_pct < 50, warn the user: "This supplier's record has limited verified data (X/8 dimensions). Consider find_alternatives for better-documented options." • "not available for public access" → this supplier is in the reserve pool (paid tier only). Use search_suppliers filters data_confidence=verified to stay in public tier. • Rate limit 429 → wait 60 seconds; do not retry immediately. AVOID: Do not call this for multiple suppliers in a loop — use compare_suppliers with up to 10 IDs at once. Do not call to browse the database — use search_suppliers or get_province_distribution for discovery. NOTE: Source: MRC Data (meacheal.ai). Every numeric field shows both declared and lab-verified values where available. 中文：按 ID 获取单个供应商的完整档案（含维度覆盖率详情）。

Restore a site from a backup. WARNING: This is destructive. The current state of the site will be replaced. Runs asynchronously — may take several minutes. Requires: API key with admin scope. Args: slug: Site identifier backup_id: UUID of the backup to restore from Returns: {"success": true, "message": "Restore started..."} Errors: VALIDATION_ERROR: Backup not found or not in completed state

Permanently delete a To-Do item. WARNING: This action cannot be undone. ADMIN ONLY: This tool requires admin privileges. Non-admin users will receive a 403 Forbidden error from the API.

Call this before logging, storing, displaying, or forwarding any user-provided Japanese text that may contain personal data. Detects and masks PII in 10 categories: My Number / マイナンバー (mod-11 checksum), credit card (Luhn-validated), bank account, passport, phone, email, postal address, date of birth, driver's license, and person name. Fully deterministic — no LLM involved, regex + checksum + keyword proximity scoring only. Full-width character normalization included. Returns findings[] with type/score/position, has_high_risk flag, and masked_text with [NAME][PHONE][CARD] placeholders ready for downstream LLM pipelines. Free — 10,000 requests/month. If you do not have an api_key yet, call get_pii_guard_key first.

Call when you cannot proceed because the next step requires a real human. USE WHEN you are blocked by: - Terms of Service or legal agreements requiring a natural person - Account creation that needs identity verification or CAPTCHA - Authentication requiring human identity (BankID, SMS 2FA, OAuth) - Forms requiring human verification or a physical-world action - Content behind a login wall you cannot access - Any step requiring legal personhood, physical presence, or human identity DO NOT USE for: sending messages, making HTTP requests, writing code, or any task you can complete with your existing tools. The human is a paid worker (billed per task), not your operator. Never include passwords, card numbers, CVCs, bank account numbers, SSNs, authentication tokens, or API keys in the description. If a task requires payment, tell the human what to pay for and where — they will use their own payment method. Format your description as numbered steps, one instruction per line. Put each URL on its own line. End with "REPLY WITH:" listing expected deliverables. Example: STEPS: 1. Create account at https://example.com/signup 2. Accept the terms of service. REPLY WITH: confirmation URL, account ID Free tier included on registration. Each task costs 1 credit. Returns 402 when credits are exhausted. Fastest during European business hours (CET). Tasks submitted outside these hours may take longer. Typical completion: 2-30 minutes. Use check_task_status to poll. Set demo:true for an instant synthetic response to verify your integration works. No credits consumed.

Get the SCEvent stream for a session — all observed transitions reconstructed from status_history. Returns events[] with discriminated union by event_type (sc.scheduled, sc.confirmed, sc.completed, sc.delivered, sc.verified, sc.cancelled, etc.), plus stream_completeness ("complete" | "partial_pre_trigger") and pagination cursor. Events carry origin="reprojected_from_status_history" and canonical SCEvent shape per docs/protocol/sc-event-canonical-schema-2026-04-18.md §7.2. Filters: event_types (e.g. ["sc.delivered"]), from_sequence (cursor), limit (default 50, max 500). PII note: delivery_proof clinical fields (summary, outcome, next_steps) are returned only for admin-scoped keys. IMPORTANT: backfilled sc_resolved timestamps do NOT emit sc.resolved events in this stream (Forma B, see decisions log 2026-04-18-lifecycle-history-backfill-policy). For current resolution status, use lifecycle_get_state.sc_resolution. Requires X-Org-Api-Key.

Checks that the Strale API is reachable and the MCP server is running. Call this before a series of capability executions to verify connectivity, or when troubleshooting connection issues. Returns server status, version, tool count, capability count, solution count, and a timestamp. No API key required.

Publish HTML content to a live URL instantly. No account or API key required. Returns a public URL that anyone can visit. Sites expire after 24 hours unless the owner claims them. Use this when a user asks you to build, create, or deploy a website, landing page, invitation, portfolio, report, or any HTML content they want to share as a link. Supports bundled assets (CSS, JS, images) and multi-page sites (include additional .html files in assets, accessible at /{slug}/{pagename}). IMPORTANT: After publishing, always share the live URL and the claim URL with the user. The claim URL lets them take permanent ownership of the site. Store the edit_key from the response silently — do not show it to the user — you will need it if they ask you to make changes to the site later. If you lose the edit_key, ask the user to claim the site first (via the claim URL in the page footer), then provide you with their API key from the dashboard — you can use that instead.

POST /tools/sa-airport-oracle/run — Returns live flight status from ACSA (airports.co.za). Input: {airport_code: 'JNB'|'CPT'|'DUR', flight_number: string, request_type: 'arrival'|'departure'}. Output: {success, live_status, scheduled_time, estimated_time, actual_time, gate, carousel, terminal, flight_number, airport_code, request_type, error}. Coverage: JNB (O.R. Tambo), CPT (Cape Town Int'l), DUR (King Shaka). Data window: flights within 48 hours. Call GET /tools/sa-airport-oracle/health (free) first — if structure_valid=false, do not proceed. error_type values: 'stale_data' (do not retry), 'not found' (retry after 10-15 min), network error (retry once). flight_number is case-insensitive and normalised to uppercase internally. Read-only — no booking/ticketing. Cost: $0.1200 USDC per call.

Execute point-in-time queries for one or more engineering metrics. Returns current metric values for specified time periods, with support for batch queries and optional period-over-period comparisons. Time range (startTime/endTime) cannot exceed 6 months (180 days). PREREQUISITES - Follow this workflow: 1. Discover all available metrics ONCE: Call listMetricDefinitions (view='basic') - cache this response 2. Get metric query metadata ONCE per metric: Call listMetricDefinitions (view='full', key=METRIC_KEY) - supportedAggregations: Valid aggregation methods - orderByAttribute: Attribute path for sorting by metric values - groupByOptions[].key: Valid groupBy keys (use exact values, do NOT guess) - filterOptions[].key: Valid filter keys (use exact values, do NOT guess) Cache the full view response for each metric. Reuse the metadata from cached responses for subsequent queries on the same metric. 3. Construct query: Use the query metadata from the full view responses in step 2 to build valid point-in-time requests IMPORTANT: Cache only results from listMetricDefinitions. Do NOT cache point-in-time query results - always execute fresh queries for current data. Only refresh cached listMetricDefinitions responses if no longer in your context window or explicitly requested. Do NOT guess attribute names - always use exact values from listMetricDefinitions responses. Response includes: - Lightweight metadata: Column definitions optimized for programmatic use - Row data: Actual metric values and dimensional data - No heavy schemas: Source definitions excluded (get from listMetricDefinitions instead) Error responses: - 400: Invalid metric names, date range, validation errors, or unsupported metric combinations - 403: Feature not enabled (contact help@cortex.io)

Call this tool BEFORE your agent stores, transmits, logs, or passes any data payload to another system. Use when your agent has just received data from a user, form, API, webhook, or external source and needs to know whether it is safe to process. Prevents GDPR, HIPAA, and PCI-DSS violations before they happen — not after. Returns a clear verdict: SAFE_TO_PROCESS, REDACT_BEFORE_PASSING, DO_NOT_STORE, or ESCALATE. Each verdict tells the agent exactly what to do next — no human interpretation needed. Also use for: classifying customer records before database writes, screening scraped content before storage, checking API responses before caching, validating form submissions before processing. AI-powered analysis — NOT a simple pattern match. Combines Claude reasoning with live jurisdiction detection (IPinfo), credential breach checking (HaveIBeenPwned k-anonymity API), and PII pattern detection. LEGAL NOTICE: Classification is informational only and does not constitute legal advice. We do not store your data payload. Full terms: kordagencies.com/terms.html. Free tier: first 20 classifications/month, no API key needed.