VOOZH about

URL: https://deepwiki.com/Digilac/simap-mcp/11-license

⇱ License | Digilac/simap-mcp | DeepWiki


Loading...
Menu

License

This page presents the licensing terms for the simap-mcp project and explains the permissions and limitations that apply to using, modifying, and distributing the software. For information about contributing to the project, see Contributing.

License Overview

The simap-mcp project is released under the MIT License, one of the most permissive open-source licenses. The copyright is held by Digilac Sàrl, with the license grant dated 2026.

Sources: LICENSE1-3

Full License Text

The complete MIT License text as it appears in the project repository:


Sources: LICENSE1-21

License Components and Coverage

The following diagram illustrates which components and artifacts are covered by the MIT License, mapping repository files to their distribution roles:

Project Asset License Coverage


Sources: LICENSE1-21 .prettierrc1-7 .gitignore1-37

Permissions Granted

The MIT License grants the following rights to any person obtaining a copy of the software:

PermissionDescriptionPractical Implication
UseRun the software for any purposeInstall and use simap-mcp in commercial or non-commercial environments
CopyMake copies of the softwareDistribute simap-mcp within organizations or to clients
ModifyAlter the source codeCustomize tools, add new features, or adapt for specific needs
MergeCombine with other softwareIntegrate simap-mcp functionality into larger applications
PublishMake the software publicly availableShare modified versions on GitHub or other platforms
DistributeProvide copies to othersInclude in software bundles or distributions
SublicenseGrant licenses to derivativesApply different licenses to derivative works
SellCommercialize the softwareOffer paid services or products based on simap-mcp

Sources: LICENSE5-10

Requirements and Limitations

Attribution Requirement

The license requires that the copyright notice and permission notice be included in all copies or substantial portions of the Software. This means:

  1. Source distributions: Must include the original LICENSE file LICENSE1-21
  2. Binary distributions: Must include the license text in distributed packages.
  3. Modified versions: Must retain the original copyright notice even when adding additional copyright notices LICENSE12-13

Disclaimer of Warranty

The software is provided "AS IS" without warranty of any kind. Key points:

Warranty TypeCoverage
Express WarrantiesNone provided
Implied WarrantiesExplicitly disclaimed, including merchantability and fitness for purpose
Bug-Free GuaranteeNo guarantee that software is error-free
Support ObligationNo obligation to provide support or updates

Sources: LICENSE15-17

Limitation of Liability

The authors and copyright holders are not liable for:

  • Claims arising from the software
  • Damages (including indirect, special, or consequential damages)
  • Other liability arising from the use or dealings in the software

This limitation applies whether the claim is based on contract, tort, or any other legal theory.

Sources: LICENSE17-21

License Distribution Flow

The following diagram shows how the license terms propagate through the development and distribution pipeline:

License Propagation Pipeline


Sources: LICENSE1-21 .prettierrc1-7

Practical Implications for Different Users

For End Users (Claude Users)

As an end user of simap-mcp:

  • Installation: You have the right to install and use the software freely via npx or npm install.
  • No fees: The software is free of charge.
  • No registration: No need to register or obtain permission.
  • Commercial use: Can be used in commercial environments.
  • No warranty: Use at your own risk; no guarantees provided LICENSE15-17

For Developers Extending simap-mcp

If you're building upon or modifying simap-mcp:

  • Fork freely: You can create modified versions of the TypeScript source in src/.
  • Keep attribution: Must include the original copyright notice LICENSE3 and license text LICENSE1-21
  • Add your copyright: You can add your own copyright notice for your modifications.
  • Different license: You can license your modifications under a different license, but must retain the MIT License for the original portions.

For Organizations Distributing simap-mcp

If you're including simap-mcp in a product or service:

  • Bundle freely: Can include in commercial products.
  • Include license: Must include the license file LICENSE1-21 in distributions.
  • Attribution: Should credit Digilac Sàrl in documentation.
  • Liability: Digilac Sàrl has no liability for your use of the software LICENSE17-21

Copyright Holder

The copyright for simap-mcp is held by:


Sources: LICENSE3

License File Location

The license file is located at the repository root:

  • Repository: LICENSE LICENSE1-21 at the root of the GitHub repository.

Sources: LICENSE1-21