MCP / Connector Publishing Terms

These MCP / Connector Publishing Terms (“Connector Terms”) govern access to, publication of, deployment of, use of, operation of, and interaction with MCP servers, connectors, integrations, APIs, external system integrations, and related connector functionality made available through the NexNodo platform or NexNodo Marketplace.

These Connector Terms form part of and are incorporated into the applicable NexNodo Terms of Service, Marketplace Terms, Third-Party Application Terms, Open Source Software Policy, Cloud Service Agreement, Enterprise Agreement, or equivalent customer agreement governing customer use of the NexNodo platform.

Capitalized terms not otherwise defined herein shall have the meanings assigned under the applicable customer agreement.

1. PURPOSE AND SCOPE

The NexNodo platform and NexNodo Marketplace may support MCP servers, connectors, integrations, APIs, authentication integrations, infrastructure integrations, observability integrations, developer tooling integrations, external system integrations, and related connectivity functionality.

Connector functionality may facilitate interaction between the NexNodo ecosystem and independent software systems, external APIs, cloud services, SaaS platforms, databases, infrastructure systems, AI services, repositories, development tooling, observability platforms, or equivalent external environments.

Examples may include integrations involving:

GitHub
GitLab
OpenAI
databases
observability systems
identity providers
developer tooling
AI tooling
MCP servers
or substantially equivalent third-party ecosystems.

2. CONNECTOR MODEL AND EXTERNAL DEPENDENCIES

MCP servers and connectors may depend upon external systems, third-party APIs, software providers, infrastructure providers, SaaS vendors, software communities, authentication providers, cloud services, networking environments, or equivalent operational dependencies outside NexNodo control.

Accordingly, connector functionality, compatibility, authentication outcomes, operational continuity, API behavior, feature availability, integration behavior, or supported capabilities may evolve, change, degrade, become restricted, or cease functioning without prior notice.

Unless expressly stated otherwise, NexNodo does not guarantee uninterrupted connector operation, API continuity, integration stability, feature permanence, backward compatibility, external dependency continuity, or connector availability.

3. CUSTOMER CREDENTIALS, AUTHORIZATION, AND ACCESS CONTROL

Customers remain solely responsible for credentials, secrets, authentication materials, API keys, OAuth tokens, access tokens, certificates, passwords, service accounts, connection parameters, and equivalent access mechanisms associated with connector usage.

Customers remain responsible for:

credential security
token lifecycle management
access scope review
authentication configuration
permission management
connector authorization settings
and operational governance of connector-related credentials.

Customers should grant only permissions, scopes, privileges, and authorization levels appropriate for their intended operational requirements.

NexNodo shall not be responsible for customer credential misuse, excessive permissions, misconfigured access scopes, credential leakage, customer authorization decisions, or equivalent customer-controlled access outcomes.

4. THIRD-PARTY API CHANGES AND EXTERNAL PLATFORM BEHAVIOR

Third-party providers may independently modify APIs, authentication frameworks, rate limits, service availability, licensing models, permission models, commercial terms, software behavior, integration capabilities, or platform governance frameworks.

Such changes may affect connector functionality, compatibility, feature behavior, authentication success, deployment outcomes, or integration continuity.

Unless expressly stated otherwise, NexNodo does not undertake obligations relating to:

third-party API continuity
third-party roadmap stability
external provider backward compatibility
external feature permanence
provider uptime guarantees
or equivalent third-party operational outcomes.

NexNodo shall not be responsible for connector disruption, degraded integration behavior, functionality loss, incompatibility, or operational changes arising from third-party platform actions or external dependency behavior.

5. MCP SERVERS, CONNECTORS, AND SERVICE LEVEL TREATMENT

Unless expressly stated otherwise within a specific marketplace listing, written agreement, enterprise arrangement, or service description, MCP servers, connectors, integrations, and related connectivity functionality are not subject to independent NexNodo uptime guarantees, maintenance commitments, operational warranties, or service level agreements.

The NexNodo Customer Service Level Agreement generally applies to covered NexNodo-controlled platform functionality and does not automatically extend to:

MCP servers
connectors
external APIs
third-party integrations
customer-configured integrations
external SaaS dependencies
or equivalent integration ecosystems.

Certain connectors or integrations may depend upon independent third-party service commitments, upstream provider practices, community support models, or vendor-specific frameworks; however, NexNodo does not independently guarantee such commitments unless expressly stated otherwise.

6. CONNECTOR GOVERNANCE, APPROVAL, AND REMOVAL RIGHTS

NexNodo may maintain commercially reasonable governance practices relating to connector eligibility, connector security posture, operational suitability, licensing treatment, customer safety considerations, platform integrity, external dependency management, or marketplace quality considerations.

Without limitation, NexNodo may, in its reasonable discretion:

approve connectors
reject connectors
restrict connectors
remove connectors
disable connectors
suspend connector functionality
modify marketplace presentation
limit deployment availability
or implement equivalent governance actions.

Nothing in these Connector Terms obligates NexNodo to publish, maintain, certify, support, or continue offering any connector, MCP server, integration, or related functionality.

7. FUTURE PUBLISHING FRAMEWORKS

The NexNodo ecosystem may, from time to time, support publication, submission, onboarding, review, operation, or distribution of connectors, MCP servers, integrations, or related functionality originating from:

third-party developers
software vendors
community contributors
data center partners
technology partners
enterprise customers
or equivalent external publishers.

Where applicable, additional publishing frameworks, onboarding policies, connector review criteria, vendor agreements, publishing requirements, marketplace governance rules, or connector-specific commercial terms may apply.

8. SECURITY, COMPLIANCE, AND CUSTOMER VALIDATION

Customers remain responsible for independently evaluating connectors, MCP servers, integrations, and external dependencies for suitability, security posture, licensing compatibility, regulatory compatibility, privacy implications, operational fitness, and business appropriateness.

Customers should evaluate, where applicable:

API permissions
credential scopes
data handling implications
external dependency risks
authentication requirements
security posture
provider reputation
operational requirements
privacy considerations
compliance implications
or equivalent technical, legal, security, and operational factors.

Unless expressly stated otherwise, NexNodo does not independently certify, warrant, validate, audit, or guarantee connector suitability for customer-specific requirements.

9. DISCLAIMERS AND LIMITATION OF RESPONSIBILITY

To the maximum extent permitted under applicable law, MCP servers, connectors, integrations, APIs, and related connectivity functionality are made available on an “AS IS” and “AS AVAILABLE” basis.

Unless expressly stated otherwise, NexNodo disclaims warranties, guarantees, representations, commitments, and assurances relating to:

connector availability
API compatibility
authentication continuity
integration behavior
external dependency stability
feature permanence
deployment outcomes
business outcomes
or substantially equivalent integration-related matters.

To the maximum extent permitted by applicable law, NexNodo shall not be responsible for losses, connector failures, API disruptions, authentication failures, credential misuse, provider changes, external dependency outages, integration incompatibilities, customer configuration issues, customer authorization decisions, or equivalent operational consequences arising from connector or MCP usage.

10. RELATIONSHIP TO OTHER DOCUMENTS

These Connector Terms operate together with:

Marketplace Terms
Third-Party Application Terms
Open Source Software Policy
Terms of Service
Billing Policy
Refund Policy
Customer Service Level Agreement
and equivalent NexNodo platform policies.

To the extent of direct conflict regarding upstream software licensing, external provider terms, API usage requirements, or third-party platform governance frameworks, the applicable upstream framework shall govern the relevant external system.

Except as expressly modified herein, the applicable customer agreement shall remain in full force and effect.

11. TERMS MODIFICATIONS

NexNodo may modify these Connector Terms from time to time.

Material modifications may become effective upon publication, customer notification, platform publication, marketplace publication, or equivalent commercially reasonable notice mechanisms implemented by NexNodo.

Continued use of MCP servers, connectors, integrations, or related marketplace functionality following policy effectiveness constitutes acceptance of the revised Connector Terms to the extent permitted under the applicable customer agreement.

12. CONTACT

Questions relating to connectors, MCP servers, integrations, publishing frameworks, API treatment, connector governance, or operational connector matters may be directed to:

support@nexnodo.com

or equivalent contact channels designated by NexNodo from time to time.