Skip to main content
Glama
310,001 tools. Last updated 2026-07-28 08:16

"How to check differences between files" matching MCP tools:

  • FREE — no payment required. Call this FIRST to check whether a ticker is covered and what it will cost before spending anything. Returns whether the company is in the corpus, how much data exists (filings / earnings periods / insider transactions), how fresh it is, and the exact price of every paid tool. If a ticker is not covered, the paid tools return no data — so check here instead of paying to find out.
    Connector
  • Check existing uploads and determine which files still need uploading. Call this BEFORE upload_pdf or create_upload_page to avoid duplicate uploads. Also call it after the user uploads via the widget to discover the new file and its job_id. Returns 'session_id' (always — store it!), plus: - 'already_uploaded': files found in this session with reusable job_ids - 'needs_upload': files not yet in this session (must be uploaded) You MUST call this tool before any upload, and you MUST act on its result immediately: - 'needs_upload' is non-empty → call upload_pdf (single) or batch_upload_pdf (multiple) with ONLY the files listed in 'needs_upload'. Pass the same session_id. Do NOT upload files in 'already_uploaded'. - 'needs_upload' is empty → skip uploading entirely; use the job_ids from 'already_uploaded'. When pending_filenames is omitted, returns all jobs currently in the session.
    Connector
  • MANDATORY for all document comparison requests. Compare two PDFs side-by-side. When the user asks to compare, diff, or find differences between two PDFs, you MUST call this tool — NEVER attempt to compare documents using text analysis. Displays an interactive side-by-side visual diff widget with colored highlights: red = deleted, yellow = replaced, green = inserted. The widget IS the comparison result — do NOT re-summarize the differences after calling. Before calling, confirm both job_ids exist via check_upload_status.
    Connector
  • Check the interaction between two drugs (by brand or generic name). Returns severity (contraindicated / major / moderate / minor / unknown), mechanism (when known), and source citations. Always include the response disclaimer in your final answer.
    Connector

Matching MCP Servers

  • -
    license
    -
    quality
    C
    maintenance
    A minimal MCP server with get_weather and create_ticket tools, used for testing MCP servers across protocol, unit, eval, transport, and auth layers.
    Last updated

Matching MCP Connectors

  • Transform any blog post or article URL into ready-to-post social media content for Twitter/X threads, LinkedIn posts, Instagram captions, Facebook posts, and email newsletters. Pay-per-event: $0.07 for all 5 platforms, $0.03 for single platform.

  • Live brand-name availability checks: US trademark (USPTO), domains, social handles, app stores.

  • The MITRE Rosetta Stone. Given a MITRE technique ID across 5 frameworks (ATT&CK Enterprise, ATT&CK Mobile, ATT&CK ICS, D3FEND, ATLAS), return the Bidda node for that technique plus its mapped compliance obligations: NIST 800-53 controls, ISO 27001 Annex A clauses, PCI DSS requirements, NIS2 articles, HIPAA Security Rule, DORA articles, NERC CIP, IEC 62443. The bridge between how SOC teams think (technique IDs) and how compliance teams think (control families). Free.
    Connector
  • Download one or more files server-side and return their content as base64-encoded strings. Use this to inspect images, PDFs, or any binary file attached to messages when you cannot access presigned S3 URLs directly. Supports up to 5 files per call, max 15 MB each. For large files batch in groups of 1-2 to avoid oversized responses.
    Connector
  • Answer questions using knowledge base (uploaded documents, handbooks, files). Use for QUESTIONS that need an answer synthesized from documents or messages. Returns an evidence pack with source citations, KG entities, and extracted numbers. Modes: - 'auto' (default): Smart routing — works for most questions - 'rag': Semantic search across documents & messages - 'entity': Entity-centric queries (e.g., 'Tell me about [entity]') - 'relationship': Two-entity queries (e.g., 'How is [entity A] related to [entity B]?') Examples: - 'What did we discuss about the budget?' → knowledge.query - 'Tell me about [entity]' → knowledge.query mode=entity - 'How is [A] related to [B]?' → knowledge.query mode=relationship NOT for finding/listing files, threads, or links — use search.files / search.threads / search.links for that.
    Connector
  • List files directly attached to this agent (agent-specific files, not shared collections). Returns file_id, title, status, and chunk_count for each file. chunk_count shows how many indexed chunks were created — 0 means the file is still processing. Use agents.add_file to attach a new file, or agents.remove_file to detach one.
    Connector
  • Create a named knowledge collection. Collections group files for RAG search. After creating, add files with collections.add_file and assign to agents with collections.assign_agent.
    Connector
  • Use this when runner input is missing or unclear. Explains how to obtain or generate runner input, what USRProf/evidence files should contain, whether GPX/FIT activities are enough, and how hosted MCP clients should upload artifacts.
    Connector
  • How much time had passed between the most recent conduct and the decision, measured from dates stated in the decisions, for the incident-type concerns (drugs, alcohol, criminal conduct, sexual behavior, protected information, IT misuse). Reports median years before favorable vs unfavorable decisions, with counts. Descriptive association, never a prediction.
    Connector
  • Trigger a health check for a specific smart link. Checks the default URL and all geo-rule URLs for availability. Returns the health status (healthy/broken/unknown). Rate limited to once per 5 minutes per link. Does NOT modify the link configuration. Common errors: - Rate limit: wait 5 minutes between health checks for the same link. - Smart link not found: check the ID.
    Connector
  • Compare two provenance receipts and highlight differences. Prefer `cuecrux_session` as your first and only direct MCP call. It returns a typed capability plan that routes this tool (and every other) to its preferred channel, tier, and cost class. One call per session is enough; the plan is the source of routing truth for all subsequent work. This tool remains directly callable for backward compatibility; the collapsed surface is the intended surface.
    Connector
  • Deep perceptual and semantic comparison between any two hex values. Returns quantified differences in LRV, chroma, hue angle, warmth, and CIEDE2000 distance, plus cultural context on both — which is more authoritative, more saturated, more stable under different illuminants, and what each has historically signified. Use when choosing between two colours or explaining why one works better than another. Not a harmony tool — this is a decision and reasoning tool.
    Connector
  • Check the status of a cron schedule — is it active, when does it next run, how many times has it executed?
    Connector
  • Generate the Axint project-start pack for a new Apple app without writing files. Use: use to bootstrap a new Apple project with Axint instructions; use project.index to inspect an existing project. Inputs: cwd and projectName identify the project; host choices control generated integration files. Effects: read-only generated file pack; writes no files and uses no network.
    Connector
  • Check how many Rams reviews this workspace has used and has left (rolling 30 days, shared between the GitHub App and MCP). Free to call — does not consume a review.
    Connector