Feature/dao nft tools

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,46 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: '[BUG]'
+labels: bug
+assignees: ''
+---
+
+## Bug Description
+
+A clear and concise description of what the bug is.
+
+## Steps To Reproduce
+
+1. Go to '...'
+2. Click on '....'
+3. Scroll down to '....'
+4. See error
+
+## Expected Behavior
+
+A clear and concise description of what you expected to happen.
+
+## Actual Behavior
+
+A clear and concise description of what actually happened.
+
+## Screenshots
+
+If applicable, add screenshots to help explain your problem.
+
+## Environment
+
+- OS: [e.g. macOS, Windows, Linux]
+- Node.js version: [e.g. 16.14.0]
+- npm/yarn version: [e.g. 8.5.0]
+- Base MCP version: [e.g. 1.0.0]
+- Claude Desktop version (if applicable): [e.g. 1.2.0]
+
+## Additional Context
+
+Add any other context about the problem here.
+
+## Possible Solution
+
+If you have ideas on how to fix the issue, please share them here.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,31 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: '[FEATURE] '
+labels: enhancement
+assignees: ''
+---
+
+## Problem Statement
+
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+## Proposed Solution
+
+A clear and concise description of what you want to happen.
+
+## Alternative Solutions
+
+A clear and concise description of any alternative solutions or features you've considered.
+
+## Use Case
+
+Describe how this feature would be used and who would use it.
+
+## Additional Context
+
+Add any other context or screenshots about the feature request here.
+
+## Implementation Ideas
+
+If you have ideas on how to implement this feature, please share them here.

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,31 @@
+## Description
+
+Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context.
+
+Fixes # (issue)
+
+## Type of change
+
+Please delete options that are not relevant.
+
+- [ ] Bug fix (non-breaking change which fixes an issue)
+- [ ] New feature (non-breaking change which adds functionality)
+- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
+- [ ] Documentation update
+
+## How Has This Been Tested?
+
+Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce.
+
+## Checklist:
+
+- [ ] My code follows the style guidelines of this project
+- [ ] I have performed a self-review of my own code
+- [ ] I have commented my code, particularly in hard-to-understand areas
+- [ ] I have made corresponding changes to the documentation
+- [ ] My changes generate no new warnings
+- [ ] I have added tests that prove my fix is effective or that my feature works
+- [ ] New and existing unit tests pass locally with my changes
+- [ ] Any dependent changes have been merged and published in downstream modules
+
+## Screenshots (if appropriate):

.github/workflows/build.yml

@@ -0,0 +1,27 @@
+name: Build
+
+on:
+  pull_request:
+    branches: [main, master]
+  push:
+    branches: [main, master]
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v3
+
+      - name: Setup Node.js
+        uses: actions/setup-node@v3
+        with:
+          node-version: '20'
+
+      - name: Enable Corepack
+        run: corepack enable
+
+      - name: Install dependencies
+        run: yarn install
+
+      - name: Build
+        run: yarn build

.github/workflows/format.yml

@@ -0,0 +1,27 @@
+name: Format
+
+on:
+  pull_request:
+    branches: [main, master]
+  push:
+    branches: [main, master]
+
+jobs:
+  prettier:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v3
+
+      - name: Setup Node.js
+        uses: actions/setup-node@v3
+        with:
+          node-version: '20'
+
+      - name: Enable Corepack
+        run: corepack enable
+
+      - name: Install dependencies
+        run: yarn install
+
+      - name: Check Format
+        run: yarn ci:format

.github/workflows/lint.yml

@@ -0,0 +1,27 @@
+name: Lint
+
+on:
+  pull_request:
+    branches: [main, master]
+  push:
+    branches: [main, master]
+
+jobs:
+  eslint:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v3
+
+      - name: Setup Node.js
+        uses: actions/setup-node@v3
+        with:
+          node-version: '20'
+
+      - name: Enable Corepack
+        run: corepack enable
+
+      - name: Install dependencies
+        run: yarn install
+
+      - name: Run ESLint
+        run: yarn lint

.gitignore

@@ -7,3 +7,7 @@
 
 node_modules
 .env
+
+build/*
+
+*.tgz

.npmignore

@@ -0,0 +1,24 @@
+# Source files (since we're publishing the compiled output)
+src/
+
+# Development files
+.editorconfig
+.gitignore
+.yarnrc.yml
+tsconfig.json
+yarn.lock
+node_modules/
+
+# Environment and configuration files
+.env
+.env.*
+claude_desktop_config.json
+
+# Test files
+test-mcp.js
+
+# Misc
+.DS_Store
+.vscode/
+.idea/
+*.log

.prettierrc

@@ -0,0 +1,8 @@
+{
+  "plugins": ["@ianvs/prettier-plugin-sort-imports"],
+  "importOrder": ["<THIRD_PARTY_MODULES>", "^@/(.*)$", "^[./]"],
+  "importOrderParserPlugins": ["typescript", "jsx", "decorators-legacy"],
+  "semi": true,
+  "singleQuote": true,
+  "trailingComma": "all"
+}

CODE_OF_CONDUCT.md

@@ -0,0 +1,39 @@
+# Code of Conduct
+
+## Our Pledge
+
+We pledge to make participation in our project and community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment include:
+
+- Using welcoming and inclusive language
+- Being respectful of differing viewpoints and experiences
+- Gracefully accepting constructive criticism
+- Focusing on what is best for the community
+- Showing empathy towards other community members
+
+Examples of unacceptable behavior include:
+
+- The use of sexualized language or imagery and unwelcome sexual attention or advances
+- Trolling, insulting/derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or electronic address, without explicit permission
+- Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team. All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org), version 1.4, available at [https://www.contributor-covenant.org/version/1/4/code-of-conduct.html](https://www.contributor-covenant.org/version/1/4/code-of-conduct.html)

CONTRIBUTING.md

@@ -0,0 +1,107 @@
+# Contributing to Base MCP
+
+Thank you for your interest in contributing to the Base MCP server! This document provides guidelines and instructions for contributing to this project.
+
+## Code of Conduct
+
+Please be respectful and considerate of others when contributing to this project. We aim to foster an inclusive and welcoming community.
+
+## How to Contribute
+
+### Reporting Bugs
+
+If you find a bug, please create an issue on GitHub with the following information:
+
+- A clear, descriptive title
+- A detailed description of the bug
+- Steps to reproduce the bug
+- Expected behavior
+- Actual behavior
+- Any relevant logs or screenshots
+- Your environment (OS, Node.js version, etc.)
+
+### Suggesting Enhancements
+
+If you have an idea for an enhancement, please create an issue on GitHub with the following information:
+
+- A clear, descriptive title
+- A detailed description of the enhancement
+- Any relevant examples or mockups
+- Why this enhancement would be useful
+
+### Pull Requests
+
+1. Fork the repository
+2. Create a new branch for your feature or bugfix (`git checkout -b feature/amazing-feature`)
+3. Make your changes
+4. Run tests to ensure your changes don't break existing functionality
+5. Commit your changes (`git commit -m 'Add some amazing feature'`)
+6. Push to the branch (`git push origin feature/amazing-feature`)
+7. Open a Pull Request. Use [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) as your PR's title.
+
+## Development Setup
+
+1. Clone your fork of the repository
+2. Install dependencies: `npm install`
+3. Create a `.env` file with your credentials (see README.md)
+4. Build the project: `npm run build`
+5. Test the MCP server: `npm test`
+
+## Coding Standards
+
+- Follow the existing code style
+- Write clear, descriptive commit messages
+- Add comments to your code where necessary
+- Write tests for new features
+- Update documentation when necessary
+
+## Adding New Tools
+
+If you want to add a new tool to the Base MCP server, follow these steps:
+
+1. Create a new file in the `src/tools` directory
+2. Implement the tool following the existing patterns
+3. Add the tool to the list of available tools in `src/tools/index.ts`
+4. Add documentation for the tool in the README.md
+5. Add examples of how to use the tool in examples.md
+6. Write tests for the tool
+
+Existing project structure:
+
+```
+src/
+├── tools/
+│   ├── index.ts (exports toolsets)
+│   ├── [TOOL_NAME]/ <-------------------------- ADD DIR HERE
+│   │   ├── index.ts (defines and exports tools)
+│   │   ├── schemas.ts (defines input schema)
+│   │   └── handlers.ts (implements tool functionality)
+│   └── utils/ (shared tool utilities)
+```
+
+## Testing
+
+Please ensure that all tests pass before submitting a Pull Request. You can run tests with:
+
+```bash
+npm test
+```
+
+## Documentation
+
+Please update the documentation when necessary, including:
+
+- README.md
+- examples.md
+- Code comments
+- This CONTRIBUTING.md file
+
+## License
+
+By contributing to this project, you agree that your contributions will be licensed under the project's [MIT License](LICENSE).
+
+## Questions?
+
+If you have any questions about contributing, please create an issue on GitHub or reach out to the maintainers.
+
+Thank you for your contributions!