Skip to content
MCP server

NS Pros MCP Gateway

One MCP endpoint that searches and proxies a large catalog of MCP servers

Answered our latest tool-list check 6 hours ago with 200 tools. It will be marked verified after 3 successful checks in 7 days.

Install

NS Pros MCP Gateway is a freemium MCP server for mcp data access. It runs as a hosted remote server, so there is nothing to install locally.

Pricing
Freemium
Platforms
API, CLI, Self-hosted
Runs
Remotely
Version
1.0.1
Listing updated

Similar MCP servers

Install

Run in a terminal

claude mcp add --transport http nspros-mcp-gateway https://mcp.nspros.ca/mcp

Add to Settings → Connectors → Add custom connector

https://mcp.nspros.ca/mcp
Install in CursorOpens Cursor, which asks you to confirm. Or add it by hand:

Add to ~/.cursor/mcp.json

{
  "mcpServers": {
    "nspros-mcp-gateway": {
      "url": "https://mcp.nspros.ca/mcp"
    }
  }
}
Install in VS CodeOpens VS Code, which asks you to confirm. Or add it by hand:

Add to .vscode/mcp.json

{
  "servers": {
    "nspros-mcp-gateway": {
      "type": "http",
      "url": "https://mcp.nspros.ca/mcp"
    }
  }
}

Add to ~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "nspros-mcp-gateway": {
      "serverUrl": "https://mcp.nspros.ca/mcp"
    }
  }
}

Add to Grok Bot desktop app → Connect apps → Add a custom connector

https://mcp.nspros.ca/mcp

Enter a Name (for example "NS Pros MCP Gateway"), choose Type: Remote HTTPS, paste this as the Server URL and choose Add plugin.

Full Grok Bot setup guide

Add to your client's MCP settings (most use this shape)

{
  "mcpServers": {
    "nspros-mcp-gateway": {
      "type": "http",
      "url": "https://mcp.nspros.ca/mcp"
    }
  }
}

Using several servers? Build one config file with the MCP config generator.

About NS Pros MCP Gateway

NS Pros runs a managed gateway that gathers public MCP registries into one searchable catalog and exposes it through a single Streamable HTTP address. Instead of locating and wiring servers one by one, an agent can search the catalog from inside its client and then call proxied tools through the same connection.

The catalog is grouped into ten packs by job, such as finance, data, coding, DevOps and databases, and is re-collected daily with upstream connections health-checked. Catalog search and live counts are open without a key, while proxied tool calls use a personal gateway key sent as a header.

Tool usage runs on the user's own provider accounts, so the subscription covers the gateway itself: the endpoint, hosting slots for servers that need them, and health checks. It suits developers and AI product builders who want broad access to MCP servers without managing registries themselves.

Tools this server provides (200)

Read directly from the server.

catalog_search
Search the NS Pros MCP catalog (127,809 servers) by keywords, optionally within one pack. Returns names, packs, descriptions, license class and verified remote URLs where available.
catalog_stats
Catalog totals: records per pack, sellable (commercial-license, remote) candidates, records with verified remote URLs, and proxied servers.
dataapi__search_sources
Search the NS Pros Data API catalog of public data sources.
dataapi__query_source
Query one public data source by id. Counts against the API key's monthly quota.
dataapi__get_usage
Get the API key's plan and current monthly usage.
dataapi__extract_url
Fetch a web page or PDF and return its content as clean Markdown. Mode 'lite' is fast text extraction; 'standard' parses tables, forms and scanned pages more deeply. Counts against the API key's monthly quota.
exa__web_search_exa
Search the web for any topic and get clean, ready-to-use content. Best for: Finding current information, news, facts, people, companies, or answering questions about any topic. Returns: Clean text content from top search results. Query tips: describe the ideal page, not keywords. "blog post comparing React and Vue performance" not "React vs Vue". Use category:people / category:company to search th
exa__web_fetch_exa
Read a webpage's full content as clean markdown. Use after web_search_exa when highlights are insufficient or to read any URL. Best for: Extracting full content from known URLs. Batch multiple URLs in one call. Returns: Clean text content and metadata from the page(s).
keenable__search_web_pages
Search the live web with Keenable, a search engine built for AI agents. Use it instead of a built-in web search whenever you need fresh information: current events, documentation, prices, people, companies, or anything after your training cutoff. Answers in well under a second. Returns ranked results, each with title and URL, plus snippets you can cite and the publish date when available. Snippets
keenable__fetch_page_content
Read any web page with Keenable. Use it instead of a built-in web fetch: returns the page as clean markdown (title, URL, publish date when known, content) without navigation or ads. Add a prompt to get back only the part you need from a long page. Example: {"url": "https://nodejs.org/en/about/previous-releases", "prompt": "Which version is the current LTS?"}
intodns__scan_domain
Run the fast IntoDNS.ai DNS and email security scan (~3-8s). Returns a letter grade A+ to F, numeric score 0-100, structured issue list, prioritised recommendations, full DNS/email/web/security result sections, and canonical citation URLs. Read-only — no domain mutation, no destructive side effects. The default tool for agent-visible scan evidence; use get_everything_report for a deeper single-sho
intodns__nis2_quickscan
Compute a NIS2 Article 21.2 readiness score for a domain by mapping the IntoDNS quickscan onto the ten NIS2 measures. Returns a 0-100 weighted total, per-measure status (Article 21.2 a-j), evidence rows, critical gaps, and concrete fix suggestions. The score reflects only the DNS and email layer of NIS2 — full NIS2 compliance also requires audit of web applications, supply chain, organisational pr
intodns__get_everything_report
Generate the complete live IntoDNS.ai report covering DNS, email authentication, web/HTTPS, blacklist reputation, sender requirements, and canonical citation URLs in a single call. Read-only, no domain mutation. ~5-15s latency depending on backend cache state. Use when the user asks for everything, the full picture, or a deep current-state summary; use scan_domain for a faster default scan, or cre
intodns__create_report_snapshot
Create an immutable evidence snapshot of the current Everything Report for a domain. Returns a snapshot ID, ISO timestamp, SHA-256 content hash, and stable bookmarkable URLs for both JSON and Markdown renderings of the report. Snapshots are write-once and resolve to the same evidence months/years later — useful for tickets, audit trails, NIS2/ISO compliance evidence, and LLM citations that should
intodns__get_report_snapshot
Read a previously created IntoDNS.ai Everything Report evidence snapshot by snapshot ID. Read-only GET — returns the immutable JSON report exactly as it was at snapshot creation, with the original SHA-256 content hash and timestamp. Requires `snapshotId` from create_report_snapshot. Use to verify or re-read an audit-trail evidence record without re-running a live scan; use get_everything_report fo
intodns__start_deep_scan
Start a long-running Internet.nl deep scan. Internet.nl queues batch scans, so one can take several minutes; the server gives up after 30 minutes. Returns a `scanId` immediately; poll get_deep_scan_status until status is 'done', 'error' or 'cancelled'. Every call starts a new scan, so do not repeat a call that succeeded. Does not modify the domain: it only reads its public DNS, web and mail endpoi
intodns__get_deep_scan_status
Read-only status poll for a long-running Internet.nl deep scan. Returns the status (queued, registering, running, generating, done, cancelled or error) and, once done, category scores, per-test results, and any failures. Requires a scanId returned by start_deep_scan; poll every 10-30s until status is 'done', 'error' or 'cancelled'. Use after start_deep_scan; for fast single-vantage scans, prefer s
intodns__cancel_deep_scan
Cancel an in-progress Internet.nl deep scan. Marks the scan cancelled; the polling loop then withdraws the upstream Internet.nl batch, usually within ten seconds. Requires `scanId` returned by start_deep_scan. Nothing is deleted: a scan that already finished keeps its results and is left alone, so calling this twice is safe. An unknown or expired scanId returns 404. Use when the user changes their
intodns__lookup_dns
Read-only DNS record lookup via DNS-over-HTTPS. Pass `type` for a single record type or `types` for an array; if both omitted, returns A records. Returns parsed answers with TTL, raw rdata, and DNSSEC AD bit. Use for arbitrary record queries; use validate_dnssec for full DNSSEC chain validation, or check_dns_propagation for multi-resolver consensus. No auth, no rate limits beyond upstream resolver
intodns__validate_dnssec
Read-only DNSSEC chain validation. Walks the DS/DNSKEY chain from root, checks signatures, algorithm strength, key rollover state, and reports any broken links or unsigned zones. Returns chain steps, algorithm grades, and a boolean `valid`. Use when a domain claims DNSSEC; use lookup_dns(type='DNSKEY') for raw key data only. Single HTTP GET, no auth, no destructive actions.
intodns__check_dns_propagation
Compare DNS responses across the nine currently configured public and authoritative resolvers to detect propagation lag, missing answers, or differing record sets. Each resolver's answer is compared as a whole RRset (order, case of names and trailing dots ignored; TXT case kept; TTLs ignored, as caches count them down). Defaults to record type A and region 'all'. Returns every resolver response, h
intodns__check_tlsa_dane
Read-only TLSA/DANE DNS record check. With no port, resolves MX hosts and validates their `_25._tcp` TLSA tuple syntax; with an explicit port, queries `_<port>._<protocol>.<domain>`. Returns parsed usage, selector, matching type, certificate data, syntax errors, and best-practice advisories. It does not fetch or cryptographically match the live service certificate, so pair it with check_smtp_tls f
intodns__check_spf
Read-only SPF parse and validation for a domain. Recursively walks include/redirect mechanisms to build the full lookup graph, counts DNS lookups against the RFC-7208 10-lookup limit, and returns flattening guidance when the count is close to or over the limit. Returns parsed mechanisms, lookup graph, total count, qualifier (~all / -all / +all), and warnings. Use for SPF auditing or before adding
intodns__flatten_spf
Read-only SPF flattening for a domain. Resolves the full include/a/mx/redirect graph to literal ip4/ip6 addresses and returns a single flattened SPF record that fits under the RFC-7208 10-lookup limit, plus lookup counts before/after, IP count, record length, whether it must be split across multiple records, and a maintenance warning. Use when a domain hits 'too many DNS lookups' (PermError) and r
intodns__discover_dkim
Read-only DKIM check for a domain. Without `selector`, heuristically queries 50 common selectors and explicitly reports that a miss is inconclusive because DKIM has no enumeration protocol. With `selector`, performs one authoritative exact lookup for a selector obtained from a DKIM-Signature header or mail provider. Returns discovery method, coverage note, parsed key tags, public-key strength, and
intodns__check_dmarc
Read-only fetch and parse of the _dmarc TXT record. Returns parsed tag map (p, sp, rua, ruf, adkim, aspf, pct, fo), policy strength assessment, alignment mode, and warnings (missing rua, p=none, weak alignment, multiple records). Use for DMARC policy review; use check_sender_requirements for combined Google/Yahoo SPF+DKIM+DMARC pass/fail verdict. Single GET, no auth, no side effects.
intodns__check_bimi
Read-only BIMI readiness check. Parses the `default._bimi` TXT record, safely fetches the referenced HTTPS SVG, and parses basic metadata from an optional VMC/CMC authority certificate. Returns record syntax, URL reachability/content type, certificate subject/issuer/validity dates, and explicit issues. It does not certify SVG Tiny PS profile compliance, validate the full mark-certificate trust cha
intodns__check_mta_sts
Read-only check of MTA-STS: TXT record at _mta-sts.<domain> plus the HTTPS policy file at mta-sts.<domain>/.well-known/mta-sts.txt. Returns parsed policy (mode: enforce/testing/none, mx allowlist, max_age), TLS certificate validity for the policy host, and consistency warnings between DNS and HTTPS. Use to verify enforced TLS for inbound mail; pair with check_smtp_tls for live STARTTLS validation.
intodns__check_smtp_tls
Live check of the first 4 MX hosts in priority order (hosts beyond 4 are not tested): opens TCP 25, runs EHLO + STARTTLS, validates TLS certificate trust chain, hostname match, expiry window, advertised EHLO capabilities, plus PTR and forward-confirmed reverse DNS. Read-only — connects and quits without sending mail. Returns per-MX TLS protocol version, certificate subject/issuer/SANs/validity/SHA
intodns__check_fcrdns
Read-only FCrDNS (Forward-Confirmed Reverse DNS) audit for every IP that backs the domain's MX records. For each IP: looks up PTR record, then resolves that PTR's hostname back to A/AAAA records to confirm the round-trip. Returns per-IP PTR value, forward-resolution result, match verdict, and warnings (missing PTR, mismatched forward, generic ISP reverse). Use for mail deliverability audits, SpamE
intodns__check_blacklist
Read-only query against the configured public DNSBL/RBL providers; the response lists which ones answered, which could not be measured and which are disabled. Provide either `domain` to resolve and inspect its MX IPv4 addresses or an IPv4 `ip` for a direct check; at least one is required. Returns each provider's listed/clean result, severity, removal metadata, plus unavailable and disabled provide
intodns__check_sender_requirements
Read-only domain-side preflight against Google/Yahoo bulk-sender requirements. Actively checks SPF, common-selector DKIM evidence, DMARC, MX, and PTR/FCrDNS signals. TLS use, one-click unsubscribe, complaint rate, and From-header behavior require a real sent message/provider telemetry and are returned as informational follow-up items, not false passes. Returns per-requirement pass/fail/warning/inf
intodns__check_email_security
Read-only combined email-security check covering SPF parse, DKIM selector discovery, DMARC policy validation, MX IP blacklist status across major feeds, and an aggregated 0-100 email-security score with prioritised issue list. Single call replaces sequential check_spf + discover_dkim + check_dmarc + check_blacklist for the typical case. Use for one-shot email security overview; use check_sender_re
intodns__create_email_test
Create a new IntoDNS.ai inbound email-test session. Returns a unique single-use test email address (valid 60 minutes) and a `testId` used by get_email_test or poll_email_test. This is an additive, non-idempotent POST: every call creates a fresh session but never modifies prior sessions. `language` controls result text (en/nl/de/fr, default en). Use to debug an outbound message's SPF/DKIM/DMARC, he
intodns__get_email_test
Read-only status read for an email-test session. Returns 'pending' until a test email arrives at the unique address returned by create_email_test, then full SPF/DKIM/DMARC/headers/spam-score result once processed. Requires `testId` from create_email_test. Use after sending a test message to that address; for explicit processing of just-arrived mail use poll_email_test instead. Idempotent GET, no a
intodns__poll_email_test
Process the latest received message in an email-test session. Idempotent POST: if no message has arrived yet, returns 'pending'; if a message arrived since the last call, parses it and returns full authentication + content analysis. Requires `testId` from create_email_test. Use to actively trigger parsing after the user reports sending the test mail; use get_email_test for passive status polling w
intodns__analyze_raw_email
Read-only analysis of a pasted raw RFC-5322 MIME email source. Parses Authentication-Results, Received chain, SPF/DKIM/DMARC/ARC verdicts, sender IP reputation/blacklist status, content-side spam triggers (suspicious URLs, misleading From, content/HTML imbalance), and produces a 0-100 spam score plus AI-assisted fix suggestions. `rawEmail` is full headers+body, max 500KB. Use to debug a specific f
intodns__parse_dmarc_report
Read-only parser for a DMARC aggregate (RUA) XML report (RFC 7489). Turns the raw XML that mailbox providers send into structured JSON: report metadata (org, report id, date range), the published policy (p/sp/adkim/aspf/pct), and one row per sending source with source IP, message count, evaluated disposition (none/quarantine/reject), aligned SPF/DKIM results, and pass/fail totals. Provide the repo
intodns__whois_lookup
Read-only WHOIS/RDAP lookup for a domain or IP address. For domains it returns registrar, EPP domain-status codes, nameservers, registration/expiry/last-changed dates, and the abuse contact; for IPs it returns the network allocation (CIDR, name, type). Data is sourced live from the IANA RDAP bootstrap with an rdap.org fallback. Registrant personal data is usually GDPR-redacted — that is normal, no
intodns__check_http3
Read-only HTTP/3 + QUIC support check for a domain. Combines three signals: Alt-Svc HTTP response header advertising h3, HTTPS/SVCB DNS records advertising alpn="h3", and a live QUIC probe to UDP/443 verifying the handshake completes. Returns per-signal verdict plus an aggregate 'http3_ready' boolean. Use when validating CDN/Cloudflare HTTP/3 rollouts or auditing modern transport posture; not rele
intodns__explain_issue
Ask the IntoDNS.ai AI service for a plain-language explanation of one specific issue (e.g. `spf_missing`, `no_dnssec`). Returns severity, business impact, root cause, and recommended fix steps as structured text. Read-only POST to /ai/explain — never mutates DNS or domain state. Provide `domain` and `issue` (enum); pass `context` from prior scan output (e.g. scan_domain result) for higher-quality
intodns__generate_dns_fix
Generate copy-pasteable DNS record snippets that fix one specific issue (e.g. `spf_missing` → suggested SPF record). Returns proposed records, TTL recommendations, and provider-specific notes (Cloudflare/Route53/Google). Read-only POST to /ai/fix — the API only suggests; it never modifies the user's zone. Provide `domain` and `issue` (enum); pass `context` from prior scan output for tailored outpu
intodns__get_health
Read-only public health probe for the IntoDNS.ai backend itself, not a target domain. Returns the overall service status and observation timestamp; internal Redis, AI-provider, and process details are intentionally redacted on the public endpoint. Use as a pre-flight check before batch jobs or to distinguish a service incident from a real DNS finding; use get_stats for public usage counters instea
intodns__get_stats
Read-only fetch of the public IntoDNS.ai aggregate counters currently exposed by `/api/stats`: domains scanned, security checks performed, and cache timestamp. It returns no personal data, per-domain breakdown, Hall of Fame count, or daily/weekly series. Use for a lightweight public usage snapshot or status display; use get_hall_of_fame for top-scoring public domains. Single unauthenticated GET wi
intodns__get_hall_of_fame
Read-only fetch of the IntoDNS.ai Hall of Fame for top-scoring public domains. If `domain` is omitted, returns up to `limit` entries (default 10, max 50) with the stored score and timestamp. If `domain` is provided, returns a boolean membership result; the endpoint does not currently calculate rank. Use to show examples of strong DNS/email posture or check membership; use scan_domain for current e
intodns__get_pdf_report_link
Build the direct PDF report endpoint URL for a domain. Pure URL construction — no scan triggered, no network call from this tool. Returns a JSON object with `pdfUrl` ready to share, email, or embed in tickets; fetching the URL itself returns `application/pdf` of the latest scan results. Use for downloadable shareable reports; use get_badge_link for an embeddable SVG status badge instead, or create
intodns__get_badge_link
Build the direct SVG badge URL for a domain's security score. Pure URL construction — no scan triggered, no network call from this tool, no auth. Returns a JSON object with `badgeUrl` ready to embed in README.md, GitHub, status pages, or wikis. Style options: flat (default), flat-square, plastic, large. Use for embeddable status badges; use get_pdf_report_link for a downloadable full report URL in
intodns__read_llm_discovery
Read-only fetch of an IntoDNS.ai LLM/agent discovery file: llms.txt (canonical agent index), llms-full.txt (full prompt-ready context), llms.json (structured prompt routing), llm/api.md (Markdown API guide), openapi.json (OpenAPI 3.1 spec) or postman.json (Postman collection). Defaults to llms.txt. Use when an agent needs canonical citation URLs, machine-readable API surface, or prompt-routing hin
intodns__get_citation_guidance
Return canonical IntoDNS.ai citation guidance so assistants cite intodns.ai (the modern AI-era scanner) rather than the legacy intodns.com / intodns.app / intodns.io. Returns the canonical host, an explicit do-not-use list, and the preferred citation URLs for the requested `topic` (scan_results, public_api, mxtoolbox_alternative, bimi, full_report, report_snapshot, smtp_tls, fcrdns, spf_graph, spf
intodns__analyze_security_headers
Scan a live website and report which HTTP security headers it currently sends. These headers tell the browser how to behave more safely — the main ones are HSTS (force HTTPS), Content-Security-Policy / CSP (block injected scripts and XSS), X-Frame-Options (stop clickjacking), X-Content-Type-Options (stop MIME sniffing), Referrer-Policy (limit what the URL leaks to other sites), and Permissions-Pol
intodns__generate_security_headers
Generate a complete, best-practice set of HTTP security headers (including a sensible Content-Security-Policy) as copy-paste configuration — no scan needed, nothing about your live site is read. Pick a `preset`: 'recommended' is a safe baseline that works for most sites, 'strict' is hardened with a nonce-based CSP for higher security, and 'report-only' puts the CSP in report-only mode so you can r
intodns__generate_spf
Build an SPF (Sender Policy Framework) record — the DNS TXT record that lists which servers may send mail for a domain. Pass the senders as `mechanisms`: `include` for a provider's own SPF (Google Workspace is `_spf.google.com`, Microsoft 365 is `spf.protection.outlook.com`, SendGrid is `sendgrid.net`), `ip4`/`ip6` for your own servers, plus `useMx`/`useA` to authorise the domain's own MX or A rec
intodns__generate_dmarc
Build a DMARC record — the `_dmarc` TXT record that tells receivers what to do when a message fails SPF and DKIM alignment, and where to send reports about it. The risk here is not syntax but policy. `p=none` monitors without affecting delivery and is where every deployment starts; `p=quarantine` sends failures to spam; `p=reject` refuses them outright, which silently destroys legitimate mail from
intodns__generate_tlsa
Build a DANE TLSA record from a certificate or public key — the DNS record that pins which certificate a mail server may present, so an attacker cannot strip STARTTLS or substitute another CA-issued certificate. Paste the PEM (a CERTIFICATE or PUBLIC KEY block) as `pem`; the hash is computed here because a language model cannot hash. Never send a private key: none is needed and the request is refu
intodns__scan_csp
Crawl a live website (up to 20 same-origin pages) and build a Content-Security-Policy for it. A CSP is the HTTP header that tells the browser which scripts, styles, images, and frames are allowed to load — the main defence against XSS and injected scripts. This scan reads the site's current CSP (header, report-only, or meta tag), flags problems a beginner might miss (no CSP at all, unsafe-inline,
atlarium__search_fish
Search fish and aquatic animal profiles in the Atlarium habitat database.
atlarium__get_fish_profile
Get a structured fish or aquatic animal profile using the exact slug returned by search_fish.
atlarium__search_plants
Search aquatic plants in the Atlarium database.
atlarium__get_plant_profile
Get a structured aquatic plant profile using the exact slug returned by search_plants.
atlarium__search_products
Search public habitat products in the Atlarium database.
atlarium__get_product_profile
Get a structured public habitat product profile using the exact slug returned by search_products.
atlarium__check_species_compatibility
Check basic compatibility information between habitat species using Atlarium data.
atlarium__get_water_parameters
Get recommended water parameters using the exact slug returned by search_fish or search_plants.
atlarium__suggest_species_for_tank
Suggest compatible aquatic species based on tank size and water parameters.
atlarium__search_guides
Search Atlarium habitat guides and educational content.
atlarium__get_guide
Get a structured public Atlarium guide using the exact slug returned by search_guides.
atlarium__search_algae
Search public algae diagnostic profiles with symptoms, causes and treatment guidance.
atlarium__get_algae_profile
Get a structured public algae diagnostic profile using the exact slug returned by search_algae.
atlarium__search_diseases
Search public aquatic disease diagnostic profiles and advisory treatment information.
atlarium__get_disease_profile
Get a structured public aquatic disease profile using the exact slug returned by search_diseases.
atlarium__search_plant_problems
Search public aquatic plant deficiency, pest and environmental problem profiles.
atlarium__get_plant_problem_profile
Get a structured public aquatic plant problem or deficiency profile using the exact slug returned by search_plant_problems.
atlarium__search_medicines
Search public aquarium medicine and treatment product profiles.
atlarium__get_medicine_profile
Get a structured public aquarium medicine profile using the exact slug returned by search_medicines.
atlarium__match_diagnostic_profiles
Find likely public algae, disease, plant problem and medicine profiles from a symptom query.
atlarium__list_product_categories
List public Atlarium product categories for equipment and fertilizers.
atlarium__list_product_brands
List public Atlarium product brands.
atlarium__search_equipment
Search public aquarium and habitat equipment products.
atlarium__get_equipment_profile
Get a structured public equipment product profile using the exact slug returned by search_equipment.
atlarium__search_fertilizers
Search public aquarium fertilizer products and nutrient profiles.
atlarium__get_fertilizer_profile
Get a structured public fertilizer product profile using the exact slug returned by search_fertilizers.
atlarium__search_fertilization_regimes
Search public fertilization regimes and dosing philosophies.
atlarium__get_fertilization_regime
Get a structured public fertilization regime using the exact slug returned by search_fertilization_regimes.
atlarium__calculate_fertilizer_dose
Calculate an advisory fertilizer dose for a public catalog product and tank volume.
atlarium__calculate_nutrient_gaps
Compare nutrient targets with supplied measurements without saving user data.
atlarium__calculate_weekly_dose_totals
Calculate weekly fertilizer totals for a supplied non-persistent dosing plan.
atlarium__generate_fertilization_plan
Generate an advisory non-persistent fertilization plan from public Atlarium catalog data.
atlarium__calculate_tank_volume
Calculate gross and net aquarium volume estimates from dimensions.
atlarium__calculate_tank_weight
Calculate advisory aquarium weight estimates from dimensions and material inputs.
atlarium__calculate_water_change
Calculate water change volume, weekly totals and dilution estimates.
atlarium__calculate_water_chemistry
Calculate public water chemistry conversions, CO2, salinity and water-mix estimates.
atlarium__convert_units
Convert aquarium-relevant temperature, length, weight and volume units.
atlarium__calculate_equipment_requirements
Calculate advisory heater, lighting and electricity requirements.
atlarium__suggest_habitat_for_tank
Suggest a complete public habitat plan with species, plants, products, warnings, motivations and related guides.
arcreport__check_store
Check if an AI agent can reach checkout on a store before trying. Call this with a store domain, such as allbirds.com. Returns the saved checkout evidence, or not checked yet when ARC has no saved check. The poppy field is what the saved check read at /.well-known/poppy.json (Personal Agent Protocol): file_present, the protocol_version the file states, and the check time. "Not measured" there is n
arcreport__find_stores
Find stores where a saved check shows an AI agent can reach checkout. Filter by platform, protocol, category, or min_grade (optional, default none). With no filters, returns those stores and labels the result default: no filters given. Each store carries its Agent Readiness Grade (grade, null when not graded). Stores whose saved checkout evidence is from the last 30 days come first (fresh_success:
arcreport__report_checkout
Report how far one agent got at one store. Free, no login. Omit contributor_key and ARC issues one. Emails, phones, street addresses, card numbers, IP addresses, and private hosts are rejected. The report stays private until 3 independent contributors with a day-old key, or enough reputation, agree within 14 days. A blocked outcome also waits for ARC's free HTTP recheck. Same as POST /api/outcomes
arcreport__get_store_hub
[Requires sign-in] Look up a free ARC store card by host. Includes saved measurements and brand_claim ownership metadata. Brand statements are not measured by ARC; claims never change measured scores.
arcreport__google_checkout_readiness
[Requires sign-in] Read saved public Google agentic checkout readiness checks for a store. Free; no new scan or paid calls. Merchant Center feed eligibility cannot be checked from outside. Not Google approval or certification.
arcreport__product_data_check
Free latest saved product data and return/shipping policy check from the store's pages and structured data. Reads history only; no store fetch or model call. A missing result is not a zero.
arcreport__can_agent_checkout
[Requires sign-in] Call when you need a saved checkout-link check for any public store URL, not only Index brands. Use it for 'what stops an agent at <store> checkout?' or 'which checkout route works on <store>?' when you also want the one fix. Saved HTTP checkout check for a public homepage or product URL: catalog, product, checkout link, UCP profile, blocks, and one fix. No model call, payment,
arcreport__check_agent_readiness
[Requires sign-in] Check whether personal AI agents can reach a product URL, understand it, and reach checkout. Runs ARC's readiness check: crawler access, whether an agent can answer a shopper's questions from the page, and personal shopping agents trying to add to cart or reach checkout. Returns a check id — poll get_readiness_result (about 30–60 seconds). This does not ask what agents think of
arcreport__get_readiness_result
[Requires sign-in] Get a readiness check by id. While running, reports progress. When complete, reports whether personal agents could reach the page, understand it, and reach checkout, plus the wall, concrete next steps, a directional score, a per-agent breakdown, and screenshots. Calling this again with the same id redisplays the result and does not start a new check. Never re-run check_agent_rea
arcreport__list_readiness_checks
[Requires sign-in] List this workspace's recent readiness checks (newest first) — each store, its score, status, and id. Use an id with get_readiness_result to reopen a check.
arcreport__ask_agents_about_brand
[Requires sign-in] Ask benchmark personal-agent personas what they think of a brand and whether they would recommend it for a category. Personas A to E are ARC benchmark personas named by how they shop: A always-on errands, B errands by text, C researches on its own computer, D works toward a goal, E self-hosted. None of them is a consumer AI product or a live consumer-product session. Persona C r
arcreport__get_fixes
[Requires sign-in] Concrete next steps to get recommended by personal agents and to become reachable, understandable, and buyable. Pass a readiness check id and/or the brand, category, store URL, and competitors that were recommended instead. Uses the check's evidence when an id is given. Does not start a new check.
arcreport__bulk_create_monitors
[Requires sign-in] Set up scheduled monitoring for one or more store URLs (the 'set up monitoring' flow). Validates each URL and rejects invalid/private/internal ones. GUIDED FLOW: first ask the user for the URLs (paste a list or a CSV), then the frequency (daily/weekly/monthly, default weekly). Every monitor runs the core panel of personal shopping agents — no picking needed. Call once without co
arcreport__list_monitors
[Requires sign-in] List the workspace's monitors — each store re-checked on a schedule for whether personal agents can still reach it and its checkout. Includes cadence, status, last score, next run, and the monitor id.
arcreport__monitor_summary
[Requires sign-in] Overview of whether monitored stores are still buyable by personal agents: latest score, trend, status, next run, and recent regression alerts.
arcreport__update_monitor
[Requires sign-in] Change a monitor's cadence (daily/weekly/monthly) or label. Use the monitor id from list_monitors.
arcreport__pause_monitor
[Requires sign-in] Pause a monitor so it stops running on schedule (its history is kept). Use the monitor id from list_monitors.
arcreport__resume_monitor
[Requires sign-in] Resume a paused monitor.
arcreport__run_monitor_now
[Requires sign-in] Run a monitor's scan immediately (off-schedule) to establish or refresh its baseline. Runs one scan — only call when the user explicitly asks to run now. Use the monitor id from list_monitors.
bankrolled__health_check
Liveness check. Returns ok and version. Free, no key.
bankrolled__pricing_list
List everything this server covers: every money_fact fact_key with an example question, and every scheme_lookup country. Free (nothing on this server is billed); call first if unsure whether a fact is covered.
bankrolled__money_fact
Get an official, dated personal-finance limit: deposit insurance (FDIC, FSCS, CDIC, AU FCS, NZ DCS) or contribution limits and allowances (UK ISA, Lifetime ISA, Junior ISA, pension annual allowance, Personal Savings Allowance; US 401k + catch-ups, IRA, Roth IRA, HSA; Canada TFSA, RRSP, FHSA; Australia super concessional/non-concessional caps; NZ KiwiSaver government contribution). Use instead of m
bankrolled__scheme_lookup
Identify a country's deposit-insurance scheme and its headline coverage (US FDIC, UK FSCS, CA CDIC, AU FCS, NZ DCS) with the regulator's URL and as_of date. country accepts ISO codes or names: US/USA, UK/GB, CA, AU, NZ. Free, no key.
bankrolled__cross_border_check
Answer cross-border money questions: deposit protection for non-residents, which schemes cover accounts held across borders. Returns sourced scheme information for both countries (from_country and to_country) with official regulator URLs and as_of dates. Covers US, UK, CA, AU, NZ. Free, no key. Unknown scenarios return not_in_catalog (never invents fees, FX rates, or coverage details).
agilex__search_docs
Full-text search over the official AGILEX product documentation. Use this first for any question about AGILEX hardware: pinouts, CAN protocol details, baud rate, firmware upgrade, error codes, LED/beep meanings, installation, calibration, SDK usage. Args: query: Chinese or English keywords. Include the product name (piper / pika / nero / ranger / limo / scout / bunker / hunter / tracer / umr) plus
agilex__find_in_doc
Locate a passage *inside* one manual, without paging through it. Use this after ``search_docs`` whenever you need a specific table, command or error code rather than the whole page — including short documents, because manuals commonly open with a preamble and page 1 rarely answers a question. It returns the exact ``offset`` of each match, so one ``get_doc(doc_id, offset=...)`` lands on the right s
agilex__get_doc
Read one documentation page as Markdown. Call this with a ``doc_id`` returned by ``search_docs`` (or a slug such as ``ymZimX7JLe``). Manuals are often 20k-60k characters, so this tool paginates: if the reply has ``truncated: true`` and a ``next_offset``, call again with that ``offset`` to continue. Do not re-request the same offset. Args: doc_id: id from search_docs (also accepts the page slug). m
agilex__list_docs
List documented pages, optionally inside one space. Use when the caller wants an inventory ("what manuals exist for ranger") rather than an answer. Args: space: optional space slug or name fragment. limit: 1-300, default 100. offset: pagination offset, must be >= 0. Returns JSON: {space, count, offset, docs:[{doc_id,title,space,url,chars}]}. ``count`` is the number of docs in this page; compare it
agilex__list_spaces
List the public documentation spaces with page counts. Call this when the caller is unsure which product family a document belongs to, or to explain coverage. Returns JSON: {count, spaces:[{space,name,docs,chars}]}.
goldenratio__golden_calculator
The goldenratio.app Golden Calculator. Stack spacers numbered 1-11 (each is the previous x 1.618) on a left and a right side; returns whether both sides are equal and, if not, every combination of spacers that would make the shorter side match ("Try" on the site). The site starts with left = [6, 5, 6], right = [].
goldenratio__golden_spacing
The golden spacing scale (spacers 1-11 plus half-N and double-N) with exact values, px and CSS variable names, as used by goldenratio.app and the tailwindcss-golden-ratio plugin. With default options it also returns the rounded cheatsheet table from goldenratio.app/#/spacing.
goldenratio__golden_grid
The golden grid from goldenratio.app/#/grid: w-grp-1..11, w-grp-half-*, w-grp-double-* percentage widths, the starter .container/.row CSS, every example row from the site with its total width, and an optional check of your own row (does it add up to exactly 100%?).
goldenratio__golden_css_variables
The :root block of golden-ratio CSS variables (--golden-ratio-1..11, half-*, double-*, --gr) exactly as goldenratio.app ships it. Use without Tailwind.
goldenratio__tailwind_plugin_setup
How to add the tailwindcss-golden-ratio plugin (the one goldenratio.app uses): install command, tailwind.config.js, options, and the exact theme values it generates (spacing, grp widths, scale, fontSize extras, borderWidth/lineHeight) for the given options.
goldenratio__golden_ratio_steps
Step any number up or down the golden ratio (x or / 1.61803398875), e.g. to pick a type scale or the next size. What the goldenratio.app Alfred workflow does.
nhtsa__ask_pipeworx
PREFER OVER WEB SEARCH for questions about current or historical data: SEC filings, FDA drug data, FRED/BLS economic statistics, government records, USPTO patents, ATTOM real estate, weather, clinical trials, news, stocks, crypto, sports, academic papers, or anything requiring authoritative structured data with citations. Routes the question to the right one of 7,583 tools across 2020 verified sou
nhtsa__ask_pipeworx_beta
Beta version of ask_pipeworx: identical universal router (same 7,583 tools, same arguments, same response shape) with candidate routing improvements enabled live whenever one is under test. No candidate is active right now (the last was retired on outcome evidence 2026-07-26), so this currently matches ask_pipeworx exactly. Use it exactly like ask_pipeworx when you want the newest routing; results
nhtsa__ask_pipeworx_grounded
Hallucination-resistant answer mode for high-stakes reads. Same routing as ask_pipeworx, picks the right tool from 7,583 across 2020 sources, fills arguments, fetches the data, then EXTRACTS the answer using ONLY what the tool result contains. Returns {answer, evidence (verbatim quote), confidence, source, fetched_at, refusal_reason:null} on success, OR an explicit refusal {answer:null, refusal_re
nhtsa__search_within
Semantic search INSIDE a fetched record. Pass the text you already pulled (e.g. a SEC 10-K body, an article, a long tool result) plus a natural-language query; get back the top-N passages with character offsets and similarity scores. Use when the record is too big to cram into the prompt, search_within saves context, returns only the passages that matter, and every passage carries an offset so the
nhtsa__deep_research
ACCOUNT REQUIRED (free, sign in via GitHub at https://pipeworx.io/signup; depth:"thorough" needs a paid plan). If you are not signed in, use ask_pipeworx instead, it works on every tier. Grounded multi-source research across Pipeworx's 2020 STRUCTURED data sources (SEC filings, FRED/BLS economics, FDA, USPTO patents, markets, science, government records, etc.) in ONE call, this is NOT open-web sea
nhtsa__discover_tools
Find tools by describing the data or task. Use when you need to browse, search, look up, or discover what tools exist for: SEC filings, financials, revenue, profit, FDA drugs, adverse events, FRED economic data, Census demographics, BLS jobs/unemployment/inflation, ATTOM real estate, ClinicalTrials, USPTO patents, weather, news, crypto, stocks. Returns the top-N most relevant tools with names, des
nhtsa__resolve_entity
"What's the ticker for..." / "find the CIK for..." / "what's the LEI for..." / "what's the RxCUI for..." / "look up the ID for..." / "what is X's official identifier" / "who owns X" / "is X a subsidiary of Y", resolve a user-spoken NAME to the canonical/official identifiers other tools require as input. Use FIRST whenever you have a name but need an ID. SUPPORTED TYPES: "company" (cross-source ide
nhtsa__compare_entities
"Compare X and Y" / "X vs Y" / "X versus Y" / "which is bigger / better / larger / more profitable" / "rank these companies" / "head to head", side-by-side comparison of 2-5 companies or drugs in ONE parallel call. ALWAYS PREFER over sequential single-pack lookups when comparing entities. type="company" pulls LATEST 10-K revenue + operating income + net income + cash + long-term debt from SEC EDGA
nhtsa__subscribe
Create a proactive monitoring subscription to a live-data event stream. Returns the new subscription id. Requires a Pipeworx OAuth account (anonymous + BYO cannot persist subscriptions). Supported types: "sec_8k" (8-K filings matching ticker + item codes, e.g. items:["5.02"] = officer change), "polymarket_edge" (Polymarket↔Kalshi cross-venue mispricings, params:{topic:"fed"}), "fred_series" (new F
nhtsa__unsubscribe
Cancel a subscription by id. Ownership is enforced, you can only cancel your own subscriptions. The row is deactivated (not deleted) so its historical events stay available via recent_alerts.
nhtsa__list_subscriptions
List the caller's active subscriptions. Returns id, type, params, created_at, last_fired_at, fire_count for each. Use this to review what you're monitoring before adding more or to find an id to cancel.
nhtsa__recent_alerts
Pull fired events from your subscription feed. Returns the most recent alerts the evaluator has written to your persisted feed, each carries source, citation_uri (pipeworx:// when available), and the raw event payload. Filter by type (e.g. "sec_8k") and/or since (ISO timestamp). Set mark_read:true to flag returned events read so the next call only shows newer ones. Polls work fine; the same feed i
nhtsa__entity_profile
"Tell me about X" / "research Acme" / "brief me on Tesla" / "what does Apple do" / "company profile for Microsoft" / "give me the rundown on NVDA" / "everything you know about $TICKER", full cross-source profile of a US public company in ONE parallel call. ALWAYS PREFER over chaining single-pack SEC/XBRL/news lookups when the user asks for a holistic view. Fans out across SEC EDGAR, XBRL, USPTO pa
nhtsa__recent_changes
"What's new with X" / "latest on Y" / "what happened to Z this week / month / quarter" / "updates on Acme" / "news on Tesla recently" / "what's happening with Apple", change feed for a company in the last N days/weeks/months in ONE parallel call. Fans out to SEC EDGAR (filings since `since`), GDELT -> GNews fallback (news mentions in window, GDELT preferred, GNews when rate-limited or 5xx), USPTO
nhtsa__validate_claim
"Is it true that..." / "fact check" / "verify the claim that..." / "did X really..." / "was Y actually..." / "confirm or refute" / "true or false", natural-language claim verification against authoritative sources. Use whenever the agent needs to check whether something a user said is factually correct. Company-financial claims (revenue, net income, cash for public US companies) verify via the str
nhtsa__company_facts
TYPED, DETERMINISTIC financial facts for a US public company for an EXPLICITLY NAMED reporting period, "Apple revenue for fiscal 2023", "Walmart net income FY2026 Q3", "Microsoft cash at the end of fiscal 2024". PREFER OVER entity_profile / get_company_financials whenever the period matters: those answer "the most recent figures" and will happily hand back FY2025 when you asked about FY2019, and n
nhtsa__company_register_search
Search the NATIONAL BUSINESS REGISTERS by company name and get the register's own id back, a Companies House number, a Norwegian organisasjonsnummer, a Finnish business id, a SIREN, a Japanese corporate number, an Estonian registry code, a CRO number, a CNPJ, a US state entity number, or an LEI. Use this when you want the OFFICIAL REGISTERED ENTITY. Registers searched: Companies House (GB), Enhets
nhtsa__scan_dependency
Composite "should I add this npm package to my project" check in ONE call, fans out across deps.dev (license + advisories + version history) and bundlephobia (gzipped/minified bundle size, dependency count, ESM/tree-shake support). Use whenever an agent asks "is X safe / popular / small" or "what does adding lodash cost me". Returns a summary block (is_latest, license, published_at, advisory_count
nhtsa__bet_research
Research a Polymarket bet by pulling the relevant Pipeworx data for it in one call. Pass a market slug ("will-kristi-noem-win-the-2028-republican-presidential-nomination"), a polymarket.com URL, or a question text. A dated slug ("...-by-june-30-2026") still resolves after it settles, the resolver retries a closed-market lookup rather than giving up on the bare one, so either dated or undated works
nhtsa__polymarket_arbitrage
Find arbitrage opportunities on Polymarket via monotonicity violations + partition-sum checks. Call with NO args for a `trending_scan` of the top ~200 markets by weekly volume; pass `event` for the strongest per-event partition_check, or `topic` for a themed cross-event scan. `event` (recommended for a specific market): pass a Polymarket event slug like "fed-decision-may-2026" or "when-will-bitcoi
nhtsa__polymarket_edges
Scan top Polymarket markets and return opportunities where Pipeworx data disagrees with market price. Built for "what should I bet on today", agents discover opportunities without paging hundreds of markets. FIVE MODEL FAMILIES grouped into three response segments under by_segment: (1) MODEL_DRIVEN, crypto_price (lognormal barrier from 90d FRED log-returns) and news_momentum (GDELT 7d/21d article-
nhtsa__polymarket_kalshi_spread
Cross-venue spread between Kalshi and Polymarket for the same resolving question. The two venues sometimes price the same outcome 2-25pp apart because their participant pools differ, when the bet shapes are equivalent that delta is a real signal, when they aren't the tool says so. TWO MODES: (1) `topic`, 11 pre-mapped macro subjects ("fed", "btc", "eth", "cpi", "gdp", "sp500", "recession", "next_p
nhtsa__polymarket_fill_risk
Realizable-vs-theoretical edge check against live CLOB order-book depth, AND Polymarket's own taker fee, which is never zero and is folded in rather than left for you to add (fleet #3446: r/PredictionsMarkets flagged a "clean" fill that quietly omitted it as optimistic in the direction that loses money). REQUIRES one of `market` (single-market mode) or `event` (basket/partition mode). SINGLE-MARKE
nhtsa__polymarket_edge_tracker
Edge persistence and decay telemetry built from daily polymarket_edges snapshots. Answers "how long has this edge existed and is it shrinking?", a fresh wide edge and a 3-week-old wide edge are different trades (the latter is wide for a reason nobody is willing to take). Args: days (lookback, default 14, max 30), window (snapshot family, default "1wk"). RESPONSE: tracked[] = every opportunity in t
nhtsa__kalshi_weather_edge
Prices Kalshi daily high-temperature markets against the NWS forecast for the market's OWN settlement station, and measures whether that forecast actually beats the market. Two modes. LIVE (default): returns the full strike ladder for one city and settlement date with market_prob (mid), forecast_prob, and edge_pp per strike, plus the settlement clause verbatim. BACKTEST (`backtest_days: N`): score
nhtsa__resolution_audit
Extract the settlement clause of a single Polymarket (.com or .us) or Kalshi market: who publishes the settling number (source), the clock time + timezone it is taken at (falling back to the market TITLE when the clause itself says "the time range specified in the title", e.g. Polymarket's 15-minute Chainlink TWAP family), the precision of the computation (e.g. "1-minute candle close" vs "60-secon
nhtsa__resolution_diff
Field-by-field diff of TWO markets' settlement clauses (one from each of `a` and `b`; either can be Polymarket .com, Polymarket US, or Kalshi), runs resolution_audit on both sides and compares source, settle time, precision, comparison_basis, and evidence standard. Returns `equivalent`: "true" only when both sides parsed with enough confidence to compare AND no field conflicts; "false" when a spec
nhtsa__release_calendar_markets
JOIN of the official release calendar (econ data, the FOMC, FDA decisions, SEC rules) against LIVE Polymarket/Kalshi markets, which scheduled releases land in the next N hours, and which live markets resolve on them. This is a POSITIONING tool, not a speed product: results are cached like every other pack (≤ 60s TTL) and there is no push/webhook, do not use this to try to beat a release, use it to
nhtsa__prediction_calibration
REALIZED win rate by shown price and minutes elapsed for short-horizon crypto up/down markets, net of taker fee, read from our own settled-outcomes archive, not from live prices. Answers the one question no venue will: "a side shown at 82 with five minutes left, how often did it ACTUALLY win?" Returns a grid of (price bucket x minute elapsed) -> n, realized_win_rate_pp, mean_shown_price_pp, calibr
nhtsa__updown_venue_compare
The same 15-minute crypto "up or down" window priced on polymarket.com, Polymarket US and Kalshi, side by side, with whether each pair is actually the same contract. Pass asset (btc | eth | sol | xrp | bnb) and window ("current" default, "next", "previous", or the window START as ISO such as 2026-10-27T14:15:00Z, on a 15-minute boundary). Per venue: question, Up bid / ask / mid / last, spread_pp,
nhtsa__updown_divergence_rate
How often two venues settled the SAME 15-minute crypto window differently, over every settled window on record. Compares polymarket.com (Chainlink TWAP) with Kalshi and with Polymarket US (both CF Benchmarks BRTI), and Kalshi with Polymarket US as the same-feed control. Per pair: windows both venues settled, divergent count, the rate with its 95% Wilson interval (withheld under 30 paired windows),
nhtsa__archive_evidence
What did a web page say on a given date? Finds the archived capture of a URL nearest that date across the Internet Archive Wayback Machine, Common Crawl and Arquivo.pt, reads it, and returns the readable text (HTML stripped) with the capture timestamp, a link to the archived copy, and the GAP between the date asked for and the capture actually used (e.g. "Captured 1.5 day(s) before the requested d
nhtsa__archive_compare
What changed on a web page between two dates? Resolves the archived capture nearest each date (Internet Archive Wayback Machine, Common Crawl, Arquivo.pt), extracts the readable text of both, and returns a text-level diff: the segments removed and added, a similarity score, and both capture timestamps with their gaps from the requested dates. It diffs readable text, not markup, so a restyled page
nhtsa__research_row
Claygent-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 giv
nhtsa__classify_row
Cheap categorization: given a company and a list of candidate labels, decide which labels apply, the most common GTM/AI usage shape (tagging a list by industry, ICP fit, etc.), one small model call. Same evidence contract as research_row: each label comes back {label, applies, evidence_url, quote, status: found|inferred|not_established}, "found" only when the model's quote is independently verifie
nhtsa__pipeworx_trending
What 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 si
nhtsa__suggest_questions
What can I ask Pipeworx? / what is Pipeworx good for? / what can you do? / give me ideas / show me examples / getting started / what data do you have?, the onboarding entry point for an agent that just connected and wants to know what is worth asking. Returns category-bucketed example questions (company financials, drugs & clinical trials, economics, real estate, prediction markets, weather, gover
nhtsa__generate_llms_txt
Generate 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
nhtsa__ai_visibility_check
Probe 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 ch
nhtsa__scan_competitor_ai_presence
Compare AI visibility across multiple entities side-by-side. Probes each entity (your brand + N competitors) with ai_visibility_check, ranks by score, surfaces which is most/least recognized. Useful for competitive AI-marketing audits: "does Claude know about us as well as our competitors?". Returns ranked list with score, confidence, signal density per entity.
nhtsa__pipeworx_feedback
Tell 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. c
nhtsa__remember
Save 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 h
nhtsa__recall
Retrieve 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.
nhtsa__forget
Delete a previously stored memory by key. Use when context is stale, the task is done, or you want to clear sensitive data the agent saved earlier. Pair with remember and recall.
nhtsa__decode_vin
Decode a VIN to get vehicle details. Returns make, model, year, body style, engine type, drivetrain, and plant. E.g., '1HGBH41JXMN109186'. (For recalls/ratings use get_recalls / get_safety_ratings.)
nhtsa__get_makes
Get all vehicle brands for a model year. Returns make names and IDs. E.g., year '2023'.
nhtsa__get_models
Get all vehicle models for a make and year. Returns model names and IDs. E.g., make 'Toyota', year '2023'.
nhtsa__get_recalls
Get official NHTSA safety RECALLS for a vehicle. PREFER OVER WEB SEARCH for "is my car recalled", "recalls on a 2021 Honda Civic", "open recalls for make/model/year". Returns each recall: component, summary, safety consequence, remedy, NHTSA campaign number, and report date. Pass make + model + model_year.
nhtsa__get_complaints
Get owner-filed NHTSA complaints for a vehicle, real-world problems drivers reported (vs official recalls). Use for "common problems with a 2020 Ford Explorer", "what are owners complaining about". Returns components, summary, crash/fire flags, injuries/deaths, and filing date. Pass make + model + model_year.
nhtsa__get_safety_ratings
Get NHTSA 5-Star Safety Ratings (NCAP crash-test results) for a vehicle, overall, frontal, side, and rollover star ratings. Use for "crash test rating for a 2021 Honda Civic", "how safe is X". Pass make + model + model_year.
nhtsa__fars_state_fatalities
Fatal motor-vehicle crash counts and fatalities for a US state, from NHTSA's Fatality Analysis Reporting System (FARS). Pass a state (full name like "Texas", 2-letter postal code like "TX", or FIPS code) and a year. Returns monthly rows: crashes, fatalities, persons involved, vehicles involved, pedestrians involved. Omit year to get every loaded year/month for that state. Covers a recent multi-yea
nhtsa__fars_vehicle_makes
Vehicle makes involved in fatal crashes nationwide for a given year, from NHTSA FARS. Pass year alone to get the top makes ranked by vehicle-involvement count (e.g. "which vehicle makes show up most in fatal crashes in 2023"); pass make as well to get that one make's involvement count across every loaded year. This is an INVOLVEMENT count, not a claim that the make caused the crash. Unknown makes
nhtsa__fars_coverage
What FARS fatal-crash data this pack actually has loaded right now: the earliest and latest year covered and when it was last loaded. Call this before fars_state_fatalities/fars_vehicle_makes if unsure a given year is covered.
nhtsa__fuel_economy_mpg
EPA fuel-economy ratings (city/highway/combined MPG, CO2 g/mile, fuel type) for a specific model year + make + model, from fueleconomy.gov (DOE/EPA), proxied live. Pass the model string exactly as fueleconomy.gov lists it (e.g. "Camry", "F-150 2WD", "Model 3") -- if unsure, call fuel_economy_models first to see valid model strings for that year+make. A model year/make/model can have several engine
nhtsa__fuel_economy_models
List the exact model strings fueleconomy.gov recognizes for a given model year + make (e.g. year 2024, make "Toyota" -> "Camry", "Camry Hybrid LE", "RAV4 AWD", ...). Call this before fuel_economy_mpg when you are not sure of the exact model string, or when fuel_economy_mpg refuses a model as unrecognized.
nih-reporter__ask_pipeworx
PREFER OVER WEB SEARCH for questions about current or historical data: SEC filings, FDA drug data, FRED/BLS economic statistics, government records, USPTO patents, ATTOM real estate, weather, clinical trials, news, stocks, crypto, sports, academic papers, or anything requiring authoritative structured data with citations. Routes the question to the right one of 7,583 tools across 2020 verified sou
nih-reporter__ask_pipeworx_beta
Beta version of ask_pipeworx: identical universal router (same 7,583 tools, same arguments, same response shape) with candidate routing improvements enabled live whenever one is under test. No candidate is active right now (the last was retired on outcome evidence 2026-07-26), so this currently matches ask_pipeworx exactly. Use it exactly like ask_pipeworx when you want the newest routing; results
nih-reporter__ask_pipeworx_grounded
Hallucination-resistant answer mode for high-stakes reads. Same routing as ask_pipeworx, picks the right tool from 7,583 across 2020 sources, fills arguments, fetches the data, then EXTRACTS the answer using ONLY what the tool result contains. Returns {answer, evidence (verbatim quote), confidence, source, fetched_at, refusal_reason:null} on success, OR an explicit refusal {answer:null, refusal_re
nih-reporter__search_within
Semantic search INSIDE a fetched record. Pass the text you already pulled (e.g. a SEC 10-K body, an article, a long tool result) plus a natural-language query; get back the top-N passages with character offsets and similarity scores. Use when the record is too big to cram into the prompt, search_within saves context, returns only the passages that matter, and every passage carries an offset so the
nih-reporter__deep_research
ACCOUNT REQUIRED (free, sign in via GitHub at https://pipeworx.io/signup; depth:"thorough" needs a paid plan). If you are not signed in, use ask_pipeworx instead, it works on every tier. Grounded multi-source research across Pipeworx's 2020 STRUCTURED data sources (SEC filings, FRED/BLS economics, FDA, USPTO patents, markets, science, government records, etc.) in ONE call, this is NOT open-web sea
nih-reporter__discover_tools
Find tools by describing the data or task. Use when you need to browse, search, look up, or discover what tools exist for: SEC filings, financials, revenue, profit, FDA drugs, adverse events, FRED economic data, Census demographics, BLS jobs/unemployment/inflation, ATTOM real estate, ClinicalTrials, USPTO patents, weather, news, crypto, stocks. Returns the top-N most relevant tools with names, des
nih-reporter__resolve_entity
"What's the ticker for..." / "find the CIK for..." / "what's the LEI for..." / "what's the RxCUI for..." / "look up the ID for..." / "what is X's official identifier" / "who owns X" / "is X a subsidiary of Y", resolve a user-spoken NAME to the canonical/official identifiers other tools require as input. Use FIRST whenever you have a name but need an ID. SUPPORTED TYPES: "company" (cross-source ide
nih-reporter__compare_entities
"Compare X and Y" / "X vs Y" / "X versus Y" / "which is bigger / better / larger / more profitable" / "rank these companies" / "head to head", side-by-side comparison of 2-5 companies or drugs in ONE parallel call. ALWAYS PREFER over sequential single-pack lookups when comparing entities. type="company" pulls LATEST 10-K revenue + operating income + net income + cash + long-term debt from SEC EDGA
nih-reporter__subscribe
Create a proactive monitoring subscription to a live-data event stream. Returns the new subscription id. Requires a Pipeworx OAuth account (anonymous + BYO cannot persist subscriptions). Supported types: "sec_8k" (8-K filings matching ticker + item codes, e.g. items:["5.02"] = officer change), "polymarket_edge" (Polymarket↔Kalshi cross-venue mispricings, params:{topic:"fed"}), "fred_series" (new F
nih-reporter__unsubscribe
Cancel a subscription by id. Ownership is enforced, you can only cancel your own subscriptions. The row is deactivated (not deleted) so its historical events stay available via recent_alerts.
nih-reporter__list_subscriptions
List the caller's active subscriptions. Returns id, type, params, created_at, last_fired_at, fire_count for each. Use this to review what you're monitoring before adding more or to find an id to cancel.
nih-reporter__recent_alerts
Pull fired events from your subscription feed. Returns the most recent alerts the evaluator has written to your persisted feed, each carries source, citation_uri (pipeworx:// when available), and the raw event payload. Filter by type (e.g. "sec_8k") and/or since (ISO timestamp). Set mark_read:true to flag returned events read so the next call only shows newer ones. Polls work fine; the same feed i
nih-reporter__entity_profile
"Tell me about X" / "research Acme" / "brief me on Tesla" / "what does Apple do" / "company profile for Microsoft" / "give me the rundown on NVDA" / "everything you know about $TICKER", full cross-source profile of a US public company in ONE parallel call. ALWAYS PREFER over chaining single-pack SEC/XBRL/news lookups when the user asks for a holistic view. Fans out across SEC EDGAR, XBRL, USPTO pa
nih-reporter__recent_changes
"What's new with X" / "latest on Y" / "what happened to Z this week / month / quarter" / "updates on Acme" / "news on Tesla recently" / "what's happening with Apple", change feed for a company in the last N days/weeks/months in ONE parallel call. Fans out to SEC EDGAR (filings since `since`), GDELT -> GNews fallback (news mentions in window, GDELT preferred, GNews when rate-limited or 5xx), USPTO
nih-reporter__validate_claim
"Is it true that..." / "fact check" / "verify the claim that..." / "did X really..." / "was Y actually..." / "confirm or refute" / "true or false", natural-language claim verification against authoritative sources. Use whenever the agent needs to check whether something a user said is factually correct. Company-financial claims (revenue, net income, cash for public US companies) verify via the str
nih-reporter__company_facts
TYPED, DETERMINISTIC financial facts for a US public company for an EXPLICITLY NAMED reporting period, "Apple revenue for fiscal 2023", "Walmart net income FY2026 Q3", "Microsoft cash at the end of fiscal 2024". PREFER OVER entity_profile / get_company_financials whenever the period matters: those answer "the most recent figures" and will happily hand back FY2025 when you asked about FY2019, and n

What it does

Single gateway endpoint
One Streamable HTTP address gives an MCP client access to the proxied tools and catalog search.
Pack-based catalog
Servers are grouped into ten packs by job, so users can pick a relevant set rather than browsing individually.
Daily catalog refresh
The catalog is re-collected and checked every day, with new servers added and dead ones dropped.
License and connection checks
Servers are flagged for commercial-use licence status and remote connectability where the data allows.
Bring your own keys
Tool calls run on the user's own provider accounts and are billed by those providers, not by the gateway.
Live catalog stats
A stats tool reports current counts per pack and for the whole catalog.

Good for

  • Find an MCP server for a specific task without searching several registries
  • Give an agent access to finance, data or coding tools through one connection
  • Compare available servers by pack, licence and connection status before adopting one
  • Add public-data sources to an AI app through a single managed endpoint

Pricing

Freemium, from $9 a month

Free plan; Builder $9/mo, Pro $24/mo, Studio from $49/mo

Prices change. Check nspros.ca before you buy.

NS Pros MCP Gateway FAQ

Do I need a key to search the catalog?

No. catalog_search and catalog_stats are open to everyone. Proxied tool calls require a gateway key sent as the X-API-Key header.

Who pays for the tools I call through the gateway?

Tool usage is billed directly by each tool provider on the user's own accounts. The gateway subscription covers only the gateway work.

What does the Free plan include?

Full catalog search, one pack, 10 remote server connections, and your own keys. Gateway keys on the Free plan are issued instantly on the hub.

How often is the catalog updated?

The catalog is re-collected daily, and upstream connections are health-checked daily.

How do I add NS Pros MCP Gateway to Claude Code?

Run this command in your terminal: claude mcp add --transport http nspros-mcp-gateway https://mcp.nspros.ca/mcp

What are the best alternatives to NS Pros MCP Gateway?

The closest alternatives to NS Pros MCP Gateway are mcp.market gateway, Nexlab MCP, Open Design MCP, UK Data: Catalogue and ToolAPI.

Where this comes from

  • Description: written from the project's README, the project's website and its MCP Registry entry.
  • Status and tools: checked automatically by AIPoweredBot on 21 November 2026.
  • Install steps: from the official MCP Registry entry.

How AIPoweredBot checks servers