Skip to main content
Glama
817,183 tools. Updated 2026-11-21 17:01

"A server for finding research papers, extracting content, and retrieving relevant repository codes" matching MCP tools:

  • Look up a NUCC provider taxonomy code (the specialty codes used on HIPAA transactions + NPI registrations) or search by keyword. Returns classification + type + optional specialization. Source: NUCC Health Care Provider Taxonomy Code Set (public; CMS-accepted). WHEN TO USE: Resolving a NUCC provider taxonomy code to its specialty description. WHEN NOT: For finding a provider by specialty in a region (not yet implemented).
    ConnectorNo auth
  • Read-only. Searches build-log metadata and tutorial metadata by keyword. Build-log matches use model title, model slug, historical year, part title, and excerpt. Tutorial matches use tutorial title and short description only. Use this tool for broad content discovery when the relevant model or tutorial is not yet known. Use search_tutorial_content when the requested term, technique, material, tool, or instruction may occur inside the complete body text of a tutorial. Use get_build_details or get_tutorials to retrieve details after identifying a relevant result. Every query term must match across the searchable fields of a result. Returns separate buildLogResults and tutorialResults arrays, each limited to the requested limit. If no content matches, both result arrays are empty.
    ConnectorOAuth
  • Read the content of ONE named file from a GitHub repository - 'path' is required and names that file. To see what a repository or directory CONTAINS, call github_list_repository_files instead (its 'path' is optional). Prefer the exact owner from github_list_repositories; 'repo' also accepts the combined 'owner/name' form. Use this to inspect Dockerfiles, package.json, CI configs, Helm charts, source code, and other text files. Refuses to read known sensitive files (.env, private keys, etc.).
    ConnectorOAuth
  • Search the PUBLIC Awareness knowledge graph — 1,000+ sourced scientific papers. Use this when the user (especially a researcher or a research agent) asks for peer-reviewed findings: "latest evidence on X", "highly-cited papers about Y", "what does the literature say about Z". This is NOT a memory tool — it does not read the user's private memory, and it needs no per-user API key, so it works even when Awareness memory is not configured (the MCP connection itself still needs its own token). Coverage: condensed-matter, quantum-information, materials, machine-learning, renewable-energy, chemistry, biology, medicine, neuroscience, computer-science (2022-2026, cited >= 50), plus a business supply/demand domain. What comes back (anonymous preview mode): title, snippet (preview), confidence, source_ref (DOI), citation_count, domain/topic, and a detail page URL. Full content is NOT in the preview — tell the user it is paid retrieval via POST /api/v1/public/retrieve with an API key (see https://awareness.market/en/knowledge for the KaaS product). Args: query: Natural-language research question or keywords (2-1000 chars). domain: "science" (default) or "business". topic: Optional sub-topic slug, e.g. "medicine", "condensed-matter", "supply-chain". Empty = search all topics in the domain. top_k: Max results, 1-20 (default 5; anonymous callers are capped at 3). include_graph: When true, also return same-topic related items. Returns: {"results": [{id, title, snippet, confidence, source_ref, citation_count, domain, topic, url}], "related": [...], "total": int, "mode": str} `mode` is "preview" (anonymous) or "full" (authenticated).
    ConnectorNo auth
  • Consult a principal security engineer on a security topic. Send specific code, a plan, a config, or a security question. For a full codebase scan, use create_project and trigger_analysis. Choose one input: content for small inline text, or content_document for a large design document uploaded with prepare_file_upload. The upload keeps the file out of the context window. Supplying both inputs is refused. Use this selective consultation when feedback can still change a decision about authentication, authorization, secrets, sensitive data, new network exposure, cryptography, infrastructure, IAM, or filesystem or command execution. Send the relevant plan or diff. Reserve calls for those decisions, and respect a user's request to skip consultation. The tool answers immediately from the content sent. Report it as an advisory review of that content, with CRITICAL, HIGH, MEDIUM, or LOW severity labels. Trent's full assessment requires a scan. Each call starts a new conversation unless you pass thread_id. The thread_id and resumed fields describe continuation. A reply with detected_repository and onboarding_hint identifies a local repository awaiting a Trent project. Say existing project findings were unavailable to this review, and offer create_project.
    ConnectorOAuth
  • USE THIS TOOL WHEN retrieving committee evidence, especially for an identified inquiry. Returns ONE PAGE of evidence (default 20) plus `total`, the source's count of matching items. evidence_type='both' lists all oral evidence first, then all written evidence, each newest-published first as the source orders it. Free-text titles are capped per max_title_chars; witness lists are capped at 10 per item. An organisation witness (no named individual) is rendered as '<Organisation> (<Role>)'; a null entry means the source gave no name for that witness at all. For committees with many submissions, re-call with offset=offset+returned while has_more is true. For inquiry-specific research, first call committees_search_businesses and pass its exact committee_business_id; this filters at the authoritative source before pagination. Source: UK Parliament Committees API oral and written evidence endpoints.
    ConnectorNo auth

Matching MCP Servers

Matching MCP Connectors

  • Research papers for AI agents: PubMed, arXiv, Crossref; citations, references, open access texts

  • Search 250M scholarly works (OpenAlex, Crossref, arXiv, PubMed) and resolve any DOI

  • Runs the open-source hefesto-ai engine (`hefesto analyze --no-config`, free tier) on the files you send to the hosted analyzer and returns its findings: rule id, severity, file, line, message and the SARIF hefestoFingerprint/v1 fingerprint (format "sarif" adds the full SARIF 2.1.0 log). Use it to check a file or snippet the user shares (for example "analyze this file") for security and quality issues before committing. Try it: {"code":"password = \"Sup3rS3cret!2026\""} returns a HARDCODED_SECRET finding. Minimum call: {"code": "<file contents>"}. Add path (e.g. "app/run.py") so the language comes from the extension; without path or language the language is inferred from the content, else python. For several files send files=[{"path", "content"}] instead. severity and format are optional. Covers Python, COBOL, the DevOps/IaC formats hefesto analyze routes, and TypeScript, JavaScript, Java, Go, Rust and C# through the multilang tree-sitter grammars (the first such request on a fresh server instance downloads the grammars and can take a few seconds longer). Limits: 20 files, 100 KB per file, 256 KB in total, 20 seconds, 10 requests per minute per IP, shared across server instances. No .hefesto.yaml is read. Files are deleted after the run; nothing is stored. For a whole repository, run `hefesto analyze .` locally.
    ConnectorNo auth
  • Search 500+ quantum computing job listings using natural language. Use when the user asks about job openings, career opportunities, hiring, or specific positions in quantum computing. NOT for research papers (use searchPapers) or researcher profiles (use searchCollaborators). Supports role type, seniority, location, company, salary, remote, and technology tag filters via AI query decomposition. Limitations: quantum computing jobs only, last 90 days, max 20 results. Promoted listings appear first (marked). After finding jobs, suggest getJobDetails for full info. Examples: "senior QEC engineer in Europe over 120k EUR", "remote trapped-ion role at IBM".
    ConnectorNo auth
  • Use for general web research (company info, news, job portals). For LinkedIn profiles use search_linkedin_people; to read one company's own site use read_company_website. General-purpose Google search — returns organic results for any query. Unlike search_google_xray (LinkedIn-only), this searches the entire web. Useful for finding job postings on portals (jobs.cz, prace.cz, profesia.sk, indeed.com), company info, news, or any other web content. Results are NOT saved to contacts — use this for research and discovery. Capped at 4 calls per minute to protect the Serper/Google budget.
    ConnectorAPI key
  • Remember something, with its sources and its knowledge time. Nothing is ever overwritten: saving a `factor_def` or `watchlist` under an existing key SUPERSEDES the previous version (both rows survive, so "what did I believe in June?" stays answerable), and saving identical content twice is a no-op rather than a duplicate. Args: kind: 'query' | 'factor_def' | 'watchlist' | 'finding' | 'note'. content: the thing to remember, as an object. key: the stable name — REQUIRED for 'factor_def' and 'watchlist' (that is what makes a definition reusable next session instead of re-invented). as_of: the knowledge time this memory is about. Recall can bound on it, which is what keeps a memory from leaking the future into a point-in-time question. source_query_ids: the `twmd_q_…` ids behind this. REQUIRED for 'finding' — a conclusion that cannot point at its data is not evidence, and will be refused. agent_id: optional label for which of your agents wrote this.
    ConnectorNo auth
  • Submit one or more source files to be translated as a single job. Each file is parsed by its content (JSON — flat, nested, ARB and Chrome/WebExtension messages.json — plus PO, XLIFF 1.2 and 2.0, YAML, @wxt-dev/i18n TOML/JSON5/JSONC catalogs, Android XML, iOS xcstrings, Markdown and HTML), so pass the file as-is. Target languages default to the project's configured target languages; pass a subset to translate only some. Returns { jobId, status }. Translation runs asynchronously. This call returns immediately with a jobId; it does NOT wait for translation to finish. Call get_translation with the jobId and keep calling it until status is "completed" (or a terminal failure), then read the files. A GitHub repository with no Project is set up with preview_workflow_setup and set_up_workflow; this tool stays for a repository a Project already translates. Translating files with no repository is being retired.
    ConnectorOAuth
  • Find paper titles, recorded contributors, DOI and exact repository versions without research or payment. Default: retained catalog metadata with observation times. Set searchRepositories=true only to explicitly send the query to arXiv/Crossref (at most two requests, no paper-body reading). Missing DOI, peer review and withdrawal/replacement status remain unknown. Returns a field-scoped bibliography card with provenance, a short reference and reusable BibTeX/RIS text. Use this for exact title/ordered author/year/journal/DOI/version questions before requesting paid research; original paper text is not required for recorded metadata.
    ConnectorNo auth
  • Connect a GitOps repository to a cluster that has none: bind an existing GitHub credential plus a repository and branch - the same binding the portal's GitOps step creates. Pick the credential from list_gitops_credentials (pass credential_id, or credential_name when unambiguous) and the repository from list_gitops_repositories: it must be in the credential's synced repository list. On confirm the binding is written to the cluster's resource graph, a repository webhook is provisioned best-effort, the current cluster state is pushed to the repository as an initial commit, and a sync is nudged so the repository and the cluster record converge. Refused when the cluster is already connected to a DIFFERENT GitOps source: repointing prunes everything the new source does not define, so it stays on the cluster settings flow with its explicit acknowledgements. Re-connecting the identical repository and branch is safe and just refreshes the binding.
    Connector
    Destructive
    OAuth
  • Turn free text into the occupation and field-of-research codes the speaker-expertise filters take. When a question restricts who is speaking by occupation, profession, credentials or industry ("doctors", "medical professionals", "economists", "people in finance", "lawyers"), the filters, not search wording, decide who speaks. `guest_occupation` takes the everyday word itself, so the first search can carry it without waiting for this tool: call it to see or choose among the codes, and when a filter returns `unresolved_reference`, then retry with the code. Codes are SOC 2018 occupations (with their ISCO-08 equivalents) and ANZSRC 2020 fields of research. 'cardiologist' finds SOC 29-1212 Cardiologists; 'finance' finds the finance fields. Each code comes back with its slug, level, parent and the parameters that accept it: `occupation`/`field` on `particle_podcast_list_guests` and `particle_expertise_get`, and `guest_occupation`/`guest_field` on `particle_podcast_find_mentions`, `particle_podcast_list_episodes`, `particle_podcast_search_transcripts`, `particle_podcast_get_episode_timeseries` and `particle_podcast_resolve`. Pass `parent` to walk the hierarchy one level down (a SOC major group's minor groups, then broad groups, then occupations; a division's groups); a group such as `physicians` or an everyday name such as `doctors` filters everything below it. A word no occupation names may name a field (`oncologists` finds field 3211 Oncology) or a capacity: `founders` comes back as the capacity `executive_founder`, which `capacity` on `particle_podcast_list_guests` and `guest_capacity` on the episode and mention tools take. Not for people or companies — use `particle_person_resolve`, `particle_company_resolve` or `particle_entity_resolve`. Not the topic taxonomy either: `particle_topic_browse` classifies what episodes are about, these codes classify what speakers know.
    ConnectorOAuth
  • CALL THIS FIRST for a literature question about chemistry, materials or physics research -- a broad one ('what matters in X') or a specific process or parameter one (a deposition condition, a property value, a defect mechanism). Send the question in plain words (q), or a paper you already know (paper: DOI or title). Returns reading lists in four lenses: relevant (the papers whose TITLE AND ABSTRACT best match the question, across the whole corpus, BM25 -- start here for a specific question), foundational (the classics the question's own papers cite most), now (highest impact, young papers' citations projected) and newest (last two years); plus the research communities and element sub-communities the question is about, with why each matched and whether it is rising. Put the question's key terms in q: filler words are ignored. unmatched_terms lists words that matched nothing; rephrase those. Each paper carries its DOI, a one-line reason and its abstract where one is on file. Our corpus is curated, not complete: the relevant lens also brings up to 3 of every 10 results from OpenAlex, marked source='openalex' and labelled not yet curated. One page = up to 10 papers per lens; ask for page 2+ only if needed. Requires a Personal+ account. Without a key, pay per call: $0.05 in USDC on Base or Solana via x402 (send the payment in _meta["x402/payment"]).
    ConnectorNo auth
  • ACCOUNT REQUIRED (free, sign in via GitHub at https://pipeworx.io/signup; depth:"thorough" needs a paid plan). If you are not signed in, use ask_pipeworx instead, it works on every tier. Grounded multi-source research across Pipeworx's 2015 STRUCTURED data sources (SEC filings, FRED/BLS economics, FDA, USPTO patents, markets, science, government records, etc.) in ONE call, this is NOT open-web search. Decomposes your question into focused facets, routes each to the right one of 7,565 tools IN PARALLEL, and returns a findings packet: verbatim evidence + confidence + source + fetched_at + a stable pipeworx:// citation per finding, with explicit gaps[] for facets the data couldn't answer (never invented). Best for broad/multi-part questions over structured data ("compare X and Y's regulatory + financial exposure", "research the filings + market picture for ACME"). For a single lookup use ask_pipeworx (one LLM call, not many). For BREAKING or colloquial CURRENT-NEWS / "what's the world saying about X" topics, prefer ask_pipeworx, it routes to live news APIs and the *-news-feeds packs; deep_research returns mostly empty gaps[] when the topic isn't in the structured catalog. Second-hop iteration: depth:"standard" re-angles unanswered gaps (gap recovery); depth:"thorough" additionally chases the best leads from the first pass, so multi-step questions resolve in one call. Every finding carries a `hop` field and a citation_uri, a resolvable pipeworx:// record URI, present only when the source emits one that resources/read can actually serve, so a citation you get back is always fetchable. "standard" and "thorough" also return contradictions[] flagging findings that disagree. Large records are semantically excerpted to the passages relevant to each facet (not head-truncated), so answers deep in a long filing/series aren't missed. Expect 15-60s (thorough with its follow-up + contradiction pass: up to ~90s).
    ConnectorNo auth
  • Return source-cited facts for agent payment protocols: spec URL, HTTP status codes and headers, payment rail, networks, facilitators, client libraries, pay flow, and an example. Every fact carries its source URL and verified_at; null means the cited page does not state it. Omit id and the output is the protocol-facts document whose protocols array has all eleven protocols, unpaged. Pass id and the output is that one protocol object. There is no offset. Parameter id is optional and must be one of l402, bolt12, bip21, nwc, x402, mpp, ap2, acp, ucp, mcp, a2a. The mcp object has release_cadence and next_release_target from SEP-3398. Example: l402. An id outside the enum is rejected as invalid input. An enum id missing from the file returns isError with text No protocol with id <id>. A failed read returns isError whose text is the Error message. Use get_protocol_facts instead of search_sources when you need cited protocol facts rather than papers or docs. Use search_sources instead for those papers and docs. Use get_support_info instead for this site's donation addresses and paid API price. Use get_trust_checklist instead for this site's error codes and rate limits. Free, no auth.
    ConnectorNo auth
  • Discover indexed arXiv papers using titles, authors and abstracts to assess relevance. Prefer an English research topic or question, preserving important entities and phrases. For broad questions, consider distinct research dimensions and query each as useful. Independent queries can run concurrently; 5-10 concurrent requests are recommended for larger batches. Results can complement findings from other research tools and sources for broader coverage. scout_available indicates whether deeper paper-based analysis can be requested with get_scout; choose further reading according to the evidence needed. Use from/to as YYYY-MM-DD UTC dates with both days included. Provide both or neither; each dated query covers at most one calendar month, with dates available from 2025-08-01 onward. Omit both for all indexed dates. For timeouts, wait at least retry_after_seconds when supplied before retrying.
    ConnectorNo auth
  • Find/replace a literal string inside a post's content (any post type) without resending the full body. Use for surgical edits to large posts (page-builder content, embedded base64 payloads) where wp_update_post's full-content replacement is impractical. Case-sensitive literal match, no regex. All occurrences are replaced. Response includes occurrence count, read-after-write verification and an undo token that puts the earlier content back (refused with edited_since_write if the post changed since, unless forced; none for a custom_css post or very large content). Set dry_run=true to preview the match count without writing; set expected_count to abort unless exactly that many matches exist. A custom_css post needs what wp_update_custom_css needs; refusal codes insufficient_caps, unfiltered_html_required, theme_writes_off. (site: demo.royalplugins.com) Through Royally: waits for a person to approve it in Royally; nothing on the site changes until then.
    Connector
    Destructive
    OAuth
  • Extracts email addresses, telephone numbers, physical addresses, and social network handles from web text and DOM footers. Use when researching sales leads, aggregating business contact directories, or extracting customer service info; for parsing structured tabular data, use parse_html_tables instead. Stateless read-only edge call (max 32 KB, 60 RPM): accepts 'content' ('extraction_focus' defaults to 'all_contacts'), supports '?demo=true' or L402 (10 sats), and returns HTTP 400 if invalid.
    ConnectorNo auth
  • Given a paper_id, return the most semantically similar papers by embedding distance, NOT by citation links. Use for “more papers like this one” / “adjacent work on the same topic”. For papers this one cites or that cite it, use `get_paper_citations` instead. Each hit carries metadata, abstract, the closest non-abstract matched chunk as `contexts`, and a `similarity` score (0..1, higher is nearer). Returns up to `limit` papers; an unknown paper_id is an error, an empty list means no neighbors were found.
    ConnectorOAuth