Back to MCP Trust Indexm8ven
C
Emerging
74/100
4 days ago

FofaMap

一款证据驱动的 FOFA 资产测绘智能体：支持自然语言侦察、AI 反思、CLI / MCP / Skill / REST API，以及经人工审批的 Nuclei 扫描。

→ asaotomo/FofaMap· listed on github_topic

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

asaotomo

Source: github_topic · also listed on Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

GitHubGlama

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
✅
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 3 credentials: FOFAMAP_SERVICE_TOKEN, FOFAMAP_JWT_PUBLIC_KEY, FOFAMAP_SCAN_APPROVAL_SECRET
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
🔐 secretFOFAMAP_SERVICE_TOKENexport ='请替换为足够长的随机值'
configFOFAMAP_MCP_RESOURCE_URL
🔐 secretFOFAMAP_JWT_PUBLIC_KEY/ FOFAMAP_JWT_ISSUER / FOFAMAP_JWT_AUDIENCE 远程 JWT 校验
configFOFAMAP_JWT_ISSUERFOFAMAP_JWT_PUBLIC_KEY / / FOFAMAP_JWT_AUDIENCE 远程 JWT 校验
configFOFAMAP_JWT_AUDIENCEFOFAMAP_JWT_PUBLIC_KEY / FOFAMAP_JWT_ISSUER / 远程 JWT 校验
configFOFAMAP_MCP_ISSUER_URL
configFOFAMAP_DATABASE_URL任务数据库，默认本地 SQLite
configFOFAMAP_ENABLE_SCANNINGexport =true
configFOFAMAP_BIND_HOSTREST / MCP HTTP 绑定地址
configFOFAMAP_MCP_PORTMCP HTTP 端口，默认 8001
🔐 secretFOFAMAP_SCAN_APPROVAL_SECRETexport ='至少24个字符的高熵随机值'
configFOFAMAP_NUCLEI
configFOFAMAP_NUCLEI_ID_ALLOWLISTMCP / REST 的调用顺序是 nuclei_plan → 人工确认 → nuclei_execute。基线外的精确模板 ID 需要管理员通过 加入允许列表。
configFOFAMAP_NUCLEI_TEMPLATE_ALLOWLIST允许 REST / MCP 使用的本地模板路径
configFOFAMAP_PORTREST 端口，默认 8000
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

15/15 tools missing one or more hints — fofa_validate_query (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); fofa_fields (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); fofa_account (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +12 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tool test coverage

10/15 tools referenced in tests (67%)

Write tests that reference each tool by name so every tool has at least one test.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 3 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/asaotomo-fofamap-nlvqse)](https://m8ven.ai/mcp/asaotomo-fofamap-nlvqse)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 86531255305a9af7c68c7d5283ac89984f7e87cf
code hash: 5fbeaaf21079702815b4f1fcb587f1d6a571fa397962cb50419ab6ccbdc5b36f
verified: 8/16/2026, 9:03:58 AM
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client