Model Context Protocol (MCP) connects AI applications to server capabilities. Nexus public MCP helps clients find product facts and plan deployments; it does not connect advertiser accounts, reveal live reports or authorize campaign changes.

01

Choose the right connection

Use https://www.nexus-soft.org/mcp for read-only public product discovery over Streamable HTTP. Private operational connections have separate authorization; their tools depend on the server, modules and identity. Website registration does not grant administrator rights or platform assignments.

  • Public discovery: products, pricing scope, formats and integration requirements.
  • Private operations: verify server, identity, platform scope and permitted action.
  • Never send passwords, tokens, personal endpoints or customer exports to public discovery.
02

Understand tools, resources and prompts

MCP distinguishes callable tools, readable resources and reusable prompt templates. Nexus offers get_product_capabilities and paginated get_public_knowledge search, plus nexus://products/catalog and nexus://knowledge/public resources. The solution-discovery prompt helps plan a deployment; it does not create infrastructure. Use advertised input schemas rather than guessing dashboard fields.

03

Initialize, discover, then request information

Start with initialize to negotiate version and capabilities, then notifications/initialized. Discover capabilities through tools/list, resources/list and prompts/list. The specifications below explain this sequence. A referenced version is not a claim that every optional MCP feature is implemented by Nexus or supported by every client.

  • Confirm client transport support and use the canonical HTTPS endpoint.
  • Inspect capabilities and schemas before calling tools.
  • Handle protocol and tool errors; a failed call proves no capability.
04

Illustrative discovery: planning an XML network

With publisher traffic and advertiser agreements in place, inspect get_product_capabilities for feeds. Use get_public_knowledge to find XML mapping, limits and reporting guidance, then compare sources and scope before requesting a deployment recommendation. This is a planning example, not a recorded customer session or provider test.

  • Ask which XML controls exist and what the provider must confirm.
  • Expect sourced capabilities and outstanding integration questions.
  • Do not expect a created feed, changed budget or private report.
05

Treat operational access as a separate decision

For an operational connection, discover its own tools and permissions. Before sensitive changes, inspect targets and proposed values and obtain the required approval. Descriptions and read-only hints are not authorization controls. Public Nexus tools expose no arbitrary database queries, Redis access or code execution.

06

Keep the answer connected to evidence

Nexus public facts come from the website’s product, service and resource content, with source pages and scope boundaries. Separate educational examples from verified controls and deployment commitments. MCP does not eliminate model mistakes, prove partner compatibility or promise autonomous optimization. Ask Nexus to validate undocumented requirements.

07

Free external MCP versus in-platform AI

Connect your Nexus platform to ChatGPT and other compatible MCP clients with no Nexus integration fee. The paid in-platform AI add-on is not required. Third-party AI client subscriptions and AI provider fees are not included and may apply separately. Connection availability depends on your client, account and workspace settings; platform access still requires authorization.

08

Additional Fraud Filters

$100 per month per platform, with one free month from activation. Additional traffic-quality checks beyond the standard platform filters: datacenters, known attack sources, Tor, VPN, crawlers and fake crawlers, web scrapers and proxies. These checks do not guarantee detection of all invalid traffic. The add-on is billed once per platform, not separately for each module or location. $100 per month; the first month is free from add-on activation.

09

Test links

$100 per month per platform, with one free month from activation. Inspect the final URL, redirect chain, redirect timing and screenshot for a test link. Select the referrer, country, device profile and browser engine for the test. The add-on is billed once per platform, not separately for each module or location. $100 per month; the first month is free from add-on activation.

010

In-platform AI

$500 per month per platform, with one free month from activation. AI inside your Nexus platform, with model usage included in the add-on price. This tariff is for AI inside a customer's platform, not the public product guide on this website. The add-on is billed once per platform, not separately for each module or location. $500 per month; the first month is free from add-on activation.

Product accuracy

This guide describes Nexus product architecture and general AdTech operating concepts. Exact enforcement and integration behavior depends on the enabled revenue engine and agreed deployment configuration.

Published by Nexus Soft.

Content revised

Sources and product scope

Product references describe available controls and their limits. Examples are illustrative.