Securitytrails
NPM · @PIPEWORX/MCP-SECURITYTRAILS · 2 COMPONENTS
SecurityTrails MCP — wraps SecurityTrails API (securitytrails.com)
Available components
Last scanned (9 hours ago)
Scores higher than 87% of npm servers
Category Security
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-securitytrails). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 471 tokens (~117/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +1
- Stability: 0.20 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- Package version: 0.2.0 → 0.2.1 functional
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 82
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/@pipeworx/mcp-securitytrails@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-securitytrails |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-securitytrails/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3692343114 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:abc678dc4c9da90af68f73b94be94a5764540b943bccd63872acf6b865cbc9ded09345bdf719fb0efaf83574f1a0b40bb9e9d4ee45800484bf5a87e93 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
securitytrails_dns_history ~136
Historical DNS records for <hostname>. Returns past record values with first/last-seen dates for a given record type (a, aaaa, mx, ns, soa, txt). Example: securitytrails_dns_history({ hostname: "github.com", type: "a", _apiKey: "your-key" })
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | SecurityTrails API key |
| hostname | string | yes | Apex domain / hostname, e.g. "github.com" |
| type | string | – | DNS record type: a, aaaa, mx, ns, soa, or txt (default "a") |
No output schema declared.
No examples provided.
securitytrails_domain ~109
Domain intel (DNS, subdomain count) for <hostname>. Returns current A/MX/NS records, subdomain count, and Alexa rank. Example: securitytrails_domain({ hostname: "github.com", _apiKey: "your-key" })
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | SecurityTrails API key (get one free at securitytrails.com — 50 lookups/mo) |
| hostname | string | yes | Apex domain / hostname, e.g. "github.com" |
No output schema declared.
No examples provided.
securitytrails_subdomains ~86
Enumerate subdomains of <hostname>. Returns the subdomain labels plus fully-qualified domains. Example: securitytrails_subdomains({ hostname: "github.com", _apiKey: "your-key" })
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | SecurityTrails API key |
| hostname | string | yes | Apex domain / hostname to enumerate, e.g. "github.com" |
No output schema declared.
No examples provided.
securitytrails_whois ~86
WHOIS for <hostname>. Returns registrar, creation/expiration dates, and registration contacts. Example: securitytrails_whois({ hostname: "github.com", _apiKey: "your-key" })
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | SecurityTrails API key |
| hostname | string | yes | Apex domain / hostname, e.g. "github.com" |
No output schema declared.
No examples provided.
How do I install the Securitytrails MCP server?
Securitytrails runs locally as an npm package, launched with npx -y @pipeworx/mcp-securitytrails. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-securitytrails
claude mcp add pipeworx-io-securitytrails -- npx -y @pipeworx/mcp-securitytrails
What is the Securitytrails MCP server?
Securitytrails is an MCP server listed in the public MCP registry as io.github.pipeworx-io/securitytrails. SecurityTrails MCP, wraps SecurityTrails API (securitytrails.com). This page covers its npm package (@pipeworx/mcp-securitytrails).
Is the Securitytrails MCP server safe to use?
Securitytrails scores 85 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Securitytrails MCP server expose?
Securitytrails exposes 4 tools: securitytrails_domain, securitytrails_subdomains, securitytrails_dns_history, securitytrails_whois. Their descriptions and schemas cost roughly 417 tokens of context every time the server is loaded.
Is the Securitytrails MCP server still maintained?
Securitytrails is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Securitytrails MCP server under?
Securitytrails declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.