# NetActuate (remote · netactuate.com) Current data on NetActuate's data centers, compliance, products, marketplace apps and docs. - Trust score: 75/100 (medium) - Registry status: active - Liveness: live - Owner verified: no - Last scored: 2026-11-05 ## Components - remote · `netactuate.com`: 75/100 (this document), [markdown](https://verifymcp.io/servers/com-netactuate-net-actuate/netactuate.md), [page](https://verifymcp.io/servers/com-netactuate-net-actuate/netactuate) ## Channel facts - Endpoint: `https://netactuate.com/mcp` - Transports: `streamable-http` - Auth: `none` - Version: `0.2.13` ## Trust breakdown How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog) Scored 2026-11-05. - **Endpoint Security**: 80/100 - The endpoint's TLS certificate is valid, in date, and uses a strong key. - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. - HTTPS is enforced; there's no plaintext access path. - The HSTS (Strict-Transport-Security) header is present. - DNSSEC check failed: this domain isn't protected by DNSSEC. - **Transport & Reachability**: 100/100 - Verified streamable-http transport via a live MCP handshake. - **Schema Quality & AI Usability**: 77/100 - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name). - AI-judged instruction clarity (excellent). - Context-footprint check failed: tool/resource definitions use about 4074 tokens (~291/item across 14 items; 13 tools + 1 resources), over budget; trim descriptions and params. - Usage-examples check failed: none of the tools include examples. - **Stability & Change Management**: 10/100 - Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses. - **Tool Coverage**: 100/100 - 100% of tools have a non-trivial description (not blank, and not just the tool's name). - 100% of tool parameters carry a description. - **Tool Safety**: 100/100 - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured. - We read all 13 captured tool definition(s), and no name or description among them implies an irreversible operation. - An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it. - **Capabilities**: 100/100 - Implements a current MCP spec version (2026-07-28). ## Install ### How do I install the NetActuate MCP server? NetActuate is a hosted endpoint at https://netactuate.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation. ### Claude ```bash claude mcp add --transport http com-netactuate-net-actuate 'https://netactuate.com/mcp' ``` ### Cursor ```json { "mcpServers": { "com-netactuate-net-actuate": { "url": "https://netactuate.com/mcp" } } } ``` ### VS Code ```json { "servers": { "com-netactuate-net-actuate": { "type": "http", "url": "https://netactuate.com/mcp" } } } ``` ### Codex ```toml [mcp_servers.com-netactuate-net-actuate] url = "https://netactuate.com/mcp" ``` ### opencode ```json { "$schema": "https://opencode.ai/config.json", "mcp": { "com-netactuate-net-actuate": { "type": "remote", "url": "https://netactuate.com/mcp", "enabled": true } } } ``` ### OpenClaw ```bash openclaw mcp add com-netactuate-net-actuate --url 'https://netactuate.com/mcp' --transport streamable-http ``` ### Hermes ```yaml mcp_servers: com-netactuate-net-actuate: url: "https://netactuate.com/mcp" ``` ### Netclaw ```json { "McpServers": { "com-netactuate-net-actuate": { "Transport": "http", "Url": "https://netactuate.com/mcp" } } } ``` ### Vellum ```bash assistant mcp add com-netactuate-net-actuate -t streamable-http -u 'https://netactuate.com/mcp' ``` ### Other ```json { "mcpServers": { "com-netactuate-net-actuate": { "type": "http", "url": "https://netactuate.com/mcp" } } } ``` The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs. ## Changelog Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims. ### 2026-11-04 (score 75, +1) - [functional] Server version: 0.2.13 → 0.2.15 ### 2026-11-03 (score 74, 0) - [functional improvement] Stability: unverified → 0.03 ### 2026-11-02 (score 74) First indexed and scored. ## MCP tools (13) ### `list_data_centers` (~476 tokens) List NetActuate data centers 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. Input parameters: - `certification` (string): Only return sites holding this certification, e.g. 'SOC 2', 'HIPAA', 'ISO 27001'. Naming several ('HIPAA and SOC 2') returns sites holding all of them; use 'or' for any of them. - `country` (string): Country name, e.g. 'Germany', 'USA', 'United States', 'UK'. Matched exactly, not by substring. - `query` (string): Words that must all appear in the facility's published record (specs, carriers, FAQs), e.g. 'Equinix', 'liquid cooling', 'renewable'. - `region` (string): Region. Accepts NetActuate's own names ('Europe', 'North America', 'Asia & Oceania', 'South America', 'Middle East & Africa') and common ways of asking: 'Africa', 'APAC', 'EMEA', 'LATAM', 'Middle Eas… - `vpu` (boolean): true: only the locations where VPU capacity (NETINT video processing units, VPU-as-a-Service) is live today. Other locations are available for VPUs as a custom deployment. ### `get_data_center` (~198 tokens) Get one data center in full 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. Input parameters: - `location` (string, required): Data center slug from list_data_centers (e.g. 'amsterdam-netherlands-datacenter') or city name, optionally with its country (e.g. 'Amsterdam', 'London, UK'). ### `find_nearest_data_centers` (~275 tokens) Find the nearest NetActuate PoPs 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. Input parameters: - `latitude` (number): Latitude in decimal degrees, with longitude, when the place name is not recognised. - `limit` (integer): How many sites to return, 1 to 20. - `location` (string): The place to measure from: the target market or the end users' city or country, e.g. 'Lagos', 'Berlin', 'Osaka, Japan'. Omit if passing coordinates. - `longitude` (number): Longitude in decimal degrees, with latitude, when the place name is not recognised. ### `get_compliance_coverage` (~237 tokens) Compliance coverage across the footprint 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. Input parameters: - `certification` (string): Certification to filter by, e.g. 'HIPAA', 'SOC 2 Type II', 'ISO 27001'. Naming several ('HIPAA and SOC 2') lists sites holding all of them; use 'or' for any of them. ### `list_internet_exchanges` (~251 tokens) List internet exchange presence 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. Input parameters: - `query` (string): Words that must all appear on the exchange's page: an exchange or city name, or a service, e.g. 'DE-CIX', 'Frankfurt', 'remote peering'. ### `list_services` (~180 tokens) List NetActuate products and solutions 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. ### `find_marketplace_apps` (~471 tokens) Find apps in NetActuate's marketplace 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'). Input parameters: - `category` (string): A marketplace category: 'Media & Streaming', 'Networking & Security', 'AI & ML', 'Observability', 'Storage' or 'Consulting & Services'. - `freeDemo` (boolean): true for only the listings that offer a free live demo from their page. - `licensing` (string): 'free', 'byol' (bring your own license, plus NetActuate compute) or 'trial'. - `limit` (integer): How many listings to return, 1 to 50. - `query` (string): Words that must all appear in the listing (name, vendor, description, features, use cases, protocols), e.g. 'transcode', 'WebRTC', 'SRT', 'ad insertion'. - `vendor` (string): A vendor as list_marketplace_partners names it, e.g. 'Wowza', 'NETINT', 'Broadpeak'. 'Open Source' gives the open-source projects. ### `get_marketplace_app` (~253 tokens) Get one marketplace listing in full 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. Input parameters: - `app` (string, required): A listing's slug or URL (e.g. 'wowza-streaming-engine', 'https://netactuate.com/marketplace/broadpeak/') or its name (e.g. 'Wowza Streaming Engine'). ### `list_marketplace_partners` (~147 tokens) List NetActuate's marketplace partners 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. ### `get_netactuate_doc` (~258 tokens) Get one NetActuate docs page in full 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. Input parameters: - `doc` (string, required): A docs URL or path (e.g. 'https://netactuate.com/docs/guides/building-with-cloud-init', 'networking/bgp'), or a page title (e.g. 'Terraform Provider v2'). ### `find_api_endpoints` (~332 tokens) Search NetActuate's API reference 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. Input parameters: - `limit` (integer): How many endpoints to return, 1 to 50. - `query` (string): Words that must all appear in the endpoint's path, summary or description, e.g. 'server', 'bgp sessions', 'firewall', 'dns record'. - `version` (string): Only this API version: v3 for VPC, Kubernetes, cloud routers, storage, firewalls and secrets; v2 for the rest. ### `search_netactuate` (~370 tokens) Search NetActuate's published content 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. Input parameters: - `limit` (integer): Maximum results per content type, 1 to 50. - `query` (string, required): Search terms, all of which must appear apart from a place (if none holds all, the most), e.g. 'renewable power', 'anycast DNS', 'live video', 'pricing', 'Wowza Africa'. Fewer, distinctive words find… ### `get_netactuate_page` (~243 tokens) Get one NetActuate page in full 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. Input parameters: - `page` (string, required): A slug or URL from search_netactuate or list_services (e.g. 'media-substrate', 'solutions/dns-services', 'https://netactuate.com/pricing'), or a page name (e.g. 'Media Substrate'). ## Diagnostics Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-netactuate-net-actuate/netactuate#diagnostics ## Score history - 2026-11-05: 75 - 2026-11-04: 75 - 2026-11-03: 74 - 2026-11-02: 74 ## Common questions ### What is the NetActuate MCP server? NetActuate is an MCP server listed in the public MCP registry as com.netactuate/net-actuate. Current data on NetActuate's data centers, compliance, products, marketplace apps and docs. This page covers its hosted endpoint (https://netactuate.com/mcp). ### Is the NetActuate MCP server safe to use? NetActuate scores 75 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm. ### What tools does the NetActuate MCP server expose? NetActuate exposes 13 tools: list_data_centers, get_data_center, find_nearest_data_centers, get_compliance_coverage, list_internet_exchanges, and 8 more. Their descriptions and schemas cost roughly 3,691 tokens of context every time the server is loaded. ### Does the NetActuate MCP server require authentication? No. We connected to NetActuate without credentials and it answered, so anything it exposes is reachable by anyone who knows the address. ### Is the NetActuate MCP server still maintained? NetActuate is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced. ## Links - Remote endpoint: https://netactuate.com/mcp - Website: https://netactuate.com/mcp - Changelog RSS feed: https://verifymcp.io/servers/com-netactuate-net-actuate/netactuate.xml - Changelog JSON feed: https://verifymcp.io/servers/com-netactuate-net-actuate/netactuate.json - HTML version of this page: https://verifymcp.io/servers/com-netactuate-net-actuate/netactuate