open-index/open-npm huggingface dataset:
npm package: @fincode/mcp-api
Description: MCP server for fincode payment API integration
Latest version: 1.0.2

# Fincode MCP Server

## 概要

このプロジェクトは、fincode APIをModel Context Protocol (MCP) サーバーとして利用するためのパッケージです。

導入手順は以下を参照してください
- https://github.com/fincode-byGMO/fincode-mcp.git
npm package: @fincode/mcp-docs
Description: MCP server for fincode documentation access
Latest version: 1.0.0

# Fincode MCP Server

## 概要

このプロジェクトは、fincode APIをModel Context Protocol (MCP) サーバーとして利用するためのパッケージです。

導入手順は以下を参照してください
- https://github.com/fincode-byGMO/fincode-mcp.git
npm package: @fincore/cli
Description: CLI for Fin-Core hosted tenant APIs and Hello World onboarding.
Latest version: 0.1.1

# @fincore/cli

CLI for tenant-facing Fin-Core operations and hosted Hello World onboarding.

## Install

Run without a global install:

```bash
npx @fincore/cli doctor
```

Install globally:

```bash
npm install -g @fincore/cli
fincore doctor
```

Install into a local project:

```bash
npm install @fincore/cli
npx fincore doctor
```

Distribution note:

- The intended public install paths are npm global install and `npx`.
- Phase 20 CI validates the same publish-shaped artifact path before the first registry release.

## Windows / offline zip bundle

For restricted environments, a secondary `.zip` bundle can be assembled from the built CLI.

Validated offline path:

- unzip `fincore-cli-<version>-offline.zip`
- set `FINCORE_BASE_URL` and `FINCORE_API_KEY`
- run `node .\dist\index.js doctor`
- run `node .\dist\index.js hello`
- run `node .\dist\index.js usage`

PowerShell helper:

```powershell
$env:FINCORE_BASE_URL = "https://YOUR_FINCORE_BASE_URL"
$env:FINCORE_API_KEY = "YOUR_API_KEY"
.\samples\doctor-hello-usage.ps1
```

Notes:

- the CLI zip bundles the same built `@fincore/sdk` under `node_modules/@fincore/sdk`
- it is a manual Node execution path, not a native Windows executable
- see `docs/public/windows-offline-quickstart.md` for the tested Windows flow

Commands:
- `fincore whoami`
- `fincore quickstart`
- `fincore hello`
- `fincore doctor`
- `fincore plan`
- `fincore health`
- `fincore usage [--view <summary|metering>]`
- `fincore chains list`
- `fincore suites list`
- `fincore deployments list`
- `fincore deployments show --deployment-id <id>`
- `fincore official-rail show`
- `fincore api-keys list`
- `fincore api-keys create --label <label> [--environment <env>] [--expires-at <iso>]`
- `fincore api-keys rotate <keyId> [--label <label>] [--environment <env>] [--expires-at <iso>]`
- `fincore api-keys revoke <keyId>`

Discovery command visibility rules:
- official contract-platform rows are visible to all authenticated tenants
- tenant custom suites/deployments are only visible to the tenant that owns them
- commands are read-only and do not enable contract mutation or custom authoring

Configuration precedence:
1. `FINCORE_API_KEY` / `FINCORE_BASE_URL`
2. `~/.fincore/config` JSON

First hosted flow:
- `fincore doctor`
- `fincore hello`
- `fincore usage`
- open `/usage`

`fincore doctor` checks:
- API key validity
- tenant hosted state
- plan/tier visibility
- connectivity
- request-time rate-limit posture

`fincore quickstart` is optional orientation, not part of the formal hosted success contract.

Exit codes:
- `0` ok
- `2` usage/config missing
- `10` unauthorized (401)
- `11` forbidden (403)
- `13` suspended/revoked tenant
- `14` pending tenant activation
- `15` entitlement denied
- `12` not found (404)
- `20` rate limited (429)
- `30` upstream 5xx
- `40` network-ish
- `70` unknown
npm package: @find_bumblebee/create-fox
Description: Alias for fox-init, so you could use `npm init fox showcase`.
Author: bumblebee
Latest version: 0.5.5

# create-fox

[![NPM version][npm-image]][npm-url]
[![build status][travis-image]][travis-url]
[![Test coverage][codecov-image]][codecov-url]
[![David deps][david-image]][david-url]
[![Known Vulnerabilities][snyk-image]][snyk-url]
[![NPM download][download-image]][download-url]

[npm-image]: https://img.shields.io/npm/v/create-egg.svg?style=flat-square
[npm-url]: https://npmjs.org/package/create-egg
[travis-image]: https://img.shields.io/travis/eggjs/create-egg.svg?style=flat-square
[travis-url]: https://travis-ci.org/eggjs/create-egg
[codecov-image]: https://codecov.io/gh/eggjs/create-egg/branch/master/graph/badge.svg
[codecov-url]: https://codecov.io/gh/eggjs/create-egg
[david-image]: https://img.shields.io/david/eggjs/create-egg.svg?style=flat-square
[david-url]: https://david-dm.org/eggjs/create-egg
[snyk-image]: https://snyk.io/test/npm/create-egg/badge.svg?style=flat-square
[snyk-url]: https://snyk.io/test/npm/create-egg
[download-image]: https://img.shields.io/npm/dm/create-egg.svg?style=flat-square
[download-url]: https://npmjs.org/package/create-egg

Alias for [fox-init], so you could use `npm init fox showcase`.

Thanks to `npm init` feature introduced at npm@6, see [npm-init](https://docs.npmjs.com/cli/init) for more details.

## Usage

```bash
$ npm init fox showcase
$ npm init fox showcase --type=simple
```

[MIT](LICENSE)