open-index/open-npm huggingface dataset:
npm package: @oaslananka/atlas
Description: npm Registry for MCP Servers — discover, compare, install, and trust any MCP server
Author: oaslananka
Latest version: 1.0.0

# @oaslananka/atlas

Registry and installation workflow for discovering, scoring, and validating MCP servers.

## Install

```bash
npm install -g @oaslananka/atlas
```

## Quick Start

```bash
atlas seed
atlas serve --port 4003
atlas search github --verified
```

## Example

```bash
curl http://127.0.0.1:4003/api/servers?q=github
curl http://127.0.0.1:4003/api/trending
```

## Core Features

- searchable MCP server catalog
- seed data for known servers
- HTTP registry API
- install and verification helpers
- uptime and health tracking

## Works Well With

Atlas complements `@oaslananka/bridge` for generated servers and `@oaslananka/forge` for pipelines that need discovery before execution.
npm package: @oaslananka/bridge
Description: Turn any OpenAPI/GraphQL/gRPC API into an MCP server
Author: oaslananka
Latest version: 1.0.0

# @oaslananka/bridge

Generate MCP servers from OpenAPI-style API descriptions.

## Install

```bash
npm install -g @oaslananka/bridge
```

## Quick Start

```bash
bridge validate openapi ./petstore.yaml
bridge generate openapi ./petstore.yaml --output ./generated/petstore --name petstore
```

## Example

```bash
bridge generate openapi ./openapi/internal-api.yaml \
  --output ./generated/internal-api \
  --name internal-api
```

## Core Features

- OpenAPI parsing and schema normalization
- JSON Schema generation
- MCP server code generation
- starter package metadata and README generation

## Works Well With

Generated servers can be published into `@oaslananka/atlas` and then aggregated through `@oaslananka/composer` for multi-service tool surfaces.
npm package: @oaslananka/composer
Description: Aggregate N MCP servers into one — zero config in AI clients
Author: oaslananka
Latest version: 1.0.0

# @oaslananka/composer

Aggregate multiple MCP backends into a single namespaced proxy endpoint.

## Install

```bash
npm install -g @oaslananka/composer
```

## Quick Start

```yaml
servers:
  github:
    transport: http
    url: http://localhost:3001/mcp
```

```bash
composer serve --config ./composer.yml
composer list-tools --config ./composer.yml
```

## Example

```yaml
servers:
  atlas:
    transport: http
    url: http://127.0.0.1:4003/mcp
  observatory:
    transport: http
    url: http://127.0.0.1:4006/mcp
```

## Core Features

- backend connection management
- namespaced tool routing
- conflict handling across multiple servers
- reconnect-friendly operational model

## Works Well With

Composer is the natural upstream for `@oaslananka/sentinel` and the default aggregation layer for `@oaslananka/forge` pipelines.
npm package: @oaslananka/forge
Description: Chain MCP tools into declarative pipelines — the Unix pipe for MCP
Author: oaslananka
Latest version: 1.0.0

# @oaslananka/forge

Declarative pipeline engine for chaining MCP tools into production workflows.

## Install

```bash
npm install -g @oaslananka/forge
```

## Quick Start

```bash
forge init hello-world
forge validate hello-world.yaml
forge serve --port 4000
```

## Example

```yaml
name: nightly-catalog-sync
version: "1"
servers:
  composer:
    transport: http
    url: http://127.0.0.1:4010/mcp
steps:
  - id: list-registry
    type: tool
    server: composer
    tool: atlas__search
    input:
      q: github
```

## Core Features

- pipeline execution with persistence
- timeout, retry, branching, and loop support
- HTTP API and websocket run streaming
- transform, webhook, email, and script nodes

## Works Well With

Pair Forge with `@oaslananka/composer` to fan out across multiple backends, and add `@oaslananka/sentinel` in front of those backends when pipeline execution needs policy enforcement and audit logs.
npm package: @oaslananka/observatory
Description: Full observability for MCP — traces, metrics, costs, and anomalies
Author: oaslananka
Latest version: 1.0.0

# @oaslananka/observatory

Metrics, traces, anomaly detection, alerting, and dashboards for MCP workloads.

## Install

```bash
npm install -g @oaslananka/observatory
```

## Quick Start

```bash
observatory serve --port 4006
observatory metrics latency --minutes 60
observatory baseline latency --days 7
```

## Example

```bash
curl http://127.0.0.1:4006/api/dashboard
curl http://127.0.0.1:4006/api/anomalies
```

## Core Features

- SQLite-backed metric and span storage
- anomaly detection and baseline computation
- alert channel management
- OTLP ingestion-ready observability API

## Works Well With

Observatory pairs especially well with `@oaslananka/forge` for pipeline-level telemetry and `@oaslananka/sentinel` when you want approval and denial events surfaced as operational signals.
npm package: @oaslananka/sentinel
Description: Zero-Trust MCP Security Layer — Policy, audit, PII masking, spend control
Author: oaslananka
Latest version: 1.0.0

# @oaslananka/sentinel

Zero-trust MCP proxy with key management, policy enforcement, audit logging, approval gates, and PII controls.

## Install

```bash
npm install -g @oaslananka/sentinel
```

## Quick Start

```bash
sentinel keys create --name local-dev --allow-tool "*"
sentinel pii-scan "Contact me at ops@example.com" --redact
sentinel proxy --upstream-url http://localhost:3000/mcp
```

## Example

```bash
sentinel proxy \
  --upstream-url http://127.0.0.1:4010/mcp \
  --db ./data/sentinel.sqlite \
  --policy ./examples/sentinel-policy.yaml
```

## Core Features

- virtual key lifecycle and rotation
- request and response pipelines
- audit trail export
- approval hold workflow
- PII detection and redaction including TR-specific patterns

## Works Well With

Sentinel is most effective in front of `@oaslananka/composer` or `@oaslananka/forge`, where one policy layer can protect many downstream MCP tools and pipeline runs.
npm package: @oaslananka/shared
Description: Shared MCP types, JSON-RPC utils, logger, test helpers
Author: oaslananka
Latest version: 1.0.0

# @oaslananka/shared

Shared protocol, transport, auth, retry, telemetry, and health primitives for the MCP Infrastructure Suite.

## Install

```bash
npm install @oaslananka/shared
```

## Quick Start

```ts
import { withRetry, logger } from "@oaslananka/shared";

await withRetry(async () => {
  logger.info("hello from shared");
});
```

## Example

```ts
import { MCPClient, StreamableHTTPTransport } from "@oaslananka/shared";

const client = new MCPClient(
  new StreamableHTTPTransport({ url: "http://127.0.0.1:4003/mcp" }),
  { clientInfo: { name: "catalog-check", version: "1.0.0" } },
);

await client.connect();
const tools = await client.listTools();
await client.disconnect();
console.log(tools.tools.map((tool) => tool.name));
```

## Included Modules

- MCP client and server primitives
- stdio and streamable HTTP transports
- retry and timeout helpers
- API key middleware, rate limiting, and health endpoints
- telemetry helpers for spans and metrics

## Works Well With

Use `@oaslananka/shared` as the foundation for every other workspace in the suite, especially `@oaslananka/forge` for orchestration and `@oaslananka/sentinel` for transport-aware proxying.
npm package: @oasp/asciidoc-link-checker
Description: Tool to check each link of each asciidoc
Author: Capgemini
Latest version: 1.2.2

# Asciidoc-link-checker

[![build status](https://travis-ci.org/oasp/asciidoc-link-checker.svg?branch=master)](https://travis-ci.org/oasp/asciidoc-link-checker)

Tool to check each link of each asciidoc inside a wiki of a gitHub repository

# How to use

1.  Clone this repository into a local folder on your computer or install the tool globally:

    `npm install -g @oasp/asciidoc-link-checker`

2.  Open the console and move to that folder.
3.  Install the dependencies:

    `npm install`

4.  (OPTIONAL) In order to make your own **asciidoc-link-checker** releases you need to install globally `np`:

    `npm install -g np`

5.  Clone the wiki you want to check links:

    `git clone https://github.com/my-repository/my-repository.wiki.git`

6.  Start the checkout:

    `$ linkchecker ./my-repository.wiki/`

The tool will check each link of each asciidoc inside the wiki searching those links that are wrong

# Output

When the check is done, you will see on your console the links that didn't work and an exit code

If all links are correct you will see:
'Done: All links are correct'

Otherwise you will see:
'Done: Some link failed'
npm package: @oasp/oasp4fn
Description: The Open Application Standard Platform for node.js and serverless
Author: Capgemini
Latest version: 0.6.3

# OASP4fn

Oasp4fn will help you to develop your javascript cloud backend in a fast and easy way, thanks to his intuitive API and his query-style usage and making use of the [serverless framework](https://serverless.com/) and the [webpack](https://webpack.github.io/) build tool in the deployment. You only have to choose the services you want to use with your desired options and it will be ready to use.

For more information and examples, please check out our [github wiki](https://github.com/oasp/oasp4fn/wiki).
npm package: @oasp/ts-merger
Description: 2-way TypeScript Merger
Author: Capgemini
Latest version: 2.0.0

# TS-Merger
Generic TypeScript Merger

[![build status](https://travis-ci.org/oasp/ts-merger.svg?branch=master)](https://travis-ci.org/oasp/ts-merger)
[![build status](https://travis-ci.org/oasp/ts-merger.svg?branch=develop)](https://travis-ci.org/oasp/ts-merger)

## Usage

```javascript
let tsm = require('@oasp/ts-merger');
let mergedCode: string = tsm.merge(baseContents, pathContents, patchOverrides);
```

Being:
- baseContents: contents of the base in a string
- patchContents: contents of the patch in a string
- patchOverrides(**true**/**false**): Being false, base will have priority in case of conflicts. With true, patch will have priority.  

### Example
```javascript
let tsm = require('@oasp/ts-merger');
let mergedCode: string = tsm.merge(baseContents, pathContents, patchOverrides);
```

## Features

The merger allows merging of this node kinds:

- ImportDeclaration
- ClassDeclaration
- Decorator
- FunctionDeclaration
- MethodDeclaration
- Parameter
- BodyMethod
- PropertyAssignment
- PropertyDeclaration
- Constructor
- ArrayLiteralExpression
- ObjectLiteralExpression
- CallExpression
- VariableAssignment

This version allows merging of TypeScript files that follow this structure:

- Array of imports
- Array of functions
- Array of variables
- Array of classes

##Examples

**Base file**
```javascript
import a from 'b';
import f from 'g';

class Example1 {
    private propertyFromBase: string;

    oneMethod() {
        let variable = 'base';
    }
}
```

**Patch file**

```javascript
import c from 'd';
import h from 'g';

class Example1 {
    private propertyFromPatch: number;

    oneMethod() {
        let variable = 'patch';
    }

    anotherMethod(){}
}

class AnotherClass {}
```
**Resultant merged code (patchOverrides=false)**

```javascript
import a from 'b';
import c from 'd';
import { f, h } from 'g';

class Example1 {
    private propertyFromBase: string;
    private propertyFromPatch: number;

    oneMethod() {
        let variable = 'base';
    }

    anotherMethod(){}
}

class AnotherClass {}
```

**Resulting merged code (patchOverrides=true)**

```javascript
import a from 'b';
import c from 'd';
import { f, h } from 'g';

class Example1 {
    private propertyFromBase: string;
    private propertyFromPatch: number;

    oneMethod() {
        let variable = 'patch';
    }

    anotherMethod(){}
}

class AnotherClass {}
```

## Future version

Next releases will include merge support for:

- InterfaceDeclaration