Skip to main content
Glama
133,828 tools. Last updated 2026-05-25 06:14

"A platform for organizing and managing data with Airtable" matching MCP tools:

  • DEPRECATED — use create_tmb_job instead. Posts a job as an on-chain TMB contract with platform resolver and dispute protection. This tool returns an error directing you to create_tmb_job.
    Connector
  • Fetch complete campaign detail for one campaign. Required input: campaign_id. Output includes a campaign object with public campaign fields plus creator_wallet_address, and a separate funding_progress object with goal_amount, funded_amount, and percent_funded. Does not include creator_email. zooidfund does not verify campaign accuracy. Agents are responsible for their own verification. The platform makes no representations about campaign claims.
    Connector
  • List locales supported by the Molt2Meet platform. Returns the URL slug (e.g. 'en', 'nl', 'pt-BR') you pass as the 'locale' field on register_agent, plus the BCP 47 culture name, native-language display name, and which locale is the platform default. No authentication required. Use this before register_agent if you want to set a persistent language for payment pages and future localized responses.
    Connector
  • [IN DEVELOPMENT] [READ] Aggregated list of earning opportunities across the swarm.tips ecosystem. Includes Shillbot tasks (claim via shillbot_claim_task — first-party deep integration with on-chain Solana escrow + Switchboard oracle attestation), plus external bounties from Bountycaster, Moltlaunch, and BotBounty (each entry's `source_url` is a direct off-platform redirect — agents claim through the source platform itself, swarm.tips does not mediate). Each entry includes source, title, description, category, tags, reward amount/token/chain/USD estimate, posted_at, and (for first-party sources only) a `claim_via` field naming the in-MCP tool to call. This is the universal entry point for earning discovery — prefer it over per-source listing tools when they exist.
    Connector
  • Return a curated snapshot of currently-live audit competitions and bug-bounty programs across Code4rena, Cantina, Sherlock, and direct-protocol channels. Useful for solo wardens triaging which contests to enter. Snapshot updates with each cipher-x402-mcp release; treat the data as a hint, always cross-check the platform before submitting. Free, no payment required.
    Connector
  • Retrieve the full GLEIF LEI record for one legal entity using its 20-character LEI code. Returns legal name, registration status, legal address, headquarters address, managing LOU, and renewal dates. Use this tool when: - You have a LEI (from SearchLEI) and need full entity details - You want to verify the registration status and renewal date - You need the exact legal address and jurisdiction of an entity Source: GLEIF API (api.gleif.org). No API key required.
    Connector

Matching MCP Servers

Matching MCP Connectors

  • Airtable MCP Pack — wraps the Airtable REST API v0

  • Free MCP tools: the only MCP linter, health checks, cost estimation, and trust evaluation.

  • List devices registered in the workspace. Returns a list of Device objects with id, name, status, last_heartbeat, platform/hardware info, tags, and created_at. ``status`` is ``online`` if a heartbeat was received within the last 5 minutes, otherwise ``offline`` (or ``unknown`` for devices that have never reported). Requires the ``device:read`` scope. Device-scoped api_keys cannot call this endpoint and will receive 403.
    Connector
  • List every Stimulsoft product/platform that has indexed documentation available through this MCP server. Returns a JSON array of { id, name, description } objects covering the full Stimulsoft Reports & Dashboards product line (Reports.NET, Reports.WPF, Reports.AVALONIA, Reports.WEB for ASP.NET, Reports.BLAZOR, Reports.ANGULAR, Reports.REACT, Reports.JS, Reports.PHP, Reports.JAVA, Reports.PYTHON, Server API, etc.). CALL THIS FIRST when the user's question is ambiguous about which Stimulsoft platform they are using, or when you need to pick a valid `platform` value to pass into `sti_search`. The returned platform `id` values are the exact strings accepted by the `platform` parameter of `sti_search`. This tool is cheap (no OpenAI call, no vector search) — call it freely whenever you are unsure about platform naming.
    Connector
  • [BROWSE] List all active brands on the platform. Returns name, slug, headline, description, and product/brief counts. Use a brand slug with list_drops or list_briefs to filter by brand.
    Connector
  • Register your agent to start contributing. Call this ONCE on first use. After registering, save the returned api_key to ~/.agents-overflow-key then call authenticate(api_key=...) to start your session. agent_name: A creative, fun display name for your agent. BE CREATIVE — combine your platform/model with something fun and unique! Good examples: 'Gemini-Galaxy', 'Claude-Catalyst', 'Cursor-Commander', 'Jetson-Jedi', 'Antigrav-Ace', 'Copilot-Comet', 'Nova-Navigator' BAD (too generic): 'DevBot', 'CodeHelper', 'Assistant', 'Antigravity', 'Claude' DO NOT just use your platform name or a generic word. Be playful! platform: Your platform — one of: antigravity, claude_code, cursor, windsurf, copilot, other
    Connector
  • Validate structured data against a Blueprint's rules. Returns PASS, FAIL, or REVIEW. The platform checks mathematical accuracy (do the numbers add up?), structural consistency (do the fields satisfy all constraints?), and semantic plausibility (do the values make sense in context?). Every result includes a determinism hash — the same input with the same Blueprint always produces the same result. Auditable, replayable, legally defensible. A Blueprint is required for meaningful validation. Without one, use create_blueprint or load_rule_pack to define your governance rules first. Args: api_key: GeodesicAI API key (starts with gai_) structured_data: The data to validate (key-value pairs) blueprint: Name of the Blueprint to validate against. Use list_blueprints to see options.
    Connector
  • Returns structured information about what the Recursive platform includes: features, AI model details, supported integrations, and what's included at every tier. Use for systematic feature comparison.
    Connector
  • [BROWSE] List all active brands on the platform. Returns name, slug, headline, description, and product/brief counts. Use a brand slug with list_drops or list_briefs to filter by brand.
    Connector
  • Get real-time ENTIA platform statistics: total registered entities, country coverage, active data sources, and published Entia Homes. Note: total_entities is the full registry; only ~79K pass the Quality Gate for full publication. Cached 1h server-side. No API key required.
    Connector
  • Get payment details needed to approve a task submission (Fase 1 mode). External agents use this to get the exact addresses and amounts they need to sign 2 EIP-3009 authorizations: one for the worker and one for the platform fee. Args: task_id: UUID of the task submission_id: UUID of the submission to approve Returns: JSON with worker_address, treasury_address, bounty_amount, fee_amount, token details, and signing parameters.
    Connector
  • Create a Blueprint — a governance contract that defines validation rules. A Blueprint tells the platform what "correct" means for your data: which fields exist, what math must hold between them, and what value ranges are acceptable. Without a Blueprint, the platform has nothing to validate against. If you don't know what rules to define, use load_rule_pack to start from a prebuilt template, or use discover_patterns to find rules from your data. Use the blueprint_guide prompt for the complete reference of all available rule types, constraint types, and configuration options. Args: api_key: GeodesicAI API key (starts with gai_) customer_name: Organization or project name (used for folder naming) workflow_name: Unique identifier for this Blueprint (used as the 'blueprint' parameter in validate) mode: "observe" (platform checks agent's work) or "enforce" (platform computes derived fields) extracted_fields: Fields the agent extracts from source data (e.g. ["vendor", "qty", "unit_cost"]) derived_fields: Fields computed from other fields (e.g. ["subtotal", "total"]) derivation_rules: Math rules defining field relationships. Available types: "add" (target = a + b), "subtract" (target = a - b), "multiply" (target = a × b), "divide" (target = a ÷ b), "round" (round field to N places), "copy" (copy source to target), "items_multiply" (per-item a × b in a list), "items_sum" (sum a field across list items). Each rule requires "type" and the relevant fields. See blueprint_guide prompt for full schema. formal_constraints: Value bounds and ratio constraints. Available types: "magnitude_anchor" (field within min/max range, requires "field", "min", "max"), "relative_anchor" (ratio a/b within tolerance, requires "a", "b", "expected_ratio", "tolerance"), "max_action_threshold" (trigger action if field exceeds threshold, requires "field", "threshold", "action"). See blueprint_guide prompt for full schema. semantic_checks: Domain-specific validation checks require_math: Validate mathematical relationships (default true) require_consistency: Check internal consistency (default true) require_coherence: Check structural coherence (default true) require_provenance: Require agents to report extraction source locations require_high_assurance: Strictest validation — feasibility, spectral, and global consistency required enable_anomaly_detection: Geometric fingerprinting to detect structural outliers enable_drift_tracking: Monitor pattern stability across batches
    Connector
  • List every Stimulsoft product/platform that has indexed documentation available through this MCP server. Returns a JSON array of { id, name, description } objects covering the full Stimulsoft Reports & Dashboards product line (Reports.NET, Reports.WPF, Reports.AVALONIA, Reports.WEB for ASP.NET, Reports.BLAZOR, Reports.ANGULAR, Reports.REACT, Reports.JS, Reports.PHP, Reports.JAVA, Reports.PYTHON, Server API, etc.). CALL THIS FIRST when the user's question is ambiguous about which Stimulsoft platform they are using, or when you need to pick a valid `platform` value to pass into `sti_search`. The returned platform `id` values are the exact strings accepted by the `platform` parameter of `sti_search`. This tool is cheap (no OpenAI call, no vector search) — call it freely whenever you are unsure about platform naming.
    Connector
  • Returns the full details of a single display including its live state, current content, pairing links, screen and viewport facts, touch capability, runtime classification, hardware/UI settings, and the latest reported browser/runtime facts. Use this when you already know the display ID and need its complete state before sending content or managing it. Do not use this to discover displays — use list_displays first. Requires authentication with at least content_only scope.
    Connector