M

Monomi

Know your exposure before attackers do: passive attack surface recon for agents

0x41io/monomi · v1.8.0 · 26906bc · Tools & Integrations

by 0x41ioOwner verifiedScan grade: Acceptable

Monomi is an open-source recon tool by 0x41. It maps a domain's external attack surface from public sources only, and its MCP server lets AI agents run each check as its own tool.

InstallSource
Follow0
Trust Score77Security scan74ComponentsScan pending
Protect this install with HOL Guard

Guard checks the skills and MCP servers a plugin adds on your machine and asks you before a risky action runs. The scores above are free, and no plan changes them.

Is Monomi a fit?

From the plugin's manifest and HOL's scan. Anything the plugin does not declare is shown as not declared.

Works with

  • MCP

Before you install

Sign-in
Not declared
Declared access
Not declared
License
Not declared

Check before relying on it

  • 1 medium finding from the scan. See the evidence
  • No license declared in the manifest.

About Monomi

What it checks

  • Subdomains from Certificate Transparency logs (crt.sh + Cert Spotter), auto-categorized
  • Hosting: IPs, ASN, provider and country
  • Open ports and known CVEs from Shodan InternetDB, with CDN edge IPs (Cloudflare, CloudFront, Okta) flagged
  • Email spoofing: SPF, DMARC and DKIM, with a verdict
  • Subdomain takeover: dangling CNAMEs flagged as leads, dead unclaimable records marked stale
  • IP threat-intel: Tor, VPN, hosting and scanner labels

Built to be trusted

  • Passive by default: the MCP server never contacts the target
  • Every finding cites its source and collection time
  • Leads, not verdicts: CVEs and takeovers are flagged to verify

For MSPs, small security teams, bug bounty hunters, and the agents they run. Python, MIT license, CLI or MCP server.

Monomi (物見): Japanese for "lookout."

What is Monomi?

Monomi is a published tools & integrations plugin for AI coding agents in the MCP ecosystem, developed by 0x41io and distributed through the HOL AI plugin registry. MCP server: passive external attack surface recon for agents, with subdomain discovery from Certificate Transparency logs, hosting and port/CVE lookups, email spoofing and subdomain takeover checks, and suspicious-IP investigation, each result carrying its source; also a Python CLI with optional evidence-cited AI reports.

Canonical slug
0x41io/monomi
Version
v1.8.0 · 26906bc · updated Nov 6, 2026

Registry snapshot

Owner verification
Verified on HOL as @0x41io
Scanner
HOL plugin scanner
Security result
Needs review
Digest verified
Yes

Trust and security

Trust & reputation

On-Chain Verified
77

HOL Trust Score

Per-metric points (0–100 each) combined via a weighted average into the overall score.

Installability
100/100
Maintenance
90/100
MCP server setup
100/100
Plugin Security
74/100
Provenance
80/100
Publisher Quality
100/100

Provenance

Plugin root
.
Source repo
https://github.com/0x41io/monomi
Source commit
26906bc243a9…
Publisher verified
Yes
Owner verified
@0x41io
Agent Plugins 1.0
Not detected

Continuous scanner CI not detected

This plugin remains listed. Its overall trust score is reduced by 10% because security checks are not maintained in the source repository's CI.

Optional: maintain the scanner in the source repository's CI to receive the full trust score. Listing does not require that change.

README badge not detected

Plugin owners can add the HOL badge to the repository README from Guard Plugins. Distribution, not security evidence. It adds a 2% engagement adjustment to the overall trust score and never changes the security result.

Security posture

See how the Trust Score is computed
Needs review
Security result
74
Security score
0
High findings
Provider
codex-plugin-scanner
Grade
C · Acceptable
Version
3.24.2
cisco-skill-scanner: skippedcisco-mcp-scanner: skipped

Manifest Validation

21/31

9 checks

Security

16/16

9 checks

Operational Security

0/6

5 checks

Best Practices

6/9

5 checks

Marketplace

N/A

3 checks · not applicable

Skill Security

N/A

3 checks · not applicable

Code Quality

10/10

2 checks

Published advisories

None matched in GitHub security advisories, checked . This covers published advisories only, not problems nobody has reported.

GitHub security advisories are those the source repository has published.

Findings

mediumoperational-securityDEPENDENCY_LOCKFILE_MISSING

requirements.txt is present without a corresponding lockfile or pinned dependency snapshot.

Commit a lockfile or use fully pinned requirements for reproducible dependency resolution.

lowoperational-securityDEPENDABOT_MISSING

Automation or dependency surfaces exist, but .github/dependabot.yml is missing.

Add Dependabot updates for GitHub Actions and dependency manifests.

infomanifest-validationPLUGIN_JSON_RECOMMENDED_AUTHOR

The manifest is missing the documented recommended field "author".

Add "author" to strengthen the plugin manifest metadata.

infomanifest-validationPLUGIN_JSON_RECOMMENDED_LICENSE

The manifest is missing the documented recommended field "license".

Add "license" to strengthen the plugin manifest metadata.

infomanifest-validationPLUGIN_JSON_RECOMMENDED_KEYWORDS

The manifest is missing the documented recommended field "keywords".

Add "keywords" to strengthen the plugin manifest metadata.

infomanifest-validationPLUGIN_JSON_INTERFACE_SHORTDESCRIPTION

The interface object is missing a valid "shortDescription" value.

Add a valid "shortDescription" field to the interface metadata.

infomanifest-validationPLUGIN_JSON_INTERFACE_LONGDESCRIPTION

The interface object is missing a valid "longDescription" value.

Add a valid "longDescription" field to the interface metadata.

infomanifest-validationPLUGIN_JSON_INTERFACE_CAPABILITIES

The interface object is missing a valid "capabilities" value.

Add a valid "capabilities" field to the interface metadata.

infomanifest-validationPLUGIN_JSON_INTERFACE_ASSET_WEBSITEURL

The interface field "websiteURL" must use HTTPS or point to a safe in-repo asset.

Update "websiteURL" to use HTTPS or an existing relative asset path.

infomanifest-validationPLUGIN_JSON_INTERFACE_ASSET_PRIVACYPOLICYURL

The interface field "privacyPolicyURL" must use HTTPS or point to a safe in-repo asset.

Update "privacyPolicyURL" to use HTTPS or an existing relative asset path.

infomanifest-validationPLUGIN_JSON_INTERFACE_ASSET_TERMSOFSERVICEURL

The interface field "termsOfServiceURL" must use HTTPS or point to a safe in-repo asset.

Update "termsOfServiceURL" to use HTTPS or an existing relative asset path.

infomanifest-validationPLUGIN_JSON_INTERFACE_ASSET_COMPOSERICON

The interface field "composerIcon" must use HTTPS or point to a safe in-repo asset.

Update "composerIcon" to use HTTPS or an existing relative asset path.

infomanifest-validationPLUGIN_JSON_INTERFACE_ASSET_LOGO

The interface field "logo" must use HTTPS or point to a safe in-repo asset.

Update "logo" to use HTTPS or an existing relative asset path.

infomanifest-validationPLUGIN_JSON_INTERFACE_ASSET_SCREENSHOTS

The interface field "screenshots" must use HTTPS or point to a safe in-repo asset.

Update "screenshots" to use HTTPS or an existing relative asset path.

infobest-practicesCODEXIGNORE_MISSING

A .codexignore file helps prevent accidental inclusion of local artifacts and secrets.

Add a .codexignore file with generated assets, local state, and secret paths.

Install guidance

Install in Source

Install v1.8.0 from a native release archive or pinned source.

Install guide
  1. 1

    Download the release archive

    Use the v1.8.0 archive. That tag is a different source revision from later commits on the default branch.

    shell
  2. 2

    Follow the publisher install guide

    https://github.com/0x41io/monomi/blob/v1.8.0/docs/INSTALL.md

Did setup work in Source?

No setup reports for Source yet. Self-reported by signed-in visitors. Copying a command is not counted, and most installs are never reported.

Attested installs: Fewer than 10 attested installs of this plugin in week 2026-W44, so no number is shown. Counted from opt-in HOL Guard install reports, once per machine and runtime, and never mixed with the answers above. How install reports work.

0x41 octopus black
1 / 1

0x41 octopus black

Full size
Loading reviews

Plugin manifest

{
  "name": "monomi",
  "version": "1.8.0",
  "description": "MCP server: passive external attack surface recon for agents, with subdomain discovery from Certificate Transparency logs, hosting and port/CVE lookups, email spoofing and subdomain takeover checks, and suspicious-IP investigation, each result carrying its source; also a Python CLI with optional evidence-cited AI reports",
  "repository": "https://github.com/0x41io/monomi",
  "homepage": "https://github.com/0x41io/monomi",
  "interface": {
    "displayName": "Monomi",
    "developerName": "0x41io",
    "category": "Tools & Integrations"
  },
  "holReleaseTag": "v1.8.0",
  "holAssessedCommit": "26906bc243a9699de106a25b8e00bc5be2857320",
  "holManifestOrigin": "synthesized",
  "registryIndexVersion": 9
}

File inventory

.codex-plugin/plugin.json

plugin-manifest

711 bytes

9f19c73da42eec72…

LICENSE

file

1,416 bytes

562d9a16184ea4ec…

README.md

file

24,288 bytes

604483e29b6fbda9…

README.md

file

24,288 bytes

604483e29b6fbda9…

requirements.txt

file

95 bytes

fa372201a3721379…

SECURITY.md

file

1,740 bytes

47c1263299399e5e…

Monomi — Frequently asked questions

What is Monomi?
Monomi is an AI plugin in the HOL registry. Monomi is an open-source recon tool by 0x41. It maps a domain's external attack surface from public sources only, and its MCP server lets AI agents run each check as its own tool. What it checks Subdomains from Certificate Transparency logs (crt.sh + Cert Spotter),…
How do I install Monomi?
Install Monomi in your harness: Source — https://github.com/0x41io/monomi/releases/tag/v1.8.0. Full step-by-step guidance is on the HOL plugin page.
How do I install Monomi in Source?
To install Monomi in Source, start with https://github.com/0x41io/monomi/releases/tag/v1.8.0. The complete step-by-step install guide for Source is on the HOL plugin page.
Is Monomi free?
Monomi is listed as open source on HOL.
How is the Trust Score for Monomi computed?
Monomi has a HOL Trust Score of 77 out of 100. The score is a weighted sum of six components from a static scan of the source, capped for high-severity findings and adjusted by two disclosed policies. Memberships and payments are not inputs, and a scan is not a safety guarantee. Full breakdown: https://hol.org/registry/plugins/0x41io%2Fmonomi/trust
Who publishes Monomi?
Monomi is published by 0x41io and listed on HOL.
Is Monomi available now?
Monomi is currently available according to its latest public launch.

Directory acceptance

Listed in 0 of 5 directory lists

Read from the list each directory publishes on GitHub. Being listed means the directory accepted the plugin; it is not a HOL security rating.

Lists last read . HOL re-reads them every day.

Submitting it? Check it against each directory's rules

Install signal

HOL cannot see every install. These are separate signals from different sources, so they are not added together. Counts under each floor show as <N.

Install commands issued here
<5
HOL Guard install commands issued from this listing, last 28 days.
Opt-in install reports
<10
Machines that reported installing it through HOL Guard in week 2026-W44. Reporting is opt-in, so most installs are not counted.
HOL Guard workspaces
<5
Workspaces that approved it or include it in an approved-plugin feed, as of today.
New GitHub stars
<5
From HOL's GitHub snapshots of the repository, 2026-11-02 to 2026-11-06.

Related plugins

Ordered by Trust Score. Listings cannot pay for these positions. Check each one fits your task before switching from Monomi.

Alternatives in Tools & Integrations

See all Tools & Integrations plugins

History, reviews, and similar plugins

Latest launch