@erikirby/domain-intel

MCPcommunity
v1.0.0UnknownUnknownUpdated 4mo agonpmGitHub

Website intelligence for AI agents. Given any URL, returns tech stack, hosting provider, security posture, email config, SEO metadata, and DNS records. No scraping — uses standard HTTP/DNS/WHOIS protocols only.

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
37Downloads/wk
4mo agoLast update
Package
AuthorUnknown
LicenseUnknown
Version1.0.0
Sourcenpm+mcp-registry
npm@erikirby/domain-intel
GitHuberikirby/toolcompare-fyi
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface4 tools · none privileged
Security scan✓ Cleanv1.0.0 · 24d agoHow well does this scan work?
EvalsNone
IndexedAug 26, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

4 tools · none privileged
Statically extracted from the published packagev1.0.0 · 24d ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

tech_detectDetect technologies used by a website. Given a URL, identify CMS, frameworks, analytics tools, CDN, hosting provider, payment processors, and more. Uses only HTTP headers and HTML parsing — no scraping or third-party APIs.

Detect technologies used by a website. Given a URL, identify CMS, frameworks, analytics tools, CDN, hosting provider, payment processors, and more. Uses only HTTP headers and HTML parsing — no scraping or third-party APIs.

No input schema was published for this tool.

security_headersCheck security HTTP headers for a URL. Returns a security score, which headers are present (HSTS, CSP, X-Frame-Options, etc.) and which are missing. Essential for website security auditing.

Check security HTTP headers for a URL. Returns a security score, which headers are present (HSTS, CSP, X-Frame-Options, etc.) and which are missing. Essential for website security auditing.

No input schema was published for this tool.

email_securityCheck email security configuration for a domain. Returns SPF, DKIM, and DMARC record status. Essential for verifying deliverability and preventing email spoofing.

Check email security configuration for a domain. Returns SPF, DKIM, and DMARC record status. Essential for verifying deliverability and preventing email spoofing.

No input schema was published for this tool.

website_analyzeComprehensive website analysis. Given any URL, returns tech stack, hosting provider, security posture, SSL status, email security config, SEO metadata, social media profiles, WHOIS domain info, and DNS records. All from standard HTTP/DNS/WHOIS protocols — no scraping.

Comprehensive website analysis. Given any URL, returns tech stack, hosting provider, security posture, SSL status, email security config, SEO metadata, social media profiles, WHOIS domain info, and DNS records. All from standard HTTP/DNS/WHOIS protocols — no scraping.

No input schema was published for this tool.

4 of 4 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

Website intelligence for AI agents. Given any URL, returns tech stack, hosting provider, security posture, email config, SEO metadata, and DNS records. No scraping — uses standard HTTP/DNS/WHOIS protocols only.

Keywords
mcp
Alternatives
Comparing tool surfaces…

Tools exposed

4 tools · none privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

Dependency tree

What one Forge scan resolved from npm metadata on 2026-08-31 — observed resolution, not a publisher declaration.

60 packages resolved · 3 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

71 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

+59 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.