com.olyport/wildfire

MCPcommunitylive
v1.1.0com.olyportUnknownUpdated 6mo ago

Active wildfire incidents from the National Interagency Fire Center

Endpoint healthlive
checked 6 days ago · 273ms
100% of the last 5 checks reached this endpoint
Works in
ClaudeCursorCopilotChatGPTGemini

Inferred from the transports this listing declares (streamable-http). 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 →
6mo agoLast update
Package
Authorcom.olyport
LicenseUnknown
Version1.1.0
Sourcemcp-registry
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/30
→ Publisher: this listing has no repository on file, so `forge publish` cannot verify ownership automatically. Use "Claim this listing" above — Forge reviews these by hand.
—Domain verification+0/10
→ Not currently available for this listing type — the domain-verification check only runs for npm-backed packages today, so this row cannot be earned here yet regardless of what's hosted at the domain.
✓Prompt-injection scan · clean+30/30
✓Obfuscation / exfil scan · clean+20/20
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
DependenciesNot audited
Tool surface3 tools · none privileged
Security scan✓ Cleanvlive · 1mo agoHow well does this scan work?
EvalsNone
IndexedJun 13, 2026

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

Tools

3 tools · none privileged
Observed live from the vendor's endpoint1mo ago

Read from a real MCP initialize → tools/list handshake against the declared endpoint. No tool was ever invoked — tools/list is the read-only introspection call the protocol defines for this. It reflects what the server advertised at that moment; a hosted endpoint is not pinned to any version and can change without notice.

  • https://mcp.olyport.com/wildfire/mcp3 tools · 1373ms
get_active_firesGet current active wildfire incidents from NIFC. Returns data on active wildfires including name, location, size, and containment status. Data is updated frequently during fire season. Args: state: Two-letter US state abbreviation to filter by (e.g. 'CA', 'OR'). min_acres: Minimum fire size in acres to include (e.g. 100 for fires over 100 acres). limit: Maximum number of fires to return (default 50).

Get current active wildfire incidents from NIFC. Returns data on active wildfires including name, location, size, and containment status. Data is updated frequently during fire season. Args: state: Two-letter US state abbreviation to filter by (e.g. 'CA', 'OR'). min_acres: Minimum fire size in acres to include (e.g. 100 for fires over 100 acres). limit: Maximum number of fires to return (default 50).

No input schema was published for this tool.

get_fire_perimetersGet fire perimeter data for active or recent wildfires. Returns perimeter boundaries and associated metadata. Useful for understanding the geographic extent of fires. Args: fire_name: Name of a specific fire to look up (case-insensitive partial match). state: Two-letter US state abbreviation to filter by.

Get fire perimeter data for active or recent wildfires. Returns perimeter boundaries and associated metadata. Useful for understanding the geographic extent of fires. Args: fire_name: Name of a specific fire to look up (case-insensitive partial match). state: Two-letter US state abbreviation to filter by.

No input schema was published for this tool.

get_fire_statsGet wildfire statistics summary including total fires and acres burned. Returns aggregate statistics from active incident data. When no year is specified, returns current year statistics. Args: year: Year to get statistics for (e.g. 2025). Defaults to current year.

Get wildfire statistics summary including total fires and acres burned. Returns aggregate statistics from active incident data. When no year is specified, returns current year statistics. Args: year: Year to get statistics for (e.g. 2025). Defaults to current year.

No input schema was published for this tool.

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

Active wildfire incidents from the National Interagency Fire Center

Keywords
mcp
Alternatives
Comparing tool surfaces…

No dependency coverage

This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.