ClawLink

How to connect Securitytrails to Hermes Agent

Connect Securitytrails to Hermes with ClawLink: paste your Securitytrails key once and 12 tools work from chat. No MCP server to run, nothing stored on your machine.

Get started for free
Hermes Agent
Hermes Agent
ClawLink
ClawLink
Securitytrails
Securitytrails
SecuritytrailsAPI KEYMCP

SecurityTrails is a cybersecurity platform providing comprehensive domain, IP, DNS, and WHOIS intelligence data.. Once connected, Hermes Agent can read and act on Securitytrails from chat — pairing, token refresh, and tool wiring handled for you.

12 tools

Most guides for giving Hermes Agent Securitytrails access start with registering your own OAuth app or pasting API keys into env files, then leave the token refresh and tool wiring to you. ClawLink gives Hermes a more practical Securitytrails setup: pair once in the browser and your always-on Hermes agent can act on Securitytrails for you, reading and doing real work on your behalf with no auth, token refresh, or tool wiring to build yourself.

Setup

It takes three steps to connect Hermes to Securitytrails.

  1. 1

    Install and pair

    Install the ClawLink plugin, then pair Hermes with a one-time browser approval:

    hermes plugins install ClawLink-HQ/hermes-plugin --enable
  2. 2

    Connect Securitytrails

    Paste your API key in the dashboard.

  3. 3

    Use it from chat

    Ask Hermes Agent: "What can you do with Securitytrails?"

Install by command

The prompt above walks Hermes through this. By hand, it is four commands and a browser approval:

hermes plugins install ClawLink-HQ/hermes-plugin --enable
hermes clawlink begin    # prints an approval link — open it and approve
hermes clawlink finish   # after approving in the browser
hermes clawlink test

Then connect Securitytrails in the ClawLink dashboard — paste your Securitytrails API key once.

Verify the connection by asking Hermes:

Pull the relevant data from Securitytrails, summarize it in plain English, and point out anything that needs attention.

Using a different agent?

The Hermes plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI:

npx -y @useclawlink/cli login

login opens the same browser approval and stores a credential locally. Once Securitytrails is connected in the dashboard, that agent calls the same 12 Securitytrails tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.

Securitytrails MCP for Hermes

Looking for a Securitytrails MCP server for Hermes Agent? ClawLink connects Securitytrails to Hermes Agent and exposes 12 Securitytrails tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using OpenClaw instead? The OpenClaw Securitytrails integration works the same way.

What the Hermes Agent Securitytrails integration can do

12 Securitytrails tools are ready for Hermes Agent once the account is connected.

All 12 Securitytrails tools for Hermes

ToolWhat it does
Get company associated ips securitytrails_get_company_associated_ipsRetrieve IPs associated with a company domain
Get domain securitytrails_get_domainRetrieves comprehensive domain information from SecurityTrails including current DNS records
Get domain ssl securitytrails_get_domain_sslFetch current and historical SSL certificate details for a hostname
Ip search statistics securitytrails_ip_search_statisticsFetch aggregated statistics for IP addresses matching a DSL query
List projects securitytrails_list_projectsList ASI projects available to the account
Ping securitytrails_pingTest authentication and connectivity with the SecurityTrails API
Scroll securitytrails_scrollContinue scrolling through DSL search results
Search ips securitytrails_search_ipsSearch IP addresses via SecurityTrails DSL
SQL API execute query securitytrails_sql_api_execute_queryExecute SQL-like queries against SecurityTrails data
SQL API scroll results securitytrails_sql_api_scroll_resultsFetch next page of SQL query results
Temp scrape securitytrails usage securitytrails_temp_scrape_securitytrails_usageRetrieve account usage information from the SecurityTrails API
Bulk static asset rules securitytrails_bulk_static_asset_rulesBulk add or remove static asset rules for a SecurityTrails ASI project

Try it: find the Securitytrails tool you need

Browse the 12 Securitytrails tools

Click any tool to see exactly what Hermes can do and copy a ready-to-use prompt.

Example prompts

Pull the relevant data from Securitytrails, summarize it in plain English, and point out anything that needs attention.

Pull the relevant data from Securitytrails, summarize it in plain English, and point out anything that needs attention.

Pull the relevant data from Securitytrails, summarize it in plain English, and point out anything that needs attention.

The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for Hermes Agent. That is fine if you want to build and maintain the integration yourself. Most teams just want Securitytrails working from chat.

ManualClawLink
Credential handlingCollect, validate, store, and rotate the Securitytrails API key yourself, then make sure every tool call uses the right account.Users complete the hosted ClawLink setup once and the connected Securitytrails account becomes available to the agent without you building credential management.
Ongoing maintenanceYou own refresh logic, permission debugging, environment config, and every provider-specific edge case for Securitytrails.ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure.
Agent usabilityYou still need to expose the right Securitytrails actions to the runtime in a format your agent can reliably use.12 tools for Securitytrails are already exposed through ClawLink, so the agent can read and act from chat immediately.

Composio also exposes Securitytrails to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for Hermes Agent users instead. You install the plugin once, connect Securitytrails in the browser, and the 12 tools above work from chat. There is no SDK and no config file, and the Securitytrails key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full Composio alternatives comparison.

Troubleshooting

Hermes paired but still can't use Securitytrails

Pairing is a two-step handshake: run hermes clawlink begin, approve the link in your browser, then run hermes clawlink finish. If you ran finish before approving, or the approval link expired, run hermes clawlink begin again to get a fresh link. Confirm the plugin was installed with --enable, then verify with hermes clawlink test.

Connection succeeds but no tools appear

Reconnect Securitytrails from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.

"Tool schema not loaded yet" error when calling Securitytrails tools

Securitytrails tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Securitytrails call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again.

Securitytrails returns 403 or "permission denied" on one action while others work

Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs.

API key setup works but results look incomplete

Double-check that the API key for Securitytrails has the right scopes or account access. A valid key can still be too limited for some reads or writes.

FAQ

Is there a Hermes Agent Securitytrails integration?

Yes. ClawLink is the fastest way to connect Hermes to Securitytrails: link your Securitytrails account once in the browser and Hermes Agent can call the Securitytrails API through 12 ready-made tools — no custom code or token handling.

How do I connect Securitytrails to Hermes with ClawLink?

Install the plugin with hermes plugins install ClawLink-HQ/hermes-plugin --enable, then pair once: run hermes clawlink begin, approve the link in your browser, and run hermes clawlink finish. Connect Securitytrails in the dashboard and Hermes can use it from the next message — no config files, and the Securitytrails key you paste is stored server-side instead of in your environment.

How long does it take to connect Securitytrails to Hermes Agent?

About two minutes. Sign in, click Connect next to Securitytrails in the dashboard, authenticate, and Hermes Agent can use it from the next chat message.

Why use ClawLink instead of wiring Securitytrails up myself?

The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for Hermes Agent. That is fine if you want to build and maintain the integration yourself. Most teams just want Securitytrails working from chat.

Hermes paired but still can't use Securitytrails

Pairing is a two-step handshake: run hermes clawlink begin, approve the link in your browser, then run hermes clawlink finish. If you ran finish before approving, or the approval link expired, run hermes clawlink begin again to get a fresh link. Confirm the plugin was installed with --enable, then verify with hermes clawlink test.