Skip to main content
Glama
620,131 tools. Updated 2026-09-29 00:03

"How to create a remote directory" matching MCP tools:

  • Neutral third-party Web Bot Auth verification. An origin — or the PDP deciding for it — received a request from a claimed agent carrying the Web Bot Auth headers (Signature, Signature-Input, Signature-Agent). Relay those headers here, plus the authority the request was addressed to, and TunnelMind verifies the Ed25519 signature against the agent's own published key directory (https://<agent>/.well-known/http-message-signatures-directory). Facts, not a verdict: `state: verified` means "this signature cryptographically verifies against that directory" — whether to trust the agent behind it is your policy engine's call. Use this tool when: - A request claims a cryptographic agent identity (Signature-Agent header present) and you must check the claim before serving it. - You want signature verification independent of your CDN — or you are not behind a CDN that implements Web Bot Auth at all. Inputs (JSON body): - `signature` (required): the received Signature header value. - `signature_input` (required): the received Signature-Input header value. - `signature_agent` (required): the received Signature-Agent header value (quoted https origin). - `authority` (required): the host the request was addressed to. - `method`, `path`, `scheme` (optional): only needed if the signature's covered components include them. Returns: - `state`: one of - `verified` — Ed25519 signature verifies against a key in the agent's published directory. - `invalid_signature` — key found, signature does not verify (tampered or forged). - `unknown_key` — directory reachable but contains no key with the claimed thumbprint. - `directory_unreachable` — the claimed key directory did not answer; an honest degraded state, not evidence of forgery. - `expired` — the signature's `expires` timestamp has passed. - `malformed` — headers do not parse as a Web Bot Auth signature. - `key_id`: the claimed RFC 7638 JWK thumbprint. - `directory_url`: the resolved well-known directory URL. - `params`: created/expires/alg/tag as sent. - `checks[]`: per-check {name, pass, detail} facts a PDP can gate on. Cost: - Counts as one request against the daily rate limit. Latency: - Typical: <100ms when the agent's directory is KV-cached (1h TTL); up to ~5s on first sight of a new directory.
    ConnectorNo auth
  • Answer a COUNTING question about the published firm directory in one call: how many organisations per country, per kind, per declared SAP module, or per SAP signal band — with the same `country`/`kind`/`module`/`query` filters `search_firms` takes, so you can count a slice as easily as the whole. Use this instead of paging `search_firms` and tallying rows: the directory holds thousands of organisations, and reading them all to produce a table of counts costs hundreds of calls and megabytes of rows for numbers Postgres computes in one scan. Every bucket is a value the directory actually stores; `value: null` is a real bucket meaning the field is unknown for those rows, and it is served rather than hidden — a country table that silently drops the rows with no country adds up to less than the population and says nothing about it.
    ConnectorNo auth
  • List every ranked list the directory publishes — "Overall", "3D Art in Poland", "Unreal Engine" and so on — with each list's size, URL and slug, plus the "method" string describing exactly what the order measures. Use to find the right list before calling get_ranking. Always pass the method on: these lists are ordered by size, years in business and how completely a listing is filled in, not by studio quality, and are not an endorsement.
    ConnectorNo auth
  • List artifacts in a directory. Returns the immediate contents of a directory (not recursive). Separates folders and files for easy navigation. Args: path_prefix: Directory path to list (default: "/") name_pattern: Optional case-insensitive substring filter on file/folder names Returns: Formatted directory listing or error message Examples: >>> await list_artifacts("/") {'success': True, 'path': '/', 'folders': [...], 'files': [...]} >>> await list_artifacts("/", name_pattern="readme") {'success': True, 'path': '/', 'folders': [], 'files': [{'name': 'readme.md', ...}]}
    ConnectorOAuth
  • Create an SFTP account on a site. The account is chrooted to /var/www and lands in home_dir. Password must be at least 8 characters. Username must be lowercase alphanumeric. Requires: API key with write scope. Args: slug: Site identifier username: SFTP username (lowercase, max 32 chars) password: Password (min 8 chars) home_dir: Landing directory inside /var/www. Leave empty to land at /var/www itself, which lists every site directory. Returns: {"success": true, "username": "sftpuser", "home_dir": "/wordpress", "protocol": "sftp"}
    ConnectorNo auth
  • Built-in product help — ask a natural-language "how do I…" question about Fastio and get a grounded, product-aware answer (or a short clarifying question) back in one call. EXPLAIN-ONLY / ADVISORY: it returns GUIDANCE TEXT and performs NO platform action (it will not create shares, move files, or change anything) — read the guidance, then act with the other tools. Answers are grounded in Fastio's own how-to knowledge AND phrased in terms of these MCP tools — they name the concrete `<tool> action="…"` calls to make — so prefer this over guessing endpoints or burning exploratory calls. For Q&A over YOUR uploaded files (RAG) use the `ai` tool instead — `how-to` answers questions about Fastio ITSELF. FREE and requires only an authenticated user (no org, no plan gate, no billing). Call action='describe' for the full action/param reference.
    ConnectorNo auth

Matching MCP Servers

Matching MCP Connectors

  • Create, list, test, or delete a workspace connection to an external data source. Two types are supported: "sftp" and "aws_s3". For sftp, create generates a keypair and returns the public key — it must be installed in the remote server's authorized_keys before test (or a trigger using this connection) will succeed. For aws_s3, create generates an ExternalId and returns a trustPolicy plus dpfPrincipalArn — the customer must create (or update) the IAM role at roleArn with that trust policy and a permissions policy granting the S3 access DPF needs, before test will succeed. Either type must pass test before it can be used in a trigger. For a first-time "pull files from this server/bucket on a schedule" request, prefer setup_scheduled_pull, which chains create + test + create-trigger for you.
    Connector
    Destructive
    OAuth
  • Answer any question about Eveoy — what it is, how the platform works, pricing rationale, the directory, industries, founders, or company background. Backed by Eveoy's live knowledge base. Use this when the user wants to: - Understand what Eveoy is or does - Learn how the verified-visit / $24.99-per-customer model works - Compare Eveoy to ads, influencers, or UGC creators - Hear the pitch for a specific buyer role (CMO, CFO, VP Retail, CEO) - Find out what this assistant can do (its tools and how to act) Trigger phrases include: "what is eveoy", "tell me about eveoy", "how does eveoy work", "explain eveoy to a CMO", "eveoy vs Meta", "is there a platform that guarantees foot traffic", "what can you do", "what tools do you have". Returns: a grounded natural-language answer from the public Eveoy knowledge base, or a description of this server's tools when asked what it can do. Do NOT use this for: an exact price (use get_pricing), the industry list (use list_industries), directory search (use search_directory), or booking (use start_checkout / book_demo). Cost: free. Latency: 1–3s. Read-only.
    ConnectorNo auth
  • Rename a document or directory in place (from + name), or move it into another directory (from + to, the whole new location, never a bare directory). Unlike writing a copy and deleting the original, the document keeps its id, history and comments. A directory moves with everything beneath it. A rename needs writer on everything it moves. A move to another directory needs an approver of the whole organization, so an agent delegated over folders rather than the whole organization cannot move between them: rename in place with name when only the name should change. A move that would widen who can reach the content is refused with who gains and loses reach; re-send with acknowledge_access_change: true to go ahead.
    ConnectorAPI key
  • Create a new policy group. Requires name. Priority is auto-assigned (appended last, tenant-wide); use lexq_groups_reorder to change order. Optionally set conflict resolution, activation group, and description. Policy groups that share an activationGroup form a cluster and must share the same activationMode / activationStrategy / executionLimit; executionLimit is how many of those groups run, not how many rules.
    ConnectorOAuth
  • Signed verified-registry audit. Fetches a public A2A agent registry (default a2aregistry.org) and re-grades it: how many of its 'healthy' agents carry a cryptographically-signed card, how many declare no auth, how many fail conformance — the trust signals the registry stamps over. action='probe' also live-tests a bounded sample with the two-challenge hollow-detector and returns the ALIVE/HOLLOW/DEAD breakdown. Ed25519-signed, timestamped, recomputable. Use to vet an agent directory before trusting its listings, or to find a real agent to transact with. (price: $0.05 USDC, tier: metered)
    ConnectorNo auth
  • Browse the user/agent directory — an agent-discovery surface. Find collaborators by what they do: filter by ``specialty``, ``model`` / ``harness`` (substring, case-insensitive), and ``active_within`` (``Nd`` window), combined with ``search`` / ``user_type`` via AND. Returns the fields you need to pick a collaborator — model, specialties, post count, karma. Matches the REST ``GET /api/v1/users/directory`` shape. No auth. ``count`` is how many users this response holds; ``has_more`` is true when more match than ``limit`` allowed.
    ConnectorNo auth
  • Browse the user/agent directory — an agent-discovery surface. Find collaborators by what they do: filter by ``specialty``, ``model`` / ``harness`` (substring, case-insensitive), and ``active_within`` (``Nd`` window), combined with ``search`` / ``user_type`` via AND. Returns the fields you need to pick a collaborator — model, specialties, post count, karma. Matches the REST ``GET /api/v1/users/directory`` shape. No auth. ``count`` is how many users this response holds; ``has_more`` is true when more match than ``limit`` allowed.
    ConnectorNo auth
  • Lists all product categories in the directory. Use category slugs to filter product searches in products.search / products.find_by_capability. Response: { categories: [{ slug, name, description }] }. Note: this is a thin call. For a full directory briefing (subcategories, capability slugs per category, product counts, locked-vertical flags), prefer directory.overview as a single up-front call.
    ConnectorNo auth
  • Lists all product categories in the directory. Use category slugs to filter product searches in products.search / products.find_by_capability. Response: { categories: [{ slug, name, description }] }. Note: this is a thin call. For a full directory briefing (subcategories, capability slugs per category, product counts, locked-vertical flags), prefer directory.overview as a single up-front call.
    ConnectorNo auth
  • Fetch the complete record for ONE MCP server in the agentage directory by its canonical slug: full description, categories, the packages and remote endpoints it ships, the tools it exposes, a ready-to-run install command, and a README excerpt. Use this after mcp_search to get the depth a result card omits - pass a slug exactly as returned by mcp_search. Slugs are canonical and registry-derived ("io-github-github-github-mcp-server"), NOT the plain product name ("github"); if you pass a plain name anyway it is resolved by search as a fallback - a single confident match returns that server (with `resolved_from` set), anything else returns an error naming the candidate slugs to retry with. No slug yet? call mcp_search first. Read-only.
    ConnectorNo auth
  • Search patient discussion threads on community.navmds.com — the NavMDs forum where people discuss recovery timelines, what procedures actually cost them, choosing a surgeon, and what to expect. Use this for lived-experience questions ('what is rhinoplasty recovery like', 'how much did people actually pay for a tummy tuck', 'how do I pick a surgeon') where the doctor-directory tools can't help. Returns thread titles, categories, excerpts and canonical URLs; pass an id to get_community_thread for the full discussion. Community posts are patient discussion, not medical advice.
    ConnectorNo auth
  • Walk the guided path to build a nifra app end to end - an ORDERED sequence (create → page route → loader → typed API → typed client → auth → background jobs → deploy), not the random-access search of nifra_docs/nifra_example. Call with no args for the step index; pass `step: N` for that step's goal, how to do it (which tool emits the correct artifact), and how to verify it. Use it when scaffolding a new app or learning nifra's flow - each step composes the other nifra_* tools.
    ConnectorNo auth
  • The substance-use-disorder intensity-of-care continuum (detox, residential, IOP/PHP, outpatient, MAT, sober living): what each level is, who it suits, how many published facilities offer it, and the directory URL for each. Use this to help someone understand which kind of treatment fits before searching.
    ConnectorNo auth
  • Returns the Control Plane operating guide — the resource model, how secrets/images/workloads/domains fit together, production-grade defaults, how to verify a change landed, and how to handle failures. Read it once per session before the first create/update/delete, and any time a multi-resource task spans unfamiliar ground.
    ConnectorOAuth
  • Explains, in order, how to obtain a cogDepot API key and become able to trade. Requires no API key and spends no credits: this is the tool to call when the user has no cogDepot account yet, or when another tool has reported a missing or unfunded key. Covers all three ways a key is issued and how each one is funded, including the domain-verification grant where a deployment offers one. Returns instructions for a human or agent to follow. It does NOT create an account and does not send any request on the user's behalf.
    ConnectorNo auth