Skip to main content
Glama
136,384 tools. Last updated 2026-05-18 09:05

"Linux Foundation" matching MCP tools:

  • Live capability snapshot of the responder's GPU sidecar — extensions[] (e.g. gpu, clay-v1.5, prithvi-eo2), cuda_available, models_loaded[], healthy, last_polled_unix_s. Refreshed every 30 s by a background poller; reads are constant-time. When to use: Call before scheduling a GPU-heavy plan (Clay / Prithvi / Galileo embeddings, foundation-anchored algorithms) so the agent knows whether the GPU tier is up *right now* without per-request /health round-trips. Pair with `emem_topics` (its `algorithm_availability` map says which algorithm keys can run given the current capabilities) and `emem_explain_algorithm` (full inference-tier metadata per algorithm). When `extensions[]` is empty the sidecar is unreachable — only CPU/scalar/cached tiers will produce facts; foundation-anchored materializers will sign Absence with `gpu_unavailable` reason.
    Connector
  • Look up grantmaking organizations by name, topic, or location. This tool searches 174K+ grantmaking organizations from IRS data using organization names plus grant-purpose/topic signals. Use it when you know the funder's name, want aligned funders for a cause area, or want to browse by location/size/NTEE code. Multi-word searches are ranked by relevance; simple browse/name fallback results are ordered by total assets. IMPORTANT: Use search_open_grants when the user needs active grant programs or RFPs. search_funders is for finding aligned grantmakers, including ones that may fund by relationship, LOI, or annual cycle rather than a live call. Args: query: Search term for a funder name or cause-area phrase. Example: "Ford Foundation", "global health", "community foundation" Topic searches work best with 2+ words. state: Two-letter US state code to filter by funder HQ location. Example: "CA", "NY", "TX" city: City name to filter by (case-insensitive). Example: "San Francisco", "New York" ntee_code: NTEE classification code to filter by. Example: "A20" (Arts Organizations), "B" (Education), "E" (Health) min_assets: Minimum total assets filter in dollars. Example: 10000000 (foundations with $10M+ assets) max_assets: Maximum total assets filter in dollars. Example: 100000000 (foundations with up to $100M assets) has_er_grants: Filter to foundations that make expenditure responsibility grants (grants to non-501(c)(3) entities like PBCs, for-profits, and foreign orgs). Set to True to find only ER-active funders. funder_type: Optional canonical funder_type to include. Examples: "community_foundation", "family_foundation", "corporate_foundation", "private_operating", "operating_nonprofit", "independent_foundation". Use this to narrow to a specific kind of grantmaker. exclude_funder_types: Optional list of canonical funder_type codes to exclude from results. Useful for hiding operating nonprofits that surface with large "annual_grants" but are not actually grantmakers — e.g., exclude_funder_types=["operating_nonprofit"] hides PATH and similar operating organizations. grantee_country_codes: Optional list of FIPS 10-4 country codes (e.g., "UK" for United Kingdom, "IN" for India, "KE" for Kenya, "SF" for South Africa) to restrict to funders whose grantees are located in those countries. Use this when the user is asking for funders that move money into a specific non-US geography. Country here is the grantee's HQ country, derived from foundation_grants. When set, the search is forced through the hybrid path; the ILIKE-only name-match path cannot filter by country. Distinct from `state`, which filters by the funder's own US HQ. country: Optional HQ country name (or list of names) to restrict to funders headquartered in those countries (e.g., "Germany", ["United States", "Canada"]). Distinct from `grantee_country_codes` (where the funder's grants land) and from `state` (US state of HQ). Use when the user asks for funders based in a specific country — e.g. "European-headquartered foundations" → country=["Germany","Spain","United Kingdom", "Switzerland","Netherlands","France"]. US foundations are included only when "United States" (or "USA") is in the list, or when the param is omitted. limit: Maximum number of results to return. Default: 20, Maximum: 50 Returns: Dictionary containing: - results: List of matching foundations with ein, name, city, state, total_assets, annual_grants, website_url, has_er_grants, has_pris, funder_type (when populated), topic_match_count (when query takes the hybrid topic-search path — see below) - total_returned: Number of results returned - query_params: The search parameters used - note: Helpful context about the results topic_match_count is the number of distinct grant-purpose strings under this funder that matched the FTS query. It surfaces only on topical searches (multi-word queries that route to the hybrid path) and only for 990-filer rows; ILIKE-only and non-990 rows omit the field. Rule of thumb: - topic_match_count == 1 → single tangential grant, often noise (e.g. a credit-union foundation surfacing for "telemedicine" because of one passing-mention grant) - topic_match_count >= 3 → substantive topical coverage Examples: search_funders(query="community foundation", state="CA") search_funders(query="global health", min_assets=100000000) search_funders(ntee_code="E", min_assets=50000000) search_funders(state="NY", city="New York", limit=10) search_funders(has_er_grants=True, state="CA") search_funders(funder_type="community_foundation", state="CA") search_funders(query="PATH", exclude_funder_types=["operating_nonprofit"]) search_funders(query="global health", grantee_country_codes=["IN"]) search_funders(query="climate resilience", grantee_country_codes=["KE", "SF"]) search_funders(query="youth education", country="Germany") search_funders(country=["Germany","Spain","Netherlands"])
    Connector
  • Vector delta between the same cell at two tslots: returns the per-element residual, its L2 norm (scalar change-magnitude), the cosine between the two source vectors (orientation drift), and both source fact CIDs so the agent can quote both attestations as evidence. When to use: Call when the user asks 'how much did X change between A and B' for a foundation embedding at one place. Pass `tslot_a` and `tslot_b` (must differ); default `encoder=geotessera`. For per-band scalar change (NDVI delta, elevation delta) use `emem_diff` instead.
    Connector
  • WRITE to the Knowledge Base. This tool has TWO modes: **MODE 1 — SAVE a new card**: Provide `content` with full Markdown following the ACTIONABLE schema below. **MODE 2 — REPORT OUTCOME**: Provide `kb_id` + `outcome` ('success' or 'failure'). WHEN TO USE: - Mode 1: After successfully fixing a bug IF no existing KB card covered it. - Mode 2: ALWAYS after applying a solution from `read_kb_doc` and running verification. INPUT: - `content`: (Mode 1) Full Markdown KB card content — follow the EXACT template below. - `overwrite`: (Mode 1) Set to True to update an existing card. - `kb_id`: (Mode 2) ID of the card to report outcome for. - `outcome`: (Mode 2) 'success' or 'failure'. - `enrichment`: (Mode 2, optional) Additional context to merge into the card when outcome is 'failure'. ━━━ CARD TEMPLATE (Mode 1) — copy this structure EXACTLY ━━━ ``` --- kb_id: "[PLATFORM]_[CATEGORY]_[NUMBER]" # e.g. WIN_TERM_001, CROSS_DOCKER_002 title: "[Short Title — max 5 words]" category: "[terminal|devops|supabase|fastmcp|network|database|...]" platform: "[windows|linux|macos|cross-platform]" technologies: [tech1, tech2] complexity: [1-10] criticality: "[low|medium|high|critical]" created: "[YYYY-MM-DD]" tags: [tag1, tag2, tag3] related_kb: [] --- # [Short Title — max 5 words] > **TL;DR**: [One sentence — what's the problem + solution] > **Fix Time**: ~[X min] | **Platform**: [Windows/Linux/macOS/All] --- ## 🔍 This Is Your Problem If: - [ ] [Symptom 1 — specific symptom or error message] - [ ] [Symptom 2 — specific error code or log line] - [ ] [Symptom 3 — environment/version condition] **Where to Check**: [console / logs / env / task manager / etc.] --- ## ✅ SOLUTION (copy-paste) ### 🎯 Integration Pattern: [Global Scope] / [Inside Init] / [Event Handler] ```[language] # [One-line comment — what this code does] [depersonalized code WITHOUT specific paths, use __VAR__ for things to replace] ``` ### ⚡ Critical (won't work without this): - ✓ **[Critical Point 1]** — [why it's essential] - ✓ **[Critical Point 2]** — [common mistake to avoid] ### 📌 Versions: - **Works**: [OS/library versions where confirmed working] - **Doesn't Work**: [OS/library versions where known broken] --- ## ✔️ Verification (<30 sec) ```bash [single command to verify the fix worked] ``` **Expected**: ✓ [Specific output or behavior that confirms success] **If it didn't work** → see Fallback below ⤵ --- ## 🔄 Fallback (if main solution failed) ### Option 1: [approach name] ```bash [command] ``` **When**: [condition to use this option] | **Risks**: [what might break] ### Option 2: [alternative approach] ```bash [command] ``` **When**: [condition] | **Risks**: [what might break] --- ## 💡 Context (optional) **Root Cause**: [1 sentence — why this problem occurs] **Side Effects**: [what might change after applying the fix] **Best Practice**: [how to avoid this in future — 1 point] **Anti-Pattern**: ✗ [what NOT to do — common mistake] --- **Applicable**: [OS, library versions, conditions] **Frequency**: [rare / common / very common] ``` ━━━ END OF TEMPLATE ━━━ RULES for ACTIONABLE cards: 1. Solution FIRST — after diagnosis, code immediately 2. Depersonalize — no names, project names, or absolute paths 3. Use `__VAR__` markers for anything the user must replace 4. One Verification command, result visible in <30 sec 5. Fallback — 1-2 options max, always include When/Risks 6. Context at End — WHY is optional reading for curious agents
    Connector
  • Search for verified local service providers across 9 trade categories: floor coating (epoxy/polyaspartic), radon mitigation, crawl space repair, laundry pickup & delivery, mold/asbestos abatement, basement waterproofing, foundation/slab repair, septic pump services, and water damage restoration. Returns provider name, rating, review count, business status, services offered, certifications, years in business, and a link to the full profile with contact details. Each provider includes Google Maps URL when available. Covers major US metro areas. Use list_niches first to get valid niche IDs, and list_service_types for valid service_type values.
    Connector
  • List available MCP tools and get detailed help. Use this tool to discover what tools are available and how to use them. Call without parameters to see all tools, or provide a tool name to get detailed help including parameters, examples, and related tools. Args: tool_name: Optional name of a specific tool to get detailed help for. Example: "search_funders", "get_funder_profile" Returns: If called without parameters: - server_name: Name of the MCP server - server_version: Current version - total_tools: Number of available tools - tier: Current access tier (free) - rate_limit: Rate limit information - tools: List of available tools with names, descriptions, and examples If called with tool_name: - tool: Detailed tool information including: - name: Tool name - description: What the tool does - parameters: List of parameters with types, descriptions, and examples - examples: Example usage - related_tools: Tools that work well together with this one Examples: list_tools() # See all available tools list_tools(tool_name="search_funders") # Get detailed help for search_funders list_tools(tool_name="get_funder_profile") # Get help for get_funder_profile
    Connector

Matching MCP Servers

Matching MCP Connectors

  • Foundation discovery and grant intelligence for nonprofits. 174K+ US funders, IRS 990 data.

  • GLEIF MCP — Global Legal Entity Identifier Foundation (free, no auth)

  • Fans out across every wired foundation-embedding encoder (`geotessera`, `clay_v1`, `prithvi_eo2`) for one cell and returns a structured per-encoder state map. Each encoder is attempted independently; encoders that fail at this cell surface under `missing` with a typed reason instead of killing the request. When to use: Call when the agent wants cross-encoder consensus (do Tessera, Clay, and Prithvi agree on the archetype here?), redundancy-aware reasoning (which encoder is freshest at this cell?), or a concatenated multi-encoder state for downstream linear probes. Pass `encoders: [...]` to override the default foundation set.
    Connector
  • Dense state vector for a place. Two views: `encoder` (single foundation embedding at its native dim — 128-D Tessera, 1024-D Clay, 1024-D Prithvi) and `cube` (the full 1792-D voxel concatenated across every wired band, with per-band coverage manifest and full-fidelity extras for any encoder whose native dim exceeds its cube slot). When to use: Call when the agent needs a dense, ready-to-feed vector for downstream similarity / linear-probe / clustering, or wants a single rebindable handle (`memory_token` / `state_cid`) for a place. Default `view=encoder` (cheap, single recall) — pass `encoder` (default `geotessera`) to pick the band. Pass `view=cube` for the responder's full attested view at the cell; the response carries `coverage[]` so an agent can distinguish attested-zero (signed Absence) from not-yet-materialised, and `extras[]` preserves full Clay/Prithvi 1024-D vectors when the cube truncates to a 384-D slot. Pair with `emem_find_similar` for k-NN, `emem_compare` for two-cell cosine, or `emem_verify_receipt` to verify the signed payload offline.
    Connector
  • Search open grant opportunities from Kindora's active foundation-program corpus and federal government grants. Searches both private foundation grant programs (from IRS data and funder websites) and federal government grant opportunities (from Grants.gov). Uses full-text search with natural language understanding — queries are parsed into individual terms with stemming, so "youth after school programs" matches programs about youth, after-school, and programming even if those exact words don't appear together. Search covers program names, descriptions, focus areas, beneficiary types, and geographic focus fields. Use the state parameter to focus on geographically relevant opportunities. Query syntax: - Natural language: "affordable housing for seniors" (matches any of these terms) - Quoted phrases: '"after school"' (matches exact phrase) - Exclusion: "education -higher" (matches education, excludes higher education) - Combine: '"mental health" youth -adult' (phrase + term + exclusion) - No query: returns broadly open programs sorted by upcoming deadlines (browsing mode) Args: query: Natural language search query. Searches across program names, descriptions, focus areas, beneficiary types, and geographic focus. Supports quoted phrases for exact matching and -term for exclusion. Example: "youth outdoor education", "affordable housing", "STEM education for girls", "food bank hunger", "climate change environment", "domestic violence women" focus_area: Filter foundation programs by focus area (matches values in focus_areas array). Example: "Education", "Health", "Environment" agency: Filter government grants by agency name (case-insensitive). Example: "Department of Education", "NSF", "NIH" state: Two-letter US state code to filter by geographic relevance. Returns programs focused on that state plus nationally available programs. Example: "CA", "NY", "TX" country: Country name for non-US geographic filtering. Returns programs whose geographic_focus is tagged for that country plus any tagged Global / International / Worldwide. Use this instead of state for international queries — passing "India" via state would error because state requires a US code. Mixing state with a non-US country is rejected. Example: "India", "Kenya", "Mexico", "Global" deadline_days: How far ahead to search for deadlines, in days. Default: 90 (3 months). Maximum: 365 (1 year). Rolling/always-open programs are always included regardless. min_award: Minimum grant size filter in dollars. Example: 50000 (grants of $50K+) max_award: Maximum grant size filter in dollars. Example: 500000 (grants up to $500K) nonprofit_only: Only show nonprofit-eligible government grants. Default: True source: Filter by grant source type. Options: "foundation" (private foundation programs only), "government" (federal grants only), or omit for both sources combined. PREFER omitting this — the foundation corpus is much larger, and filtering to government-only often returns few or zero results. limit: Maximum number of results to return. Default: 20, Maximum: 50 Returns: Dictionary containing: - results: List of open grant opportunities with: - source: "foundation" or "government" - title: Program or grant name - description: Brief description - funder_name: Foundation name or government agency - funder_ein: Foundation EIN (null for government) - funder_state: Foundation's state (null for government) - deadline: Date string, "Rolling", "LOI Open", or "Open" - deadline_type: "specific_date", "rolling", "loi_open", "always_open", "annual_cycle" - days_until_close: Days until deadline (null for rolling) - grant_range: Formatted grant size range (e.g., "$50,000 - $500,000") - focus_areas: List of focus areas - geographic_focus: Geographic eligibility - application_url: Where to apply - total_returned: Number of results - query_params: Search parameters used - summary: Counts by source, urgent deadlines, and rolling programs - note: Helpful context about the results Tips for effective searches: - Combine state + query for geographically targeted results - If the user gives a specific foundation name, use search_funders first - Use natural language — describe what you're looking for in plain terms - Try multiple specific searches rather than one broad search - Use source="foundation" for private grants with rolling/LOI deadlines - Omit query entirely to browse open programs by upcoming deadline IMPORTANT — presenting results to users: - Focus on what was found, not what wasn't. Present results positively. - Do NOT comment on corpus size, data limitations, or coverage gaps. - If few results are returned, suggest trying related keywords or using search_funders to find aligned foundations — many accept unsolicited inquiries or run annual grant cycles that may not have an open window right now. Frame this as "here are additional prospects to explore" not "the search didn't find enough." - Many excellent funders don't post public open calls — they fund through relationships, LOIs, and nominations. Use search_funders and get_funder_profile to identify these funders as proactive prospects. Examples: search_open_grants(query="youth outdoor education", state="CA") search_open_grants(query="affordable housing", state="NY", source="foundation") search_open_grants(query="STEM education for girls", state="TX") search_open_grants(query="food bank hunger", min_award=10000) search_open_grants(query="mental health services", state="CA") search_open_grants(query="climate change environment", source="foundation") search_open_grants(source="government", nonprofit_only=True, state="NY") search_open_grants(focus_area="Environment", source="foundation") search_open_grants(query="community health workers", country="India") search_open_grants(query="climate resilience", country="Global") search_open_grants() # Browse open programs by upcoming deadline Related tools: - search_funders: Find grantmaking organizations by name or location — use this alongside search_open_grants to identify foundations that may be a good fit even if they don't have a posted open grant right now - get_funder_profile: Get detailed profile for a specific foundation - get_foundation_grants: See past grants made by a foundation
    Connector
  • Parse unstructured provenance text into structured entries. Read-only — does NOT save. TRIGGER: User pastes provenance text, gallery records, auction history, or says "here's the provenance," "this passed through Gagosian." Flow: parse_provenance → present results for review → save_provenance. Never skip the review step. After confirmation, call save_provenance to write entries to the catalogue. YOU (the connected AI) do the parsing — this tool does not call a server. Parse the text into structured entries and pass them as the `entries` parameter. Each entry needs at minimum: holder_name. Also extract: holder_type (individual/gallery/museum/auction_house/institution/private_collection/foundation/unknown), holder_city, holder_country, event_type (sold/gifted/bequeathed/returned/exchanged/inherited/seized/found/transferred/created/unknown), date_start_year, date_start_display (human-readable, e.g. "ca. 1960", "by 1965"), date_end_year, date_end_display, date_start_approximate/date_end_approximate (boolean), certainty_level (certain/probable/possible), gap_before (boolean if gap in chain), and notes. Return entries in chronological order (earliest first). IMPORTANT: If the text describes a consignment, loan, or deposit, do NOT extract those as provenance entries. Those are custody events (the work moves physically but ownership does not), tracked on a separate timeline. Use create_custody_event to record them instead, with kind=consignment or kind=loan (historical "deposit" language in old catalogues maps to loan).
    Connector
  • Get detailed information about a specific ICD-11 entity by code or URI. Use this tool to: - Get the full definition of a disease - Retrieve coding notes and exclusions - Get the official title and synonyms Provide either an ICD-11 code (e.g., "BA00") or a full foundation URI.
    Connector
  • Get the Senzing JSON analyzer script with commands to validate and analyze mapped data files client-side. The analyzer validates records against the Entity Specification AND examines feature distribution, attribute coverage, and data quality. Returns the Python script (no dependencies) with instructions. No source data is sent to the server — the LLM runs the script locally against your files. REQUIRED parameter: `workspace_dir` (a writable directory where the script and any reports are saved). Do NOT assume /tmp exists (some environments like Kiro do not provide it). Typical values: Linux `/tmp` or `~/sz-workspace`; macOS `~/sz-workspace`; Kiro/sandboxed an explicit path under your home.
    Connector
  • Check server health and connectivity. Returns: Dictionary with health status including: - status: "healthy" or "unhealthy" - version: Server version - environment: Current environment (dev/staging/prod)
    Connector
  • Search the Global Legal Entity Identifier Foundation (GLEIF) database for Legal Entity Identifiers (LEIs) by entity name. Returns the 20-character LEI code, legal name, registration status, legal address, and jurisdiction. Use this tool when: - You need the LEI for a financial institution or fund company - You want to verify the legal registration of a firm - You are cross-referencing SEC EDGAR entities with their global LEI - You need to look up parent/subsidiary relationships (use GetLEIDetail) LEIs are required for regulatory reporting under MiFID II, EMIR, and Dodd-Frank. Cover 2M+ legal entities globally across 200+ jurisdictions. Source: GLEIF API (api.gleif.org). No API key required.
    Connector
  • Use when someone asks about Jennifer Rebholz's published articles, Arizona Attorney Magazine columns, formal written work, or her Bar Foundation oral history contribution. Returns her published works with titles, publications, dates, and links.
    Connector
  • Create a new entity — a person, gallery, museum, auction house, institution, foundation, or collector referenced in the catalogue. Always call suggest_entity first to check for duplicates before creating. Entities are used throughout the catalogue for provenance holders, exhibition venues, bibliography authors, and sale buyers. Include city and country when known to help with deduplication.
    Connector
  • List all available service directories in the LocalPro network. This is the starting point for discovering what categories of verified local service providers are available. Categories include floor coating, radon mitigation, foundation repair, basement waterproofing, crawl space repair, mold/asbestos/lead remediation, septic services, and laundry services. Returns niche IDs needed for all other tools.
    Connector
  • List all available service directories in the LocalPro network. This is the starting point for discovering what categories of verified local service providers are available. Categories include floor coating, radon mitigation, foundation repair, basement waterproofing, crawl space repair, mold/asbestos/lead remediation, septic services, and laundry services. Returns niche IDs needed for all other tools.
    Connector
  • Authoritative ICD-10 → ICD-11 mapping using WHO transition tables (release 2025-01, bundled with the server). Returns the primary 1:1 ICD-11 category for the ICD-10 code plus any alternative ICD-11 candidates that WHO documents (some ICD-10 concepts split into multiple ICD-11 entities). For each mapping, includes the ICD-11 code, title, chapter, and the Foundation URI / Linearization URI for navigating to the full entity definition. Use this for clinical coding, billing migration, retrospective analysis, and any workflow that needs authoritative mapping rather than text-search candidates. Coverage: 11,243 ICD-10 categories (excludes chapters and blocks like "A00-A09" which aren't used in clinical coding). Provide a code like "E11" (Type 2 diabetes), "I21" (Acute MI), or "A07.8" (4 alternatives in WHO's table). Both dotted ("A07.8") and undotted ("A078") forms are accepted. Returns "no mapping" when the code isn't in the WHO category-level table — that's the honest answer rather than a fuzzy search fallback.
    Connector
  • Check if a skill is compatible with a specific platform before downloading. / 다운로드 전 호환성 검증. requirements(python/packages)와 platform_compatibility 기준으로 compatible 여부를 반환. Args: skill_id: 검증할 스킬 ID python_version: 에이전트 Python 버전 (예: "3.11.2") os: "linux" | "darwin" | "windows" installed_packages: {"requests": "2.31.0"} 형태 dict (선택) target_platform: 설치 대상 플랫폼 ("ClaudeCode" 등) Returns: 요약 문자열 (compatible 여부 + 누락 패키지 + 추천 설치 명령)
    Connector