recon-mcp

MCPcommunity
v0.1.2io.github.oceanmodelingUnknownUpdated 11d agoGitHub

Hurricane reconnaissance data — HDOB flight observations, Vortex Data Messages, SFMR, and ATCF fixes

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 →
9GitHub stars
1Forks
11d agoLast update
Package
Authorio.github.oceanmodeling
LicenseUnknown
Version0.1.2
Sourcemcp-registry
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✗ Attestation rejected
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface12 tools · 1 privileged
Security scan⚠ Warnings (1)v6.0.0 · 19d agoHow well does this scan work?
PROVattestationArtifact built from https://github.com/jhm1909/recon but the listing declares https://github.com/mansurjisan/o
EvalsNone
IndexedAug 26, 2026

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

Tools

12 tools · 1 privileged
Statically extracted from the published packagev6.0.0 · 19d 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.

pre_commitPre-commit impact analysis

Pre-commit impact analysis

No input schema was published for this tool.

scopestaged or unstaged

staged or unstaged

No input schema was published for this tool.

architectureGenerate architecture documentation

Generate architecture documentation

No input schema was published for this tool.

onboardCodebase onboarding guide

Codebase onboarding guide

No input schema was published for this tool.

recon_mapArchitecture overview: tech stack, packages, entry points, health. WHEN: First time in a codebase, or need to recall architecture. NOT: You need details about a specific symbol (use recon_explain). THEN: recon_find to locate specific symbols.

Architecture overview: tech stack, packages, entry points, health. WHEN: First time in a codebase, or need to recall architecture. NOT: You need details about a specific symbol (use recon_explain). THEN: recon_find to locate specific symbols.

No input schema was published for this tool.

recon_findSmart search: exact name, wildcard (*Handler), or natural language. WHEN: Looking for a symbol, function, class, or pattern. NOT: You already know the symbol name and need full context (use recon_explain). THEN: recon_explain for details on a result.

Smart search: exact name, wildcard (*Handler), or natural language. WHEN: Looking for a symbol, function, class, or pattern. NOT: You already know the symbol name and need full context (use recon_explain). THEN: recon_explain for details on a result.

No input schema was published for this tool.

recon_explainFull 360-degree context of a symbol: callers, callees, flows, cross-language links. WHEN: You need to understand a function/class before modifying it. NOT: You just need to read the source code (use Read tool). THEN: recon_impact if you plan to change it.

Full 360-degree context of a symbol: callers, callees, flows, cross-language links. WHEN: You need to understand a function/class before modifying it. NOT: You just need to read the source code (use Read tool). THEN: recon_impact if you plan to change it.

No input schema was published for this tool.

recon_impactBlast radius: what breaks if you change this symbol, including affected tests. WHEN: Before modifying any exported function or shared type. NOT: Just exploring (use recon_explain first). THEN: Make the change, then recon_changes to verify.

Blast radius: what breaks if you change this symbol, including affected tests. WHEN: Before modifying any exported function or shared type. NOT: Just exploring (use recon_explain first). THEN: Make the change, then recon_changes to verify.

No input schema was published for this tool.

recon_changesGit diff → affected symbols → risk assessment → affected tests. WHEN: Before commit, or reviewing a PR. NOT: No changes have been made yet. THEN: Fix issues, then commit.

Git diff → affected symbols → risk assessment → affected tests. WHEN: Before commit, or reviewing a PR. NOT: No changes have been made yet. THEN: Fix issues, then commit.

No input schema was published for this tool.

recon_renameprivilegedGraph-aware safe rename across all files. Always dry_run first. WHEN: Renaming a symbol and want to catch all references. NOT: Simple text replacement in one file (use Edit tool). THEN: Review plan, then run with dry_run: false.

Graph-aware safe rename across all files. Always dry_run first. WHEN: Renaming a symbol and want to catch all references. NOT: Simple text replacement in one file (use Edit tool). THEN: Review plan, then run with dry_run: false.

No input schema was published for this tool.

recon_exportGenerate Mermaid diagram of package/symbol/file relationships. WHEN: Need visual representation for documentation or understanding. NOT: Just need a list of packages (use recon_map). THEN: Paste diagram in PR or docs.

Generate Mermaid diagram of package/symbol/file relationships. WHEN: Need visual representation for documentation or understanding. NOT: Just need a list of packages (use recon_map). THEN: Paste diagram in PR or docs.

No input schema was published for this tool.

recon_rulesCode quality analysis via knowledge graph: dead code, circular deps, unused exports. WHEN: Reviewing code quality, cleaning up, or auditing architecture. NOT: Looking for a specific symbol (use recon_find). THEN: recon_explain on flagged items for context.

Code quality analysis via knowledge graph: dead code, circular deps, unused exports. WHEN: Reviewing code quality, cleaning up, or auditing architecture. NOT: Looking for a specific symbol (use recon_find). THEN: recon_explain on flagged items for context.

No input schema was published for this tool.

12 of 12 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

Hurricane reconnaissance data — HDOB flight observations, Vortex Data Messages, SFMR, and ATCF fixes

Keywords
mcp
Alternatives
Comparing tool surfaces…

No dependency coverage

Forge's dependency resolver reads npm metadata only, so this PyPI package has no resolved tree. That is a gap in coverage, not a clean bill of health.

Topics

Related in weather