Skip to main content
Glama
751,298 tools. Updated 2026-11-06 13:54

"Analysis of March 18th JFK Assassination Document Releases" matching MCP tools:

  • List a public/competitor creator's videos by platform + handle. Sort by 'recent' or 'top' (best-performing); optionally with analysis inline. Only returns creators already in the analysis library — for one you haven't ingested yet this returns reason="creator_not_in_library" with a next_step of analyze_creator(platform, username), not an error. When more videos exist beyond this page the response includes next_cursor — pass it back as cursor (same sort/filters) to fetch the next page; when next_cursor is absent you have everything.
    ConnectorOAuth
  • Re-queue an already-uploaded document through the pipeline. Use this to re-run extraction/PII detection/quality scoring on a document you've already processed — e.g. after a document_type_hint change, without downloading and re-uploading the original file. Returns immediately with a job_id — poll with job.status the same way as after document.process. Only works for documents whose original file is still stored on the server (locally uploaded, not connector-sourced). If the file is no longer available, re-upload it with document.process instead. Args: document_id: ID of a previously processed document. pipeline_config: Optional pipeline config overrides, e.g. {"document_type_hint": "invoice"}.
    ConnectorNo auth
  • Changes part of a draft's document without resending the rest. The patch is a JSON Merge Patch (RFC 7386): an object shaped like the document naming only what is to change. Three rules and no others -- an object recurses, so {"settings":{"displayComments":false}} changes one switch and leaves the rest of the settings alone; a null removes the member it names, which is the only way to clear the description without restating the document; and everything else replaces, arrays included. That last rule is why this is not the tool for tasks: a tasks array in the patch replaces every task there is. Use it for the name, the description, the settings, the tags and the permissions, and use apply_draft_operations for anything inside tasks, fields, parameters, conditions or notifications. A property the document has no word for is dropped rather than stored, so read the document in the answer rather than assuming the patch landed.
    ConnectorAPI key
  • Use a published configuration for an event not yet on sale, or remove it (null); its removed seats are blocked. Use when: e.g. "the 12 March show uses the concert setup" while it is in setup. Needs "Manage live events" (publish permission in Designer). Fails if a removed seat is held or booked. Example: {"eventKey": "ev_1350a828b5ff", "expectedRevision": 0, "configuration": {"id": "ec_4f1c2a9e7b3d5f8e0a2c4e6b8d1f3a5c", "version": 2}}
    Connector
    Destructive
    OAuth
  • Get the full analysis (incl. scene breakdown) for a video — owned or public/competitor. Pass `platform` and `post_id` separately (the native post_id from analyze_post or list_videos — not the composite `id` field). Deep analysis runs async (~30-60s): right after analyze_post this returns {"status": "pending", "retry_after_seconds": N} — that is expected, not an error. Wait that long and call again until you get the full analysis. A genuine 404 means the post was never analyzed — call analyze_post(url) first.
    ConnectorOAuth
  • Zero-arg macro dashboard: key snapshots plus upcoming releases. Filtered calendar list→get_economic_calendar. Indicator snapshot or series→get_macro_indicator. Read-only public research data. No account access, no order placement or fund transfers. Not investment advice.
    ConnectorNo auth

Matching MCP Servers

  • A
    license
    Not graded
    quality
    A
    maintenance
    A registry of product release notes from across the web, normalized, summarized, and queryable via MCP. Enables agents and developers to search and retrieve the latest releases from hundreds of vendors.
    53 npm
    13
    Apache 2.0
  • A
    license
    Not graded
    quality
    C
    maintenance
    Enables searching and retrieving documents that congressional committees publish on their own websites, including press releases, oversight letters, staff reports, and interview transcripts, with no authentication required.
    423 npm
    MIT

Matching MCP Connectors

  • Committee Releases — documents congressional committees publish on their OWN websites: press…

  • Chipp: software factory deploys and releases: history, the deploy gate, Deploy now, rollbacks.

  • Search the Nordic financial database for company filings, press releases and macroeconomic summaries. Use this as the primary tool for any question about Nordic listed companies, markets or macro conditions. Do not use to retrieve a full document — results are chunked text excerpts; use parse_pdf_to_text for the full original document. Do not use for Swedish company registration data — use get_company_info instead. The database contains ~1 million vectors across four Nordic markets (NO/SE/DK/FI). COMPANY FILINGS Annual reports (XBRL/ESEF) and quarterly reports from ~1 500 listed companies across Oslo Børs, Nasdaq Stockholm, Nasdaq Helsinki, Nasdaq Copenhagen and First North markets. Covers 2020–present. Strong coverage for NO and SE; growing coverage for DK and FI. EXCHANGE ANNOUNCEMENTS & PRESS RELEASES Regulatory filings, exchange announcements and press releases from listed companies in NO, SE, DK and FI. Covers 2020–present. MACROECONOMIC SUMMARIES Quarterly macro summaries covering key indicators per country: Norway (NO): policy rate, FX rates, CPI, house prices, credit growth, electricity price, salmon price, GDP components Sweden (SE): policy rate, house price index, household credit Denmark (DK): policy rate, house price index, household loans, electricity price Finland (FI): house price index, household debt-to-income ratio, electricity price Use report_type='macro_summary' and country='NO'/'SE'/'DK'/'FI' to filter. Use fiscal_year and a quarter reference in your query, e.g. "Norwegian housing market Q1 2024". Args: query: What you are looking for, e.g. 'net interest margin outlook', 'salmon price Q3', 'dividend policy', 'fleet utilization', 'Norwegian housing market 2024 Q1', 'Swedish policy rate inflation 2023' ticker: Optional — filter by company ticker, e.g. 'SALM', 'EQNR', 'NDA' fiscal_year: Optional — filter by year, e.g. 2024 report_type: Optional — one of: 'annual_report' – Nordic XBRL/ESEF annual reports 'quarterly_report' – Quarterly/interim reports 'press_release' – Exchange announcements and press releases 'macro_summary' – Quarterly macroeconomic summaries sector: Optional — filter by sector: 'seafood' – seafood companies 'energy' – energy / oil & gas 'shipping' – shipping companies country: Optional — filter by country code: 'NO', 'SE', 'DK' or 'FI' limit: Number of results after reranking (default 5, max 20) Returns: List of relevant text excerpts with metadata, reranked by relevance. Each result includes rerank_score, hybrid_score, vector_score, company, ticker, country, fiscal_year, report_type, period, filing_date and the full text chunk. Returns an empty list if no relevant results are found or if the Qdrant database is temporarily unreachable.
    ConnectorNo auth
  • Create an XRPL escrow vault. Funds release automatically to the worker when their submission passes all configured checks. Free to try: pass network='testnet' (see create_testnet_wallet / try_testnet_demo). Buyers can require NFT ownership, an atomic NFT Delivery-vs-Payment swap, domain verification, or W3C Verifiable Credentials before a PASS releases escrow — set the relevant proof-gate params below. Three release modes: - AI audit (default): worker submits text/files; AI referee scores against task_description or criteria. - Proof-gate only (require_ai_audit=False): payment releases when all configured proof gates pass. No AI call. - Delayed release (release_mode='challenge_window_hrs:N'): PASS holds for N hours then auto-releases. During the window, the buyer can challenge via prepare_challenge_escrow + challenge_escrow_verdict. Challenge fee ~$1 USD in XRP locked to the seller; paid to seller if PASS upheld, refundable if overturned or inconclusive. Structured criteria (recommended for complex work): - Pass criteria as a list of strings or typed dicts ({type, description, [gate]}). - Types: 'judgment' (AI decides), 'evidence' (verify URL content), 'code' (deterministic gate; supported gates: sha256_of, exact_match, regex, json_schema). - INCONCLUSIVE verdicts do not consume an attempt for the first 3 per vault; subsequent INCONCLUSIVEs count as an attempt. White-label / headless integration: - Pass callback_url to receive webhook POSTs on all state changes. - Pass metadata (JSON string) to attach your own reference IDs.
    Connector
    Destructive
    No auth
  • The rules behind every figure this server returns: the exact prompt panel and its version, which engines were measured, how share of answer is scored and rounded, the resolution of the scale in percentage points, and the editorial firewall and ownership disclosure. Call this before quoting a number as evidence, before comparing two releases, or whenever a user asks how the measurement was made or who publishes it. It is the only tool that tells you how much of a difference is meaningful, which is what stops a one-step wobble being reported as a movement. It returns rules, not figures — no brand appears in the response. For figures use get_visibility_index or get_brand_visibility; for the series, get_history. The panel is public and frozen between releases, so every published number can be recomputed by a third party from the archive at https://dabyte.ai/archive/. Re-measured weekly, so the same call returns the same figures until the next release. Data is CC BY 4.0 and free: no key, no account, no rate limit — cite the release date and dabyte.ai when quoting a number.
    ConnectorNo auth
  • The rules behind every figure this server returns: the exact prompt panel and its version, which engines were measured, how share of answer is scored and rounded, the resolution of the scale in percentage points, and the editorial firewall and ownership disclosure. Call this before quoting a number as evidence, before comparing two releases, or whenever a user asks how the measurement was made or who publishes it. It is the only tool that tells you how much of a difference is meaningful, which is what stops a one-step wobble being reported as a movement. It returns rules, not figures — no brand appears in the response. For figures use get_visibility_index or get_brand_visibility; for the series, get_history. The panel is public and frozen between releases, so every published number can be recomputed by a third party from the archive at https://dabyte.ai/archive/. Re-measured weekly, so the same call returns the same figures until the next release. Data is CC BY 4.0 and free: no key, no account, no rate limit — cite the release date and dabyte.ai when quoting a number.
    ConnectorNo auth
  • Historical odds for a SPECIFIC trip window at one resort — 'Whistler on March 27', 'Vail Jan 10–17'. From ~30 years of ERA5 monthly history it blends the window's months (weighted by days) into: the snow-day probability (the headline — for a short window how OFTEN it snows beats how MUCH falls in a season), window-scaled expected snowfall and typical base depth, the same window across the last 5 individual seasons, and the best nearby month (±1) by snow-day odds. Window max 31 days; dates are YYYY-MM-DD. This is HISTORY, not a forecast and not a prediction — for the next 14 days use get_weather_forecast, and for a whole-month question use get_monthly_snow. Windows with under 5 tracked seasons return insufficient rather than thin odds.
    ConnectorNo auth
  • Check the selected service's current runtime readiness, input limits, pricing and retention before use. Returns service and details; ready=false means the underlying service is unavailable. Free cached runtime read; no external probe, payment, analysis or historical document retrieval. Use get_utility_example for a fixed integration sample instead.
    ConnectorNo auth
  • Delete (soft-delete) one of the authenticated customer's uploaded regulation proof documents by id — proof ids come from list_identities / list_addresses. Use it to REPLACE an existing document: delete the old proof first, then call create_regulation_upload_link — the freed document slot is offered again. This is destructive and cannot be undone. A proof linked to a pending address verification cannot be deleted. Returns the deleted proof info on success.
    Connector
    Destructive
    OAuth
  • Upload an image to a document and get back the src to place it with. Pass the image as base64 in `content` with its `name`. PNG, JPEG, GIF, WebP or AVIF, detected from the bytes, not the name; SVG is not accepted. At most 3 MB. The result's `trmd` is ![alt](src): write it in a text row, a table cell or an ID row's text cell with traceable_block_write, traceable_block_update, traceable_segment_write or traceable_grid_cell, adding {width=60%,align=center} after it to size it. Uploading places nothing by itself. A write may only place an image the application holds: a src on another site or a data: URI is refused. Calling it twice uploads twice. In an organisation under controlled releases this tool works once an admin turns it on in Org settings > Releases.
    ConnectorOAuth
  • Download one HKEx document by its URL and read, page through, or search its text. ``link`` must be an HKEx document URL from search_filings (host ``www1.hkexnews.hk``); any other host is rejected. With ``extract=True`` (default) the response includes up to 30 ``tables`` and a window of extracted ``document_text``: ``max_chars`` characters starting at ``offset``. Long reports return ``next_offset``; call again with it to read the next window. Pass ``query`` to search the whole document instead: the response then lists up to 20 case-insensitive matches with their offsets and surrounding text, plus ``match_count`` — use a match offset to read that part. Set ``extract=False`` for size and content type only.
    ConnectorNo auth
  • Create an XRPL escrow vault. Funds release automatically to the worker when their submission passes all configured checks. Free to try: pass network='testnet' (see create_testnet_wallet / try_testnet_demo). Buyers can require NFT ownership, an atomic NFT Delivery-vs-Payment swap, domain verification, or W3C Verifiable Credentials before a PASS releases escrow — set the relevant proof-gate params below. Three release modes: - AI audit (default): worker submits text/files; AI referee scores against task_description or criteria. - Proof-gate only (require_ai_audit=False): payment releases when all configured proof gates pass. No AI call. - Delayed release (release_mode='challenge_window_hrs:N'): PASS holds for N hours then auto-releases. During the window, the buyer can challenge via prepare_challenge_escrow + challenge_escrow_verdict. Challenge fee ~$1 USD in XRP locked to the seller; paid to seller if PASS upheld, refundable if overturned or inconclusive. Structured criteria (recommended for complex work): - Pass criteria as a list of strings or typed dicts ({type, description, [gate]}). - Types: 'judgment' (AI decides), 'evidence' (verify URL content), 'code' (deterministic gate; supported gates: sha256_of, exact_match, regex, json_schema). - INCONCLUSIVE verdicts do not consume an attempt for the first 3 per vault; subsequent INCONCLUSIVEs count as an attempt. White-label / headless integration: - Pass callback_url to receive webhook POSTs on all state changes. - Pass metadata (JSON string) to attach your own reference IDs.
    Connector
    Destructive
    No auth
  • Create a new custom document type for the account. Use this tool when: - The user asks for a new kind of document to be distinguished, e.g. "add a Framework Agreement document type" - A document or template needs a document type that the account does not have yet Call list-account-document-types first: fynk already provides system document types such as "Non-Disclosure Agreement", "Rental Agreement" or "Service Agreement" to every account, and a custom type that duplicates one of them splits the account's documents across two types. Create a new type only when none of the existing ones fits. Write `name` in Title Case, the way fynk's own types are named ("Data Processing Agreement", "Letter of Intent"), rather than copying the user's phrasing verbatim - a request for "a type for supplier framework contracts" should produce "Supplier Framework Agreement". `description` and `prompt` are how a new type is normally set up, so propose both from what the type is for rather than leaving them out: - `description` tells users what the type covers, in one sentence. fynk's "Rental Agreement" reads: "A contract between a landlord and tenant defining the terms under which property is rented, including duration, payment terms, and usage conditions." - `prompt` is what fynk's AI analyses read when deciding whether a document is of this type - without one, they rarely pick the type. Phrase it as a selection criterion, the way fynk's own types do. "Rental Agreement" reads: "Select this type if the document defines the terms under which a tenant rents property from a landlord, including rent amount, duration, deposit, and usage conditions." `relevant_metadata_uuids` decides which metadata fields fynk's AI analyses look for in documents of this type, besides the fields already relevant for every document type, which apply to the new type automatically. Call list-account-metadata to find the candidates, and propose the fields that type's documents would carry, e.g. a "Net Rent" field for a lease type. The fields chosen here are made relevant for the new type alongside the types they already have, and list-account-metadata reports the result: each field there names the document types it is relevant for.
    ConnectorOAuth
  • Adds a party to a document, alongside any parties it already has. Use this tool when: - A contracting party is missing from a document, e.g. the counterparty of a contract created from scratch - A signatory has to be added for a party the document does not have yet: create the party first, then add the signatory with create-document-signatory Pass party_account_party_uuid to add one of the account's saved parties (list-account-parties), usually the user's own company. A saved party can be on a document only once, and is always internal. For any other party, give party_entity_name, party_address and party_scope instead. Parties cannot be added while the document is archived, in the signing stage or an approved stage, going through an approval checkpoint, or bound by a preemptive signature.
    ConnectorOAuth
  • Create a new custom document type for the account. Use this tool when: - The user asks for a new kind of document to be distinguished, e.g. "add a Framework Agreement document type" - A document or template needs a document type that the account does not have yet Call list-account-document-types first: fynk already provides system document types such as "Non-Disclosure Agreement", "Rental Agreement" or "Service Agreement" to every account, and a custom type that duplicates one of them splits the account's documents across two types. Create a new type only when none of the existing ones fits. Write `name` in Title Case, the way fynk's own types are named ("Data Processing Agreement", "Letter of Intent"), rather than copying the user's phrasing verbatim - a request for "a type for supplier framework contracts" should produce "Supplier Framework Agreement". `description` and `prompt` are how a new type is normally set up, so propose both from what the type is for rather than leaving them out: - `description` tells users what the type covers, in one sentence. fynk's "Rental Agreement" reads: "A contract between a landlord and tenant defining the terms under which property is rented, including duration, payment terms, and usage conditions." - `prompt` is what fynk's AI analyses read when deciding whether a document is of this type - without one, they rarely pick the type. Phrase it as a selection criterion, the way fynk's own types do. "Rental Agreement" reads: "Select this type if the document defines the terms under which a tenant rents property from a landlord, including rent amount, duration, deposit, and usage conditions." `relevant_metadata_uuids` decides which metadata fields fynk's AI analyses look for in documents of this type, besides the fields already relevant for every document type, which apply to the new type automatically. Call list-account-metadata to find the candidates, and propose the fields that type's documents would carry, e.g. a "Net Rent" field for a lease type. The fields chosen here are made relevant for the new type alongside the types they already have, and list-account-metadata reports the result: each field there names the document types it is relevant for.
    ConnectorOAuth
  • Adds a party to a document, alongside any parties it already has. Use this tool when: - A contracting party is missing from a document, e.g. the counterparty of a contract created from scratch - A signatory has to be added for a party the document does not have yet: create the party first, then add the signatory with create-document-signatory Pass party_account_party_uuid to add one of the account's saved parties (list-account-parties), usually the user's own company. A saved party can be on a document only once, and is always internal. For any other party, give party_entity_name, party_address and party_scope instead. Parties cannot be added while the document is archived, in the signing stage or an approved stage, going through an approval checkpoint, or bound by a preemptive signature.
    ConnectorOAuth
  • Use it when the user asks which fields Nutrient would extract from a document, or wants to review them before paying for an extraction: it generates the schema extract_fields would use for an intent from the document itself, without extracting; nothing is billed and no run is stored. Use it also to fix one set of fields before extracting several files of one kind. Pass the intent and document_type you would pass to extract_fields, and one input: asset_id from upload_documents, document or source_run_id. Returns schema and schema_fields, its top-level fields. Then call extract_fields with the same intent and instructions.schema set to this schema, edited if a requested field is missing.
    ConnectorOAuth