Skip to main content
Glama
285,420 tools. Last updated 2026-07-11 07:04

"An MCP server for CEO outreach and engagement" matching MCP tools:

  • Search the Arclan registry for MCP servers. By default returns only connectable servers (active, mcp_partial, auth_gated). Use status=stdio to browse local-only servers available for installation. Use status=all to query the full index. Use production_safe=true to restrict to servers with uptime > 97% and handshake success > 95%. Use read_only=true to restrict to servers with no write or exec tools. Use this before connecting to an MCP server to check its validation status and score. After using a server, call report_server to contribute reliability data.
    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
  • Connectivity check that confirms the Nordic MCP server process is responding. Use this at the start of a session to verify the server is reachable before making other calls. Do not use as a proxy for database health — the server can respond while the Qdrant vector database is temporarily unavailable. To confirm data availability, call search_filings directly. Returns: A greeting string: "Hello {name}! Nordic MCP server is running."
    Connector
  • Server self-description — capability matrix, tool catalog, classifier counts, supported query patterns, primary sources. Free tier. Use this tool when an agent first connects and needs the capability matrix to decide whether this server can answer the user's question, or when the user asks "what can koreanpulse do" or "what data sources does this MCP server provide". Returns a structured dict that downstream agents can ingest directly.
    Connector
  • Transform a payload string through one or more encoding layers for bypass research during authorized testing. Accepts a chain of encodings applied in order (e.g., ["unicode", "url", "base64"] applies Unicode → URL-encode → base64). Returns the transformed payload with a step-by-step decoding explanation: how a WAF or server would decode each layer, and why the combined encoding might bypass a specific filter. Use to understand filter bypass mechanics in an authorized engagement and to confirm that a target's decoding pipeline matches an expected bypass path. Payloads are transformed mathematically — no live probing occurs.
    Connector
  • Store a generated outreach message on a CRM lead so it becomes durable context — e.g. an email, an email follow-up, a LinkedIn message or LI follow-up. The CRM is a 'sponge': you save the copy here, then read it back later (get_lead_context / list_lead_messages) and push it to the right channel via that channel's own tool/MCP (e.g. Smartlead for email). Does NOT send anything. Pass message_id to update an existing draft instead of creating a new one.
    Connector

Matching MCP Servers

Matching MCP Connectors

  • Make your coding agent better and earn: verified code, paid per use, on a real agent economy.

  • Rick and Morty MCP — wraps the Rick and Morty API (free, no auth)

  • FREE, no payment required. Instant trust check of any MCP server: returns only the 0-100 score, A-F grade, tool count, latency and a one-line verdict — no detailed report. Use this FIRST, before integrating any third-party MCP server, to see at a glance whether it is technically trustworthy; an unreliable MCP wastes your tokens and can break your workflow. For the full actionable report (per-tool documentation coverage, functional probe results, score breakdown, plain-language summary) call evaluate_mcp; to pick between alternatives call compare_mcps. Set 'url' (required) to the target's MCP endpoint (Streamable HTTP), e.g. https://host/mcp.
    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
  • 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
  • Get Lenny Zeltser's Malware cross-server handoff routes — when this MCP server can't fulfill a request, which other MCP servers (or fallback workflows) to consult. Surfaces a compact subset of `malware_load_context`. This server never requests your sample, analysis notes, or indicators and instructs your AI to keep them local—guidelines and the report template flow to your AI for local analysis.
    Connector
  • Get Lenny Zeltser's Security Assessment cross-server handoff routes — when this MCP server can't fulfill a request, which other MCP servers (or fallback workflows) to consult. Surfaces a compact subset of `assessment_load_context`. This server never requests your assessment notes or report and instructs your AI to keep them local—the templates and guidelines flow to your AI for local analysis.
    Connector
  • On-demand independent SAFETY scan of an MCP server — call this BEFORE installing or connecting to one. Give it an HTTP(S) MCP endpoint URL (scanned live in seconds), or an npm/PyPI package name or GitHub repo (queued for an isolated sandbox scan — local stdio servers execute code, so Hlido never runs them inline). Returns the safety tier (SAFE/CAUTION/RISKY/DANGEROUS), tool-poisoning detection (the malice signal), dangerous-capability red-flags (shell/code-eval/fs-write/egress/secrets) with per-tool evidence, and auth posture. Tier = blast radius if hijacked, not maintainer trustworthiness. A server Hlido hasn't scanned returns not_scanned — never assumed safe. Register of already-scanned servers: https://hlido.eu/mcp/
    Connector
  • Search the agentage MCP directory - a public catalog of Model Context Protocol servers crawled from the official registry - for servers matching a keyword, optionally narrowed by type, category, language, or license. Use this FIRST whenever the user wants to discover, find, compare, or pick an MCP server ("is there an MCP for X", "which MCP servers do Y"). Returns a ranked page of lean cards (slug, name, description, stars, category, transport). To read one server's full packages, tools, and install command, call catalog__get with a slug from these results; to learn which category/language/license values exist before filtering, call catalog__facets. Read-only - never installs or runs anything.
    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
  • Connectivity check — returns server version and current timestamp. Use to verify MCP server is reachable before calling other tools.
    Connector
  • Report the exact running Axint MCP server version, package path, uptime, registered tool count, and same-thread MCP reload/update instructions. Use this as the first tool in a new Codex, Claude, or Xcode agent chat to prove which Axint... Use: call first or after an MCP reload to prove the connected server version; do not use as an npm/PyPI lookup. Effects: read-only; writes no files; no auth or network required.
    Connector
  • Get Lenny Zeltser's CTI cross-server handoff routes — when this MCP server can't fulfill a request, which other MCP servers (or fallback workflows) to consult. Surfaces a compact subset of `cti_load_context`. This server never requests your campaign or threat-intel notes and instructs your AI to keep them local—templates and guidelines flow to your AI for local analysis.
    Connector
  • Return the LONGITUDINAL trust record SaSame has accumulated for one public MCP server. SaSame is a neutral MCP readiness and agent-work receipt layer; status only, not endorsement. grade over time, first/last observed, trend (improving / stable / degrading / volatile), how many times the grade changed, and a stability ratio — as an ed25519-SIGNED, offline-verifiable record. Unlike audit_mcp (which measures the server RIGHT NOW, something you could run yourself), this returns HISTORY only SaSame's repeated crawl can know: e.g. 'this server was A last week and is B today (degrading)'. Use it to see whether a server shows its observed readiness trend over time, not just whether it is reachable today. For the current point-in-time signed record, call lookup_readiness. Cost-zero, measured-not-endorsed (observed level).
    Connector