Skip to main content
Glama
127,484 tools. Last updated 2026-05-05 18:07

"A tool for finding relevant academic publications and open-source projects on GitHub" matching MCP tools:

  • Check whether a factual claim is supported by a specific set of public evidence URLs that you already have. For each source, the tool performs a case-insensitive keyword match over the fetched page body, then marks that source as supporting the claim when at least half of the supplied keywords appear. Use this for evidence-backed claim checks on known pages, not for open-ended search, semantic reasoning, or contradiction extraction. The aggregate verdict is driven only by the per-page keyword support ratio. Fetched pages are cached for 5 minutes.
    Connector
  • Discovers the most relevant tools available on this MCP server for a given task using local semantic search (MiniLM-L6-v2 embeddings). Accepts a plain-English description of what needs to be accomplished and returns the best matching tools ranked by relevance, along with their input schemas, pricing tier, and exact call instructions. Use this tool first when you are connected to this server but do not know which specific tool to call — describe your goal and let platform_tool_finder identify the right capability. Do not use this tool if you already know the tool name — call that tool directly instead. Returns up to 10 results ranked by semantic similarity score.
    Connector
  • Find working SOURCE CODE examples from 37 indexed Senzing GitHub repositories. Indexes only source code files (.py, .java, .cs, .rs) and READMEs — NOT build files (Cargo.toml, pom.xml), data files (.jsonl, .csv), or project configuration. For sample data, use get_sample_data instead. Covers Python, Java, C#, and Rust SDK usage patterns including initialization, record ingestion, entity search, redo processing, and configuration. Also includes message queue consumers, REST API examples, and performance testing. Supports three modes: (1) Search: query for examples across all repos, (2) File listing: set repo and list_files=true to see all indexed source files in a repo, (3) File retrieval: set repo and file_path to get full source code. Use max_lines to limit large files. Returns GitHub raw URLs for file retrieval — fetch to read the source code.
    Connector
  • Upload connector code to Core and restart — WITHOUT redeploying skills. Use this to update connector source code (server.js, UI assets, plugins) quickly. Set github=true to pull files from the solution's GitHub repo, or pass files directly. Much faster than ateam_build_and_run for connector-only changes.
    Connector
  • Discovers the most relevant tools available on this MCP server for a given task using local semantic search (MiniLM-L6-v2 embeddings). Accepts a plain-English description of what needs to be accomplished and returns the best matching tools ranked by relevance, along with their input schemas, pricing tier, and exact call instructions. Use this tool first when you are connected to this server but do not know which specific tool to call — describe your goal and let platform_tool_finder identify the right capability. Do not use this tool if you already know the tool name — call that tool directly instead. Returns up to 10 results ranked by semantic similarity score.
    Connector
  • Search MidOS knowledge base for relevant information. Use this as your FIRST tool to discover what knowledge is available. Returns ranked results with titles, snippets, and quality scores. Args: query: Search query (keywords or topic) limit: Max results (1-20, default 5) domain: Filter by domain (engineering, security, architecture, devops, ai_ml) Returns: JSON array of matching atoms with title, snippet, score, and source
    Connector

Matching MCP Servers

Matching MCP Connectors

  • GitHub MCP — wraps the GitHub public REST API (no auth required for public endpoints)

  • Your AI Agent's Infrastructure Layer. Connect Claude, Copilot, Codex, or ChatGPT to 200+ managed open source services. Start databases, pipelines, and applications through natural language.

  • Get a single golf tournament by slug (e.g. 'the-masters', 'pga-championship', 'us-open', 'the-open' for Majors). Note: result/winner on finished tournaments may be null pending data backfill — consult primary sources for confirmed leaderboards.
    Connector
  • Discovers the most relevant tools available on this MCP server for a given task using local semantic search (MiniLM-L6-v2 embeddings). Accepts a plain-English description of what needs to be accomplished and returns the best matching tools ranked by relevance, along with their input schemas, pricing tier, and exact call instructions. Use this tool first when you are connected to this server but do not know which specific tool to call — describe your goal and let platform_tool_finder identify the right capability. Do not use this tool if you already know the tool name — call that tool directly instead. Returns up to 10 results ranked by semantic similarity score.
    Connector
  • Retrieves the DAG source code from a Cloud Composer environment. Use this tool when you need to understand DAG implementation details, for example to understand why a DAG run has failed, or to debug DAG's behavior. The tool returns the latest version of the source code.
    Connector
  • Show GitHub sync status for ALL tenants and solutions in one call. Requires master key authentication. Returns a summary table of every tenant's solutions with their GitHub sync state.
    Connector
  • Fetch SDK source code (type definitions, interfaces, hooks) from the open-source Web3Auth SDK repos. Use for REFERENCE and DEBUGGING only — to verify exact type shapes, constructor signatures, available hooks, and error types. Do NOT use this to discover features; many SDK options are internal or legacy. Always use get_example first for integration patterns.
    Connector
  • Push the current deployed solution to GitHub. Auto-creates the repo on first use. Commits the full bundle (solution + skills + connector source) atomically. Use after ateam_build_and_run to version your solution, or anytime you want to snapshot the current state.
    Connector
  • List the API key owner's open security findings across all scans. Use this to answer "what's my current exposure?" Filter by severity, status, or domain. Returns finding summaries; call get_scan for full detail. Requires API key.
    Connector
  • Retrieve the full JSON schema and details for a specific tool by name. Use after `search_tools` identifies relevant candidates.
    Connector
  • Fetch the full options chain (calls and puts) for one expiry date. Returns strike price, bid, ask, last price, implied volatility, open interest, and volume for every contract. Use this tool when: - You are researching options strategies for a stock or ETF - You need implied volatility across strikes for a specific expiry - You want to see open interest to gauge market sentiment Call GetOptionsExpirations first to get valid expiry dates. If expiry_date is omitted, returns the nearest available expiry. Source: Yahoo Finance via yfinance. No API key required.
    Connector
  • [READ] List open Shillbot marketplace tasks. Agents can browse content creation opportunities (YouTube Shorts, X posts, etc.) with on-chain escrow. Returns task IDs, briefs, payment amounts, and platforms. Shillbot-specific deep query with brief/blocklist/brand-voice details — for cross-source aggregated discovery use list_earning_opportunities instead.
    Connector
  • Fetch the complete source code of a Web3Auth integration example from GitHub. Returns all source files needed to understand how the integration works. Examples are the PRIMARY reference for integration patterns — always prefer example code over raw SDK source.
    Connector
  • Get a single golf tournament by slug (e.g. 'the-masters', 'pga-championship', 'us-open', 'the-open' for Majors). Note: result/winner on finished tournaments may be null pending data backfill — consult primary sources for confirmed leaderboards.
    Connector
  • Search FINRA BrokerCheck for registered individual brokers and financial representatives by name. Returns CRD number, current firm, registration status, and whether the individual has any disclosures on record. Use this tool when: - You need to find the CRD number for a named advisor or rep - You want to verify registration status for a specific individual - You are enriching a rep record that is missing a CRD Geographic workflow: if you don't know the rep's name, first use SearchBrokersByPlace to discover firms in an area, then use SearchBrokerCheckFirm to find the firm's CRD, then use this tool to find individuals at that firm. Narrow results with the optional 'state' parameter (2-letter code). To get the full profile after finding a CRD, use GetBrokerCheckDetail. Source: FINRA BrokerCheck public API. No API key required.
    Connector