This module allows you to set custom protocol handler for your nodejs app.
Model Context Protocol registry, transports, and OAuth bridges for Electric Agents
This is a command line version of protocol registry npm module.
Conformance validators for MCP servers (protocol, registry, routing, security, performance)
ACP Agent Card and federated registry
Protocol Buffers for JavaScript & TypeScript.
Get the auth token set for an npm registry (if any)
Streaming library for the Microsoft Bot Framework
Model Context Protocol Registry - Reserved
Get the set npm registry URL
Canonical Noir contracts for the Aztec Network
Fetch-based http client for use with npm registry APIs
The JavaScript implementation of the Multiaddr spec
Asset support code for React Native.
Shared type definitions for Streamoid chat component registry — host context, event protocol, registry entry shapes
TypeScript client SDK for NFTC Protocol Registry API
The postgres client/server binary protocol, implemented in TypeScript
The Chrome DevTools Protocol JSON
Check if a protocol requires a certain port number to be added to an URL.
Default registry in gulp 4.
Full BCP 47 language subtag data from the official IANA repository, in JSON format with multiple indices.
Download templates and git repositories with pleasure!
Manage node_modules trees
npm registry utikities
Interface for generating and parsing the Danish CPR Registry data files. Support the 'adressematch' protocol, which can be used to query by name and adress as well as by the personal identifical number (CPR)
The Apigee Registry API allows teams to upload and share machine-readable descriptions of APIs that are in use and in development. These descriptions include API specifications in standard formats like OpenAPI, the Google API Discovery Service Format, and the Protocol Buffers Language. These API specifications can be used by tools like linters, browsers, documentation generators, test runners, proxies, and API client and server generators. The Registry API itself can be seen as a machine-readable enterprise API catalog designed to back online directories, portals, and workflow managers.
The Apigee Registry API allows teams to upload and share machine-readable descriptions of APIs that are in use and in development. These descriptions include API specifications in standard formats like OpenAPI, the Google API Discovery Service Format, and the Protocol Buffers Language. These API specifications can be used by tools like linters, browsers, documentation generators, test runners, proxies, and API client and server generators. The Registry API itself can be seen as a machine-readable enterprise API catalog designed to back online directories, portals, and workflow managers. Note that google-cloud-apigee_registry-v1 is a version-specific client library. For most uses, we recommend installing the main client library google-cloud-apigee_registry instead. See the readme for more details.
pikuri-mcp adds Model Context Protocol support to pikuri-core agents: a +Pikuri::Mcp::Registry+ for declaring stdio + HTTP MCP servers, the +Pikuri::Mcp::Servers+ runtime that spawns them, a +Pikuri::Mcp::Synthesizer+ that LLM-fills missing server descriptions, a +Pikuri::Mcp::Verifier+ that screens server surfaces for prompt-injection patterns before any tool is advertised to the LLM, and a +Pikuri::Mcp::Extension+ that wires everything into a +Pikuri::Agent+ via +c.add_extension(...)+ in the +Agent.new+ block.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.