> For the complete documentation index, see [llms.txt](https://mcl-wp.jump.trade/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mcl-wp.jump.trade/marketplace/nfts/mcl-signed-bats/single-bats/mcl-single-signed-bat-immortal.md).
# MCL Single Signed Bat - Immortal
> *These extremely limited edition bats commemorate the spirit of the sport and imbue the wielding Meta Players with the true power of champions.*
There are a total of 12 units of MCL Single Signed Immortal NFT Bats.
The power assigned for these bats is 100.
Two individual bats were signed by the champion teams of the 1983 and 2011 World Cup.
The remaining 10 bats are signed by entities such as:
1. Alien DNA
2. Insignia
3. Mecha
### **Immortal Visual Properties**
The visual properties used to create the Immortal MCL Single Signed Bat NFTs are as follows:
Grip
* Red
* Sapphire
* Emerald
* Brass
* Bronze
* Copper
* Amber
* Jade
* Steel
* Peridot
* Amethyst
Bat Type
* 2011 CHAMPIONS COLLECTION
* 1983 CHAMPIONS COLLECTION
* MCL Signed Bat
Bat Type
Single
Frame Header
* ETH
* BTC
Frame Color
Gold
Bat Power
100
Signature
* 2011 CHAMPIONS
* 1983 CHAMPIONS
* Alien DNA
* Mecha
* Insignia
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://mcl-wp.jump.trade/marketplace/nfts/mcl-signed-bats/single-bats/mcl-single-signed-bat-immortal.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.