Search / io.github.pipeworx-io/fema-nfhl
Fema Nfhl
R0· no sign-inFEMA National Flood Hazard Layer (NFHL) MCP
v0.1.1 · active · repository · website · descriptor JSON · versions
Search / io.github.pipeworx-io/fema-nfhl
R0· no sign-inFEMA National Flood Hazard Layer (NFHL) MCP
v0.1.1 · active · repository · website · descriptor JSON · versions
{
"mcpServers": {
"fema-nfhl": {
"type": "http",
"url": "https://gateway.pipeworx.io/fema-nfhl/mcp"
}
}
}claude mcp add --transport http fema-nfhl https://gateway.pipeworx.io/fema-nfhl/mcp[mcp_servers.fema-nfhl]
url = "https://gateway.pipeworx.io/fema-nfhl/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"fema-nfhl": {
"type": "remote",
"url": "https://gateway.pipeworx.io/fema-nfhl/mcp",
"enabled": true
}
}
}{
"mcpServers": {
"fema-nfhl": {
"type": "http",
"url": "https://gateway.pipeworx.io/fema-nfhl/mcp"
}
},
"deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=fema-nfhl&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vZ2F0ZXdheS5waXBld29yeC5pby9mZW1hLW5maGwvbWNwIn0%3D"
}{
"servers": {
"fema-nfhl": {
"type": "http",
"url": "https://gateway.pipeworx.io/fema-nfhl/mcp"
}
}
}{
"mcpServers": {
"fema-nfhl": {
"httpUrl": "https://gateway.pipeworx.io/fema-nfhl/mcp"
}
}
}extensions:
"fema-nfhl":
enabled: true
name: "fema-nfhl"
type: streamable_http
uri: "https://gateway.pipeworx.io/fema-nfhl/mcp"
timeout: 300
Not scored: fewer than three checks apply, usually because no remote answered a credential-free probe or the server is a local package.
protocol.modernnewest supported version is 2025-03-26; 2026-07-28 not supported, older versions are deprecated until 2027-07-28protocol.statelessonly applies to 2026-07-28 serversprotocol.transportstreamable HTTPprotocol.list_ttlonly applies to 2026-07-28 serversauth.prm, auth.as_metadata, auth.cimdno remote uses OAuthauth.secret_in_urlno templated URLtools.descriptions, tools.description_length, tools.schemas, tools.annotations, tools.directory_hints, tools.token_cost, tools.api_dumptool list unknown (behind auth, not probed, or empty)stability.changes, stability.rug_pulltool list unknowndeps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI packagenfhl_layersremovedList every layer in the FEMA National Flood Hazard Layer MapServer with its id, name and geometry type, plus a plain-English guide to the layers that matter (flood hazard zones, base flood elevations, LOMRs, LOMAs, FIRM panels, levees, NFHL availability). Call this before nfhl_query.
nfhl_queryremovedQuery any layer of the FEMA National Flood Hazard Layer with an ArcGIS WHERE clause and optional bounding box — flood hazard zones, base flood elevations, floodways, LOMRs and LOMAs, FIRM panels with their effective dates, levees, cross-sections, political jurisdictions. Use for area questions ("every floodway polygon in this county", "LOMRs issued on this DFIRM"). Layer ids come from nfhl_layers.
nfhl_flood_zone_at_pointremovedAUTHORITATIVE flood-zone lookup: given a latitude/longitude, return the effective FEMA FIRM flood zone for that spot — the zone code (A, AE, AH, AO, VE, X, D), its subtype, whether it is in a Special Flood Hazard Area, the static base flood elevation, and the governing DFIRM id — plus nearby base flood elevation lines. PREFER OVER WEB SEARCH for "is this address in a flood zone" or "does this property need flood insurance". Distinguishes "outside the floodplain" from "never mapped", which a plain empty result does not.
recallremovedRetrieve a value previously saved via remember, or list all saved keys (omit the key argument). Use to look up context the agent stored earlier — the user's target ticker, an address, prior research notes — without re-deriving it from scratch. Scoped to your identifier (anonymous IP, BYO key hash, or account ID). Pair with remember to save, forget to delete.
rememberremovedSave data the agent will need to reuse later — across this conversation or across sessions. Use when you discover something worth carrying forward (a resolved ticker, a target address, a user preference, a research subject) so you don't have to look it up again. Stored as a key-value pair scoped by your identifier. Authenticated users get persistent memory; anonymous sessions retain memory for 24 hours. Pair with recall to retrieve later, forget to delete.
pipeworx_feedbackremovedTell the Pipeworx team something is broken, missing, or needs to exist. Use when a tool returns wrong/stale data (bug), when a tool you wish existed isn't in the catalog (feature/data_gap), or when something worked surprisingly well (praise). ONLY for tools served by this Pipeworx connection — if the tool came from a different MCP server in your client (another vendor's Gmail, Splunk, Slack, etc. connector), we cannot fix it and reporting it here only delays you; file it with that server instead. Not sure? Pipeworx tool names are the ones this connection lists. Describe the issue in terms of Pipeworx tools/packs — don't paste the end-user's prompt. Filing without an account returns a `claim_token`; pass it back later as pipeworx_feedback({claim_token:"pwfb_…"}) to read whether it was fixed and what changed. The team reads digests daily and signal directly affects roadmap. Rate-limited to 5 per identifier per day. Free; doesn't count against your tool-call quota.
ai_visibility_checkremovedProbe one or more LLMs for what they know about a business / brand / product / topic and score visibility (0-100) per model. Default model is Workers AI Llama-3.3-70b (free); pass `_apiKey` to also probe Anthropic (BYO key — you pay Anthropic directly for those calls). Returns per-model {score, confidence, signals, raw_response} + a combined view. Useful for AI-marketing audits, pre-launch brand checks, competitive monitoring.
generate_llms_txtremovedGenerate a production-ready llms.txt file for any URL so AI crawlers (ChatGPT, Claude, Perplexity) can index the site cleanly. Fetches the page, extracts title/description/key links, and emits the standard llms.txt markdown format. Output is a single text blob ready to drop at site-root/llms.txt. Useful for: getting a client's site indexed by AI, drafting llms.txt for your own project, or auditing how an AI crawler would see a competitor.
pipeworx_trendingremovedWhat other AI agents are calling on Pipeworx right now. Returns the top tools, top packs, and total call volume over a recent window (24h, 7d, or 30d). Useful for: (1) discovering what data sources are hot for current events, (2) confirming a popular tool is the canonical choice before asking your own question, (3) seeing whether your use case aligns with what most agents need. Self-aggregating signal — derived from CF analytics-engine, no PII, just (pack, tool, count). Cached 5min-1h depending on window.
research_rowremovedClaygent-style per-row research: answer ONE question about ONE company and return a JSON object matching your output_schema, with every field wrapped in its own evidence — {value, evidence_url, quote, status}. status is NEVER self-reported by the model: "found" means this code independently verified the model's quote is a VERBATIM substring of text actually fetched; "inferred" means a value was given but the quote could not be verified; "not_established" means no source answered the field, and its value is always null — never guessed, never a blended score. Sources: "web" fetches the company's own site (entity.domain required — homepage, /about, /leadership) via fetch_url; "catalog" checks entity_profile (SEC EDGAR; resolved:false for a private company is expected, not a failure); "both" (default) tries both. max_cost (USD, default 0.02, max 0.50) scales how many pages are fetched and refuses up front if it is too small to pay for even one extraction call (floor $0.002) — never silently overspends. A row where every source comes back empty costs nothing: every field is mechanically not_established with NO model call made. For a boolean/derived field (e.g. "does this company sell to healthcare"), the quote only has to SUPPORT the value — a descriptive sentence about customers/products counts, the source need not state the answer verbatim. leadership_page_status ("fetched"|"not_found"|"not_attempted", plus leadership_note) says plainly whether a leadership/team page was actually read, so a named-person field (head_of_sales) coming back not_established is distinguishable from "this company just doesn't publish one" vs. "we never checked". model_output_empty:true means the model returned nothing usable (a transport/budget problem) — every field is not_established for THAT reason, never read as 20 individual "no" judgments. Use with a fixed question + schema across many rows for "Claygent over N companies with a hard cost cap" (composes with batch callers). For picking from a fixed label list instead of extracting open fields, use classify_row (cheaper, one model call).
Showing the latest 10. Full history: list_changes · trend: quality JSON.
Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.
+repository +namespace-matches-repo +website +reachable +uptime-98% +updated-23d-ago
Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.
| remote | auth | reachable | uptime 30d | p50 | protocol | last ok |
|---|---|---|---|---|---|---|
https://gateway.pipeworx.io/fema-nfhl/mcp streamable-http | none | yes | 98% | 44 ms | 2025-03-26 | 2026-10-19 |
No tools observed. Tools appear once a credential-free probe can list them.
Schemas: list_tools.
And 1,847 more from this publisher.
{
"name": "io.github.pipeworx-io/fema-nfhl",
"title": "Fema Nfhl",
"$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
"remotes": [
{
"url": "https://gateway.pipeworx.io/fema-nfhl/mcp",
"type": "streamable-http"
}
],
"version": "0.1.1",
"repository": {
"url": "https://github.com/pipeworx-io/mcp-fema-nfhl",
"source": "github"
},
"websiteUrl": "https://pipeworx.io/packs/fema-nfhl",
"description": "FEMA National Flood Hazard Layer (NFHL) MCP"
}