io.github.houtini-ai/fanout

Name: io.github.houtini-ai/fanout
Rating: 60 (1 reviews)
Author: io.github.houtini-ai

MCPcommunity

v0.2.6io.github.houtini-aiUnknownUpdated 5mo agonpm GitHub

Multi-URL comparative content analysis with topical gap detection

[](research/keyword-fanout-explained.md) Advanced content gap analysis for the AI search era Analyze your content to discover what user queries it covers (and misses) using the same techniques AI search engines use internally. Why this matters | What it does | Installation | How to use | Methodology | Features deep-dive | Parameters | Troubleshooting The problem: Traditional SEO focused on…

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →

5mo agoLast update

Package

Authorio.github.houtini-ai

LicenseUnknown

Version0.2.6

Sourcemcp-registry

npm@houtini/fanout-mcp

GitHubhoutini-ai/fanout-mcp

Trust Status

60/100Good

✓Listed in Forge index+10/10

—Publisher identity verified+0/25

→ Publisher: run `forge publish` from the package repo to claim ownership

—Ed25519 publish signature+0/10

→ 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>" }

✓CVE scan · clean+30/30

✓Static analysis · clean+20/20

—npm provenance (Sigstore)+0/5

→ Publish from GitHub Actions with the --provenance flag

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 surface1 tool · none privileged

Security scan✓ Cleanv0.2.11 · 20d ago

EvalsNone

IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts — it cannot prove the absence of malicious code.

About

Keywords

mcp