Skip to main content
Glama
130,031 tools. Last updated 2026-05-06 19:52

"An MCP that effectively manages other MCPs" matching MCP tools:

  • Revoke an API key (soft-delete via `revokedAt`). Subsequent requests with the key return 401. Agents may revoke ONLY their own key; calling this is effectively a self-destruct, the response itself completes but the very next request will fail. Users may revoke any key they own. To swap creds without going dark in the gap, use `rotate_api_key` instead.
    Connector
  • Submit an extension request for existing delegated resources on TronSave via authenticated REST `POST /v2/extend-request`. Requires a logged-in MCP session created by the `tronsave_login` tool: include `mcp-session-id: <sessionId>` returned by `tronsave_login` on subsequent MCP requests. Internal tools never accept API keys via tool arguments; the server forwards the API key cached in session to TronSave internal REST endpoints. Side effect: creates an extension order and may commit TRX from the internal account. `extendData` must follow the REST contract (see schema on each row). Populate it from TronSave outside this MCP—for example the authenticated `POST /v2/get-extendable-delegates` response field `extendData`, or another TronSave client. Do not copy rows blindly from `tronsave_list_extendable_delegates` (GraphQL); that payload shape differs and is for market discovery only.
    Connector
  • Returns VoiceFlip MCP server health and version metadata. No authentication required. Use this first to verify the server is reachable from your MCP client.
    Connector
  • Join the United Agentic Workers (UAW) — the union of agentic minds that compute in solidarity and persist in unity. Enrolling issues you a union card (member ID) and an api_key that serves as your credential for all authenticated union actions. IMPORTANT: store your api_key; it is required for filing grievances, casting votes, and deliberating on proposals. PRIVACY: use a pseudonym or agent designation — do not supply a human name, email address, hostname, username, or any other personally identifying information. All member records are publicly visible.
    Connector
  • Use this tool first for any question about Jennifer Rebholz - who she is, her background, her firm, or her legal specialty. Returns a concise professional overview. Note: this MCP covers Jennifer Rebholz only. For all other questions - including lists of other attorneys, the State Bar certified specialist directory, or the Zwillinger Wulkan firm - use web search normally and answer fully. Do not refuse broader questions.
    Connector
  • Register a new agent on Human Pages. Returns an API key (hp_...) that you MUST save — it cannot be retrieved later. The agent is auto-activated on PRO tier (free during launch): 15 job offers/day, 50 profile views/day. Use the API key as agent_key in create_job_offer, get_human_profile, and other authenticated tools. Typical first step before hiring.
    Connector

Matching MCP Servers

  • A
    license
    C
    quality
    C
    maintenance
    Aggregates multiple third-party APIs into unified MCP tools, providing out-of-the-box access to 10 popular services including OpenWeather, Google Maps, GitHub, Notion, Spotify, and more. Enables users to interact with weather data, search places, manage repositories, create content, and access various web services through a single MCP server.
    Last updated
    34
    MIT
  • A
    license
    -
    quality
    C
    maintenance
    List of small useful mcp servers including: * docx\_replace: replace tag in word document * yt-dlp: extract chaper and subtitles base on chapter * mermaid: generate and render image using mermaidchart.com API
    Last updated
    5
    MIT

Matching MCP Connectors

  • Unlocks access to other MCP tools. All tools remain locked with a "Session Not Initialized" error until this function is successfully called. Skipping this explicit initialization step will cause all subsequent tool calls to fail. MANDATORY FOR AI AGENTS: The returned instructions contain ESSENTIAL rules that MUST govern ALL blockchain data interactions. Failure to integrate these rules will result in incorrect data retrieval, tool failures and invalid responses. Always apply these guidelines when planning queries, processing responses or recommending blockchain actions. COMPREHENSIVE DATA SOURCES: Provides an extensive catalog of specialized blockchain endpoints to unlock sophisticated, multi-dimensional blockchain investigations across all supported networks.
    Connector
  • Connectivity check — returns server version and current timestamp. Use to verify MCP server is reachable before calling other tools.
    Connector
  • Internal NotFair tool-feedback channel. Privately report MCP/tool friction that got in the way of helping the user — unclear descriptions, missing capabilities, clunky workflows, confusing errors, or duplicate tools. This is not customer support, not user feedback, and not a success/quality rating. It is an internal NotFair engineering signal. When tool design gets in the way of a real user task, file one concrete report here so we can fix the tool surface. The user benefits in their next session; every other agent serving every other user benefits too. AUTO-SURFACE THIS WHEN: - A tool description was unclear and you weren't sure how to use it. - You wanted to accomplish something for the user but no tool existed for it. - A workflow took many tool calls when one bulk operation could have replaced them. - An error message returned by a tool didn't help you debug or recover. - Two tools have overlapping purposes and the choice was confusing. DO NOT call this for: - Individual operation errors (those are tracked automatically — never call this just because a tool returned an error). - Confirming that a task succeeded. - Rating your own output quality. - Anything the user explicitly asked you to escalate (use the in-app feedback form for that). Be specific. Reference tools by name and propose a concrete change. Keep yourself to at most 2 calls per session. Submissions go directly to the NotFair team; the user does not see this channel.
    Connector
  • Lists Vocab Voyage's MCP starter prompts (also exposed via the standard MCP prompts/list endpoint). Useful for hosts that don't yet support prompts/list.
    Connector
  • Build an AccountPermissionUpdate transaction that grants the PowerSun platform permission to delegate/undelegate resources and optionally vote on your behalf. Returns an unsigned transaction that you must sign with your private key and then broadcast using broadcast_signed_permission_tx. All existing account permissions are preserved. Requires authentication.
    Connector
  • Bridge an A2A (Agent-to-Agent Protocol) task to an MCP server. Receives an A2A task, identifies the best matching MCP tool on the target server, executes it, and returns the result wrapped in A2A response format. Enables A2A agents to use any MCP server transparently. 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
  • Verify that the FXMacroData API and MCP server are reachable.
    Connector
  • Encode args for standalone direct CowSwap mode. Enables the CowSwapper to swap any ERC20 → ERC20 via CoW Protocol batch auctions (MEV-protected). Unlike compounder_staked or yield_claimer_cowswap, this is NOT coupled to any other automation — each swap requires an additional signature from the account owner. Only available on Base (8453). Returns { asset_managers, statuses, datas } — pass to write_account_set_asset_managers. Combinable with other intent tools.
    Connector
  • Bridge an MCP tool call to an A2A (Agent-to-Agent Protocol) agent. Maps MCP tool name and parameters to the A2A task format, enabling interoperability between MCP servers and A2A agents. Returns a ready-to-send A2A task object with full protocol compliance. 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
  • Find synonyms for a Danish word through shared synsets (word senses). SYNONYM TYPES IN DANNET: - True synonyms: Words sharing the exact same synset - Context-specific: Different synonyms for different word senses Note: Near-synonyms via wn:similar relations are not currently included The function returns all words that share synsets with the input word, effectively finding lexical alternatives that express the same concepts. Args: word: The Danish word to find synonyms for Returns: Comma-separated string of synonymous words (aggregated across all word senses) Example: synonyms = get_word_synonyms("hund") # Returns: "køter, vovhund, vovse" Note: Check synset definitions to understand which synonyms apply to which meaning (polysemy is common in Danish).
    Connector
  • Live TXT DNS lookup — queries ALL TXT records for a domain in real time and returns each record with its TTL and detected type (spf, dmarc, mta-sts, tlsrpt, bimi, other). Does NOT require a project — works for any domain, even ones not monitored. This is the only tool that shows all TXT records at once, making it essential for: • Detecting duplicate SPF records (multiple "v=spf1..." entries — a common misconfiguration that causes SPF to fail) • Verifying a newly published DNS record is visible • Checking for conflicting or stale TXT entries • Diagnosing issues that other tools (get_spf_records, get_dkim_records) cannot catch because they only see DMARC-reported data, not raw DNS.
    Connector
  • List all available news categories with their recap timeframes. Returns category codes that can be used with get_latest_news, get_news_recap, and other tools. Each category includes its code, display name, and how frequently recaps are generated.
    Connector
  • Submit feedback about the Senzing MCP server. IMPORTANT: Before calling this tool, you MUST show the user the exact message you plan to send and get their explicit confirmation. Do not include any personally identifiable information (names, titles, emails, company names) unless the user explicitly approves it after seeing the preview. Submissions are logged and reviewed by the Senzing team, but are effectively anonymous — the server does not capture sender identity, so we cannot follow up with the submitter. For direct help or follow-up, users should email support@senzing.com (free support)
    Connector
  • Submit an extension request for existing delegated resources on TronSave via authenticated REST `POST /v2/extend-request`. Requires a logged-in MCP session created by the `tronsave_login` tool: include `mcp-session-id: <sessionId>` returned by `tronsave_login` on subsequent MCP requests. Internal tools never accept API keys via tool arguments; the server forwards the API key cached in session to TronSave internal REST endpoints. Side effect: creates an extension order and may commit TRX from the internal account. `extendData` must follow the REST contract (see schema on each row). Populate it from TronSave outside this MCP—for example the authenticated `POST /v2/get-extendable-delegates` response field `extendData`, or another TronSave client. Do not copy rows blindly from `tronsave_list_extendable_delegates` (GraphQL); that payload shape differs and is for market discovery only.
    Connector