open-index/open-npm huggingface dataset:
npm package: @mrdanlej/n8n-nodes-verificaremail
Description: n8n node to verify email addresses using the Emailable API
Author: Daniel Alejandro
Latest version: 0.1.0

![Banner image](https://user-images.githubusercontent.com/10284570/173569848-c624317f-42b1-45a6-ab09-f0ea3c247648.png)

# n8n-nodes-starter

This repo contains example nodes to help you get started building your own custom integrations for [n8n](https://n8n.io). It includes the node linter and other dependencies.

To make your custom node available to the community, you must create it as an npm package, and [submit it to the npm registry](https://docs.npmjs.com/packages-and-modules/contributing-packages-to-the-registry).

If you would like your node to be available on n8n cloud you can also [submit your node for verification](https://docs.n8n.io/integrations/creating-nodes/deploy/submit-community-nodes/).

## Prerequisites

You need the following installed on your development machine:

* [git](https://git-scm.com/downloads)
* Node.js and npm. Minimum version Node 20. You can find instructions on how to install both using nvm (Node Version Manager) for Linux, Mac, and WSL [here](https://github.com/nvm-sh/nvm). For Windows users, refer to Microsoft's guide to [Install NodeJS on Windows](https://docs.microsoft.com/en-us/windows/dev-environment/javascript/nodejs-on-windows).
* Install n8n with:
  ```
  npm install n8n -g
  ```
* Recommended: follow n8n's guide to [set up your development environment](https://docs.n8n.io/integrations/creating-nodes/build/node-development-environment/).

## Using this starter

These are the basic steps for working with the starter. For detailed guidance on creating and publishing nodes, refer to the [documentation](https://docs.n8n.io/integrations/creating-nodes/).

1. [Generate a new repository](https://github.com/n8n-io/n8n-nodes-starter/generate) from this template repository.
2. Clone your new repo:
   ```
   git clone https://github.com/<your organization>/<your-repo-name>.git
   ```
3. Run `npm i` to install dependencies.
4. Open the project in your editor.
5. Browse the examples in `/nodes` and `/credentials`. Modify the examples, or replace them with your own nodes.
6. Update the `package.json` to match your details.
7. Run `npm run lint` to check for errors or `npm run lintfix` to automatically fix errors when possible.
8. Test your node locally. Refer to [Run your node locally](https://docs.n8n.io/integrations/creating-nodes/test/run-node-locally/) for guidance.
9. Replace this README with documentation for your node. Use the [README_TEMPLATE](README_TEMPLATE.md) to get started.
10. Update the LICENSE file to use your details.
11. [Publish](https://docs.npmjs.com/packages-and-modules/contributing-packages-to-the-registry) your package to npm.

## More information

Refer to our [documentation on creating nodes](https://docs.n8n.io/integrations/creating-nodes/) for detailed information on building your own nodes.

## License

[MIT](https://github.com/n8n-io/n8n-nodes-starter/blob/master/LICENSE.md)
npm package: @mrdemonwolf/iconwolf-mcp
Description: MCP server for AI-driven app icon generation using iconwolf
Author: MrDemonWolf
Latest version: 0.4.0

# @mrdemonwolf/iconwolf-mcp

MCP (Model Context Protocol) server for AI-driven app icon generation using [iconwolf](https://github.com/MrDemonWolf/iconwolf).

This lets AI assistants like Claude generate app icons, favicons, splash screens, and Android adaptive icons directly through conversation.

## Quick Setup

### Claude Code

```bash
claude mcp add --scope user --transport stdio iconwolf -- npx @mrdemonwolf/iconwolf-mcp
```

Then restart Claude Code.

### Manual Configuration

Add to your MCP client settings:

```json
{
  "mcpServers": {
    "iconwolf": {
      "command": "npx",
      "args": ["@mrdemonwolf/iconwolf-mcp"]
    }
  }
}
```

**Claude Code** — Add to `~/.claude/settings.json` (global) or `.claude/settings.json` (per-project)

**Claude Desktop** — Add to `~/Library/Application Support/Claude/claude_desktop_config.json` (macOS) or `%APPDATA%\Claude\claude_desktop_config.json` (Windows)

## Available Tools

| Tool | Description | Output |
|------|-------------|--------|
| `generate_icons` | Generate all icon variants from one source image | icon.png, adaptive-icon.png, splash-icon.png, favicon.png |
| `generate_icon` | Generate a standard 1024x1024 app icon | icon.png |
| `generate_favicon` | Generate a 48x48 web favicon with rounded corners | favicon.png |
| `generate_splash` | Generate a 1024x1024 splash screen icon | splash-icon.png |
| `generate_android_icons` | Generate Android adaptive icon variants | Foreground, background, and monochrome icons |

## Input

All tools accept either:

- **`file_path`** — Path to a local PNG file or Apple Icon Composer `.icon` folder
- **`base64_image`** — Base64-encoded PNG image data

Optional: **`output_dir`** — Where to write generated files (defaults to a temp directory)

## Example Usage

Once configured, just ask your AI assistant:

> "Generate all app icon variants from ./AppIcon.icon"

> "Create a favicon from ./logo.png"

> "Generate Android adaptive icons from my app icon with a blue background"

## Requirements

- Node.js >= 18

## License

MIT
npm package: @mrdiggles2/mux
Description: muxer in typescript
Latest version: 1.0.4

# mux

Process muxer written in TypeScript.

Allows configuration of installation, runtime, and clean up of individual processes. Built in menu allows tailing, restarting, and rebuilding of processes within a single terminal session.

Particularly useful for monorepo setups where you have to run frontend, backend, and infrastructure locally.

![usage](https://raw.githubusercontent.com/MrDiggles2/mux/main/docs/example.gif)

## Getting started

1. Install package

```
npm install @mrdiggles2/mux
```

2. Create a `mux.config.ts` at the root level of your project. Sample:

```typescript
import { MuxConfig } from '@mrdiggles2/mux/config';

const config: MuxConfig = {
  rootDir: __dirname,
  logPath: '.mux/logs',
  processes: [
    {
      name: 'long sleeper',
      run: {
        exec: 'sleep 1000',
      }
    }
  ]
};

export default config;
```

3. Execute `mux`

```
npx mux
```

## Configuration

Each process in `mux.config.ts` can be configured:

```typescript
...
{
  name: 'YOUR PROCESS NAME HERE',
  run: MuxCommand,
  install?: MuxCommand,
  cleanup?: MuxCommand,

}
```

Where `MuxCommand` takes the form:

```typescript
{
    exec: <Command to run in a separate process>;
    dir?: <Path to run `exec` from. Appended to provided `rootDir` in mux.config.ts>
    env?: {
      <Additional environment variables to run command with>
    }
}
```

Since `mux.config.ts` is a TypeScript file, you can also add dynamic configuration. Here is a more complete sample:

```typescript
import path from "path";
import { MuxConfig } from '@mrdiggles2/mux/config';

const dockerComposeFiles = [
  'docker-compose.yml',
  'docker-compose.local.yaml'
].map(file => path.join(__dirname, file));

const dcBin = `docker compose --ansi=always ` + dockerComposeFiles.map(file => `-f ${file}`).join(' ');

const config: MuxConfig = {
  rootDir: __dirname,
  logPath: '.mux',
  processes: [
    {
      name: 'docker-services',
      install: {
        exec: `${dcBin} up --build -d --remove-orphans --wait`
      },
      run: {
        // Run `up` here again to smoothly support restarts. Effectively a no-op
        // if the containers are already running
        exec: `${dcBin} up -d --remove-orphans --wait && ${dcBin} logs -f`
      },
      stop: {
        exec: `${dcBin} down`
      }
    },
    {
      name: 'nest-backend',
      install: {
        exec: 'npm ci',
        dir: 'backend',
      },
      run: {
        exec: 'npx nest --watch',
        dir: 'backend',
        env: {
          NODE_ENV: development
          ...<ENV VARS>
        },
      }
    },
    {
      name: 'react-frontend',
      install: {
        exec: `npm ci`,
        dir: 'frontend',
      },
      run: {
        exec: `npx react-scripts start`,
        dir: 'frontend',
        env: {
          FORCE_COLOR: '1'
          ...<ENV VARS>
        }
      }
    },
  ]
};

export default config;
```