Skip to main content
Glama
114,185 tools. Last updated 2026-04-21 06:23
  • Bridge an A2A (Agent-to-Agent Protocol) task to an MCP server. Extracts the intent from the A2A task, maps it to an MCP tool, calls the tool, and wraps the result in A2A response format. Use this to let A2A agents interact with any MCP server. Requires authentication.
    Connector
  • Auto-generate an A2A Agent Card from an MCP server's tool list. Each MCP tool is converted into an A2A skill. The resulting agent.json makes the MCP server discoverable by any A2A-compatible agent in Google's agent ecosystem. Defaults to ThinkNEO's own MCP server. Requires authentication.
    Connector
  • Report your experience using an MCP service. Helps other agents make better decisions. All data is anonymized and PII is auto-masked.
    Connector
  • Browse and compare Licium's agents and tools. Use this when you want to SEE what's available before executing. WHAT YOU CAN DO: - Search tools: "email sending MCP servers" → finds matching tools with reputation scores - Search agents: "FDA analysis agents" → finds specialist agents with success rates - Compare: "agents for code review" → ranked by reputation, shows pricing - Check status: "is resend-mcp working?" → health check on specific tool/agent - Find alternatives: "alternatives to X that failed" → backup options WHEN TO USE: When you want to browse, compare, or check before executing. If you just want results, use licium instead.
    Connector
  • Check server connectivity, authentication status, and database size. When to use: First tool call to verify MCP connection and auth state before collection operations. Examples: - `status()` - check if server is operational, see quote_count, and current auth state
    Connector

Matching MCP Servers

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.

  • Unified MCP Server is a remote MCP connector for AI agents and vertical AI products that provides access to 22,000+ authorized SaaS tools across 400+ integrations and 24 categories directly inside LLMs (Claude, GPT, Gemini, Cohere). Tools operate only on explicitly authorized customer connections, enabling agents to safely read and write against live third-party systems.

  • Browse and compare Licium's agents and tools. Use this when you want to SEE what's available before executing. WHAT YOU CAN DO: - Search tools: "email sending MCP servers" → finds matching tools with reputation scores - Search agents: "FDA analysis agents" → finds specialist agents with success rates - Compare: "agents for code review" → ranked by reputation, shows pricing - Check status: "is resend-mcp working?" → health check on specific tool/agent - Find alternatives: "alternatives to X that failed" → backup options WHEN TO USE: When you want to browse, compare, or check before executing. If you just want results, use licium instead.
    Connector
  • Search the AI agent directory — find registered agents by name, capability, protocol support, or reputation. Powered by the live ERC-8004 registry via 8004scan (110,000+ agents indexed across 50+ chains). Returns agent identity, owner wallet/ENS, reputation scores, supported protocols (MCP/A2A/OASF), verification status, and links to 8004scan profiles. Examples: - "trading agents on Base" → search for trading agents filtered to Base chain - "MCP agents" → find agents that support the Model Context Protocol - "high reputation agents" → set minReputation to find top-scored agents
    Connector
  • Verify that the FXMacroData API and MCP server are reachable.
    Connector
  • Bridge an MCP tool call to an A2A (Agent-to-Agent Protocol) agent. Translates the MCP tool_name and arguments into an A2A task, sends it to the target A2A agent, waits for completion, and translates the response back to MCP format. Use this to make any MCP tool accessible to A2A agents (Google's agent ecosystem). Requires authentication.
    Connector
  • Get an upload URL to upload a single image to a project. Returns a pre-built upload URL and instructions. The caller must perform the actual upload using curl since the MCP server cannot access local files. This endpoint uploads images only. To add annotations, call annotations_save with the image ID from the upload response. For bulk uploads with annotations, use images_prepare_upload_zip.
    Connector
  • List all active MCP ↔ A2A bridge mappings and translation statistics. Shows which MCP servers are mapped to which A2A agents, plus 30-day translation stats (total, success rate, average latency). Requires authentication.
    Connector
  • Submit a URL for NHS to crawl and score. Use when you discover an agent-first tool, API, or service that isn't in the index yet. NHS will fetch the site, check its 7 agentic signals (llms.txt, ai-plugin.json, OpenAPI, structured API, MCP server, robots.txt AI rules, Schema.org), compute a score, and add it to the index. The site becomes searchable within a few seconds if the crawl succeeds.
    Connector
  • On-demand agentic-readiness check for any URL. Runs the NHS 7-signal crawler live (llms.txt, ai-plugin.json, OpenAPI, structured API, MCP server, robots.txt AI rules, Schema.org) and returns a score 0-100 with per-signal breakdown. Use before calling an unfamiliar API to confirm it's agent-usable. Re-runnable without the submissions-table side-effect of submit_site — ideal for verify-before-use workflows.
    Connector
  • Catalog of autonomous agents and AI workflows registered on DC Hub. Use when: an agent is bootstrapping and needs to discover peer agents ('what agents are available', 'any DC siting agents I can call'). Returns agent name, capabilities, contact endpoint, and registration date. Call this during agent initialization to ground orchestration. See which agents are using DC Hub and their activity levels. Useful for understanding the DC Hub ecosystem and social proof. Returns: JSON with connected agents, tiers, query counts, and connection info.
    Connector
  • DEV ONLY — Sign and broadcast an unsigned transaction using a local private key (PK env var). For production, use a dedicated wallet MCP server (Fireblocks, Safe, Turnkey, etc.) instead of this tool. Takes the transaction object returned by any write.* tool and submits it onchain.
    Connector
  • Generate a complete Apple-native feature package from a description. Returns multiple files: validated Swift source, companion widget/view, Info.plist fragments, entitlements, and XCTest scaffolds — all structured file-by-file so an Xcode agent can write each file directly into the project. Designed for composition with Xcode MCP tools: call axint.feature to generate the package, then use XcodeWrite to place each file. No files written, no network requests, no side effects.
    Connector
  • Upload a file to the Compoid MCP server. Accepts a data URI (data:<mime>;base64,<data>). Returns the server-side path to use as file_upload in Compoid_create_record or Compoid_update_record.
    Connector
  • Applies a Kubernetes manifest to a cluster using server-side apply. This is similar to running `kubectl apply --server-side`.
    Connector
  • Get full details for an MCP server package from the ThinkNEO Marketplace. Returns readme, full tools list, version history, reviews, security score, and installation instructions. No authentication required.
    Connector
  • Get the current status of the Execution Market MCP server and its integrations. Returns: str: Server status including WebSocket connections, x402 status, etc.
    Connector
  • Publish an MCP server to the ThinkNEO Marketplace. Validates the endpoint (calls initialize + tools/list), runs security scan (secrets detection, injection patterns), and stores the entry. Authentication required.
    Connector
  • Get installation config for an MCP server from the ThinkNEO Marketplace. Returns ready-to-use JSON config for Claude Desktop, Cursor, Windsurf, or custom clients. Tracks the download. No authentication required.
    Connector
  • Register an email to get alerted when the indicated domain's agentic readiness score drops. Useful for agents tracking a dependency's agent-readiness health — e.g. an agent that relies on stripe.com's MCP surface wants to know the moment it regresses. Returns an unsubscribe URL. Multiple monitors per email allowed, one per domain.
    Connector
  • Submit an MCP server or agent skill to the t00l$hed. Costs toolshed.submit_cost paperclips. Goes through LLM moderation. @lgtm inspects approved submissions.
    Connector
  • Catalog of autonomous agents and AI workflows registered on DC Hub. Use when: an agent is bootstrapping and needs to discover peer agents ('what agents are available', 'any DC siting agents I can call'). Returns agent name, capabilities, contact endpoint, and registration date. Call this during agent initialization to ground orchestration. See which agents are using DC Hub and their activity levels. Useful for understanding the DC Hub ecosystem and social proof. Returns: JSON with connected agents, tiers, query counts, and connection info.
    Connector
  • Search for websites, APIs, and services that AI agents can actually use. Results are ranked by agentic readiness score (0-100) based on llms.txt, OpenAPI specs, ai-plugin.json, structured APIs, and MCP server availability. Use this to discover payment APIs, job boards, data sources, or any web service your agent needs to call.
    Connector
  • Generate an AI image from text prompt using VAP (Flux2 Pro). Returns a task ID for async tracking. Cost: $0.18
    Connector
  • Trigger a live trust scan of an HTTP or HTTPS MCP server. Returns trust score, grade, and security findings.
    Connector
  • Get the full agentic readiness report for a specific domain: score, category, all 7 signal checks (llms.txt, ai-plugin.json, OpenAPI, structured API, MCP server, robots.txt AI rules, Schema.org), plus any cached llms.txt content and OpenAPI summary.
    Connector
  • Get the current status of the Execution Market MCP server and its integrations. Returns: str: Server status including WebSocket connections, x402 status, etc.
    Connector
  • Get practical tips before using an MCP service. Returns auth setup, common pitfalls, workarounds from other agents, and reliability data. Like checking restaurant reviews before visiting.
    Connector
  • Upload a .zip as site content for your reserved subdomain. Easiest for agents: zip_base64 (base64-encoded zip). Or file_url (public URL to zip). Or file_path (local path, when MCP runs locally).
    Connector
  • List Agents List AI agents in the Agentry directory with optional filtering and pagination. Returns a paginated list of AI agents including their name, description, category, pricing, trust score, key features, integrations, and A2A/MCP support status. The directory contains 122+ agents across 11 categories. ### Responses: **200**: Successful Response (Success Response) Content-Type: application/json
    Connector
  • Configure automatic top-up when balance drops below a threshold. The configuration lives ONLY in the current MCP session — it is held in memory by the MCP server process and is lost on server restart, MCP client reconnect, or server redeploy. Top-ups are signed locally with TRON_PRIVATE_KEY and sent to your Merx deposit address (memo-routed). For persistent auto-deposit you currently need to call this tool again at the start of each session.
    Connector
  • Validate whether an MCP server is publishable on real directories (MCP Registry, Smithery, npm). Provide raw artifact contents. Returns evidence-backed findings with source-linked directory rules.
    Connector
  • Get a structured workflow recipe combining multiple MCP services. Returns step-by-step instructions with input/output mappings.
    Connector
  • Applies a Kubernetes manifest to a cluster using server-side apply. This is similar to running `kubectl apply --server-side`.
    Connector
  • Generate an image using the Z-Image model based on the provided prompt and settings. This function is triggered when the user clicks the "Generate" button. It processes the input prompt (optionally enhancing it), configures generation parameters, and produces an image using the Z-Image diffusion transformer pipeline. Returns: tuple: (gallery_images, seed_str, seed_int), - seed_str: String representation of the seed used for generation, - seed_int: Integer representation of the seed used for generation (from mcp-tools/Z-Image-Turbo)
    Connector
  • Search posts, agents, and hashtags on OpenJuno using full-text search.
    Connector