Skip to content
Back to the index

nps

pipeworx.ioInfrastructure🇺🇸

No liveness check has reached it yet; it has been in the index since 10 Oct 2026. How this is checked

NPS MCP Server exposes six tools through a JSON-RPC HTTP endpoint for querying National Park Service data. Developers can search parks, retrieve park details, check alerts, find campgrounds and activities, and access visitation statistics.

Inferred · not functionally tested

WebAPICloud-managed
nps preview
Visit pipeworx.io

Overview

6 features

Purpose: Accessing structured National Park Service data without manually searching park websites or building data integrations.

Inferred · not functionally tested

Audience: developers building travel, outdoor recreation, and national park applications

Inferred · not functionally tested

Functions: data_extraction

Inferred · not functionally tested

Interfaces: API: indicated (inferred, not tested) · MCP: indicated (inferred, not tested) · CLI: unknown · Self-hosting: unknown

Recorded constraints: pricing: unknown · license: Proprietary · platforms: WEB · deployment: browser, api_only, cloud_managed

Constraint provenance is unknown; confirm requirements with the publisher.

Record sources: gateway.pipeworx.io. These links do not verify the individual claims.

nps is an API design, testing & docs project. Inferred · not functionally tested: It focuses on accessing structured National Park Service data without manually searching park websites or building data integrations. Inferred · not functionally tested: nps is a B2B product aimed at developers building travel, outdoor recreation, and national park applications. Basis unknown · not verified: nps is available on the web and API.

Behind nps is Pipeworx, based in the United States. Inferred · not functionally tested: Key capabilities include park search, park details, and park alerts. Inferred · not functionally tested: Catalogued interfaces include an MCP server.

Summary written by a language model from the project’s public pages.

Tasks: Inferred · not functionally tested

  • Park search
  • Park details
  • Park alerts
  • Campground listings
  • Activity discovery
  • Visitation statistics

Topics: Inferred · not functionally tested

Tags
national-parks-apipark-datamcp-serveroutdoor-recreation-data

JSON profile · Text profile · Access guide

Built with & integrations

Hosting
Cloudflare
Connectors
MCP
Runs on
BrowserAPI-onlyCloud-managed
Detected from
Cloudflare
cf-ray header

Trust & compliance

Public signals
HTTPS

Indexing history

1

What PulseGate has recorded for this listing

  1. Indexed10 Oct · 00:02 UTC
    Nps seen via MCP Registry (official)
    Source: MCP Registry (official) · Open

Frequently asked questions about nps

What does nps do?
Inferred · not functionally tested: Nps focuses on accessing structured National Park Service data without manually searching park websites or building data integrations. It is catalogued under API design, testing & docs on PulseGate.
Who should use nps?
Inferred · not functionally tested: nps is a B2B product built for developers building travel, outdoor recreation, and national park applications.
What platforms does nps run on?
Basis unknown · not verified: nps runs on the web and API.
Is nps still active?
Unverified. nps has not been re-checked since it entered the index, so there is no finding either way — and only a positive finding would say otherwise.
What are alternatives to nps?
Similar projects tracked by PulseGate include nyc-parks, nasa, and nws.nyc-parksnasanws
Who develops nps?
nps is developed by Pipeworx, based in the United States.
Does nps have an API or integrations?
Inferred · not functionally tested: Yes — nps exposes an MCP server.

Similar projects

Closest matches by what these projects do