NetActuate MCP Server

Finds deployable apps in NetActuate's marketplace (netactuate.com/marketplace): streaming servers, transcoders, WebRTC, CDN and media software that deploys on NetActuate's edge, open source and from partners such as Wowza, Broadpeak and NETINT. Filter by any mix of words, vendor, category, licensing and freeDemo; with no filter it lists them all, featured first, `limit` at a time. A vendor or category it does not know is explained in a note naming the valid ones. Each result gives the slug, name, vendor (null for open source), tagline, licensing (free, byol, trial), vpu when it needs NETINT VPU hardware, freeDemo with its terms, sizing (minimum and recommended vCPU, RAM and disk) and its URL; count is the full number of matches. Use for 'what can I deploy on NetActuate', 'is there an SRT gateway', 'which apps can I try for free' or 'what does NetActuate offer from Wowza'. One listing in full: get_marketplace_app; the vendors: list_marketplace_partners. Listings do not say where they run; for an app and a place together, use search_netactuate ('Wowza Africa').

Returns one marketplace listing in full: what the app does, its features and use cases, the vendor and its partner page, licensing and the license terms in the listing's own words, support tier, type and deployedBy (an image NetActuate deploys, or an integration the vendor delivers), vpu, freeDemo with the page's note, and the vendor's other listings. Most listings also carry setupGuide from their docs page: sizing (minimum and recommended vCPU, RAM, disk), the fields asked at deploy, how to reach the app afterwards, and its FAQ; get_netactuate_doc returns that page (docsUrl) in full. Accepts a slug or URL from find_marketplace_apps or search_netactuate, or a name such as 'Wowza Streaming Engine'; a name matching several listings returns up to ten candidates rather than a guess. It does not say where the app runs: for locations, list_data_centers.

Lists the software vendors with listings in NetActuate's marketplace, such as Wowza, Broadpeak, NETINT, Ant Media and Red5 Pro: each with its slug, name, one-line description, website, the opening paragraph of its marketplace page, its listings (slug and name) and the netactuate.com URL of its page. 'Open Source' is the marketplace's grouping of open-source projects, marked isVendor: false. Takes no arguments. Use for 'who are NetActuate's media technology partners' or 'which vendors' software can I run on NetActuate'. For one vendor's listings in detail, find_marketplace_apps with vendor.

Returns one page of NetActuate's technical documentation (netactuate.com/docs) in full: how-to guides (cloud-init, Terraform, Ansible, Kubernetes, BGP and anycast, firewalls, load balancers, Secrets Manager, storage), product and platform reference pages, and each marketplace appliance's setup page. Gives the page's description and its body in order, headings marked '## ' and code blocks fenced, with its URL, and the marketplace listing for an appliance page. Accepts a URL or path from search_netactuate, a marketplace listing's docsUrl, or a page title such as 'Building VMs with Cloud-Init'. A title matching several pages returns up to ten candidates rather than a guess; a page longer than the server keeps is cut, with a note. An API reference page returns its endpoint instead of a body: to find endpoints, use find_api_endpoints. For marketing pages, get_netactuate_page.

Returns the full published text of one NetActuate page other than a data center: a product, solution, product category, case study, region, internet exchange or company page. Gives its summary, section headings, body copy and FAQs, with its netactuate.com URL. Use it when a question needs more than search_netactuate's one-line summaries: how Media Substrate works, what the pricing page says, what a case study found. Accepts a slug or URL from search_netactuate or list_services, or a page name such as 'Media Substrate' or 'MOQ Relay'. A name matching several pages returns up to ten candidates with their slugs rather than a guess. A very long page is cut to fit, with a note saying how much is shown; the whole page is at its URL. For a data center use get_data_center.

Keyword search across everything NetActuate publishes: the website (data centers, internet exchanges, products and pricing such as Media Substrate, MOQ Relay and the cost estimator, case studies, news, the facility FAQs), the marketplace's deployable apps, and the technical docs and API reference. Results come grouped by content type, ranked by relevance, as one-line summaries (a marketplace app and its setup page also carry its VM sizing, the app its free-demo terms); matchCounts gives the full count when a group is cut at `limit`. Results hold every word of the query (when none does, those holding the most, with a note), except a place: in 'Wowza Africa' the region, country or city is read as a location, the other words are searched, and `place` lists NetActuate's data centers there (the nearest ones for a city without a site). A query about VPUs also gets vpuLocations, where VPU capacity is live today (in the place, when one is named), and one naming a certification gets compliance, NetActuate's own certifications apart from its facilities'. Use it when no specific tool fits: product, pricing, software and how-to questions. For full text, pass a result's slug to get_netactuate_page, a listing's to get_marketplace_app, or a docs url to get_netactuate_doc.

Returns everything NetActuate publishes about one facility: building specs, the facility's compliance certifications, physical security, connectivity and carrier access, power and cooling, the Looking Glass node id, the site-specific FAQs, whether VPU capacity is live there, and its netactuate.com URL. Use it once the site is known; to find sites, use list_data_centers or find_nearest_data_centers. Some cities have two facilities (the second is labelled '(extension)'): a city name returns the primary one in full and names the other in otherSitesInCity. A partial name matching several sites returns those candidates rather than a guess. Coordinates are the city's centre, not the facility's address.

Lists NetActuate's data centers (points of presence), filtered by any mix of region, country, certification, VPU capacity and free text; with no filter it returns every site with a page on netactuate.com, and dataCenterLocations, NetActuate's own total: the figure to quote for how many locations it has. Each result gives the slug, name, city, country, region, facilityCertifications (the facility's, not NetActuate's own: get_compliance_coverage has those) and netactuate.com URL. Use it for 'where does NetActuate have presence', 'anything in Asia', 'which European sites are SOC 2' or 'where can I get VPUs' (vpu: true). For one site in full use get_data_center; for the sites nearest a place, find_nearest_data_centers; for how many sites hold each certification, get_compliance_coverage. A region or country it does not recognise is explained in a note, so an empty list means no published site matches.

Searches the documentation of NetActuate's API (the API reference at netactuate.com/docs) for endpoints by what they do: 'create a virtual machine', 'list BGP sessions', 'firewall rules', 'DNS records', 'Kubernetes cluster'. It only reads that documentation: it never calls NetActuate's API and cannot change anything. Every word must match (filler such as 'a' or 'API' is ignored), read in the API's own terms ('VM' finds cloud server endpoints first, 'create' finds build ones), and the verb weighs the documented method; with no query it lists endpoints `limit` at a time. Each result gives the documented HTTP method, path, one-line summary, API version (v2 or v3; both are current, v3 for the newer resources) and the URL of its reference page, where the parameters and request body are; count is the full number of matches. Use for 'how do I do X with the NetActuate API'. For how-to guides, Terraform and Ansible: search_netactuate or get_netactuate_doc.

Answers 'which NetActuate locations are SOC 2 / HIPAA / ISO 27001 certified' across the whole footprint, and 'is NetActuate itself SOC 2 certified'. With no argument it returns netactuateCertifications, NetActuate's own as netactuate.com/compliance lists them, and every certification its facilities publish with how many sites hold each. With a certification it lists the sites whose facility holds it, each with publishedAs: the site's own wording of the certificate, as evidence, and says whether NetActuate itself holds it. A facility's certification is not NetActuate's own. Names are normalised, because the website writes some standards several ways. Use it for regulated-workload placement; to combine a certification with a region or country, use list_data_centers' certification filter instead.

Lists the internet exchanges (IXs) where NetActuate offers colocation, bare metal, virtual machines or remote peering, for example AMS-IX, DE-CIX and LINX. With no query it returns every exchange NetActuate publishes a page for; each result gives the slug, name, description, the opening paragraph of its page and its netactuate.com URL. Use it for peering and interconnection questions, such as 'does NetActuate peer at DE-CIX' or 'which exchanges offer remote peering'. Exchange pages name cities, not regions, so filter by city or exchange. A query also returns namedOnDataCenterPages: the data centers whose own pages name a matching exchange, with those lines, which covers exchanges without a page of their own (NL-IX at Amsterdam, JPNAP at Tokyo). For an exchange's full page use get_netactuate_page; for the data centers themselves, list_data_centers.

Ranks NetActuate data centers by great-circle distance from a place named in the question: the market to be served, where the end users are, or a city being compared. Use for 'what is your closest location to Lagos', 'which sites would serve users in Japan' or latency planning. Pass the place the question is about, not where the person asking is, unless they ask for the site nearest them and say where that is. Each result is a site summary with distanceKm, nearest first. Distances are computed from city centroids, so treat them as approximate guidance, not a latency guarantee. Places are matched against a built-in list of major cities and countries; one it does not know is reported, and latitude and longitude can be passed instead.

Returns what NetActuate sells: its products as the site's own menu groups them (Cloud, Acceleration & AI, Edge Infrastructure, Networking; for example VPC, Managed K8s, GPU as a Service, Bare Metal, Object Storage, BGP Anycast, Media Substrate), each product with its slug, name, one-line description and netactuate.com URL; plus the product category pages and the solution pages (CDN, DNS, disaster recovery, cloud repatriation, overlay networks, security infrastructure, C-band transition). Takes no arguments. Use to answer 'what does NetActuate actually sell' or 'does NetActuate offer X'. Pages outside the menu, such as MOQ Relay and the pricing pages, are found with search_netactuate. Any page's full text: get_netactuate_page with its slug.