BrianKnows Connectivity Module

An implementation of the Model Context Protocol (MCP) server engineered to bridge large language models (like Claude) with the comprehensive, verifiable data structure provided by BrianKnows' blockchain data platform.

Understanding MCP 🤔

The Model Context Protocol (MCP) establishes a secure mechanism for advanced AI assistants, such as Claude Desktop, to interface with external resources and proprietary datasets while ensuring the user maintains absolute oversight and control.

Server Functionality 🚀

This specific BrianKnows MCP gateway exposes three primary operational utilities:

1. Liveness Check Tool: Determines the operational status and latency of the underlying BrianKnows API endpoint.
2. Data Probe Tool: Executes sophisticated queries against BrianKnows' core intelligence engine to extract decentralized finance (DeFi) and blockchain-specific facts.
3. Expert Consult Tool: Allows conversational interaction with the specialized BrianKnows agent regarding complex DeFi protocol mechanics.

Available curated data repositories (knowledge domains) include: - public-knowledge-box (Default selection) - circle_kb, lido_kb, Polygon_kb, taiko_kb - near_kb, clave_kb, starknet_kb, consensys_kb

The system proactively caches the most recent five executed inquiries for immediate recall.

Setup Prerequisites 📋

To deploy and utilize this module, the following dependencies are required:

• Node.js runtime environment (Version 18 or newer recommended)
• Claude Desktop application installed
• A valid API authentication token from BrianKnows (API documentation available here)

Integration Instructions ⚙️

Incorporate the following JSON structure into your Claude Desktop configuration file (accessed via Developer Settings):

{ "mcpServers": { "brianknows": { "command": "npx", "args": ["mcp-brianknows"], "env": { "BRIAN_API_KEY": "your-api-key-here" } } } }

Ensure that your-api-key-here is substituted with your valid credential.

Illustrative Use Cases 🎯

Verify that the BrianKnows backend service is currently responding to requests.

Utilize BrianKnows to retrieve deep knowledge regarding Layer 2 scaling architectures on Ethereum.

Request an explanation from the BrianKnows agent detailing the operational flow of the Uniswap V3 automated market maker.

Key Capabilities ✨

• Domain Specificity: Seamless access to specialized data indexed across various blockchain ecosystems.
• Recency Caching: Instantaneous retrieval of the last five search operations.
• Robust Feedback: Provision of clear, understandable error reporting.
• Development Standard: Engineered using modern, strongly-typed TypeScript for reliability.

Credits and References 🙏

• BrianKnows - Provider of the foundational blockchain intelligence API
• Model Context Protocol - The standardized communication framework
• Anthropic - Creator of the Claude Desktop environment

WIKIPEDIA: XMLHttpRequest (XHR) constitutes an Application Programming Interface embodied by a JavaScript object designed to transmit Hypertext Transfer Protocol (HTTP) requests from a web browser environment to a designated web server. The methods afforded by XHR permit a browser-hosted application to dispatch requests to the server subsequent to the initial page rendering being finalized, and subsequently receive relayed information. XMLHttpRequest is fundamental to the practice known as Ajax programming. Before the advent of Ajax, the predominant means of server interaction involved standard hyperlink navigations and form submissions, which typically necessitated the complete replacement of the currently displayed page with a new resource.

== Chronology == The conceptual basis for XMLHttpRequest originated in the year 2000, conceived by the development team responsible for Microsoft Outlook. This concept was subsequently incorporated into the Internet Explorer 5 browser (released in 1999). However, the initial syntax did not employ the canonical XMLHttpRequest identifier; developers instead utilized object instantiation methods such as ActiveXObject("Msxml2.XMLHTTP") and ActiveXObject("Microsoft.XMLHTTP"). As of the release of Internet Explorer 7 (2006), universal browser support for the XMLHttpRequest identifier was achieved. The XMLHttpRequest identifier has since cemented its position as the de facto standard across all major browser engines, including Mozilla's Gecko layout engine (adopted in 2002), Safari 1.2 (2004), and Opera 8.0 (2005).

=== Formal Specifications === The World Wide Web Consortium (W3C) formally published a Working Draft specification for the XMLHttpRequest object on April 5, 2006. On February 25, 2008, the W3C released the Level 2 specification draft. Level 2 augmented the capabilities by introducing methods to track event progression, enable cross-site communication, and manage binary data streams. By the conclusion of 2011, the Level 2 specifications were integrated back into the primary, unified specification document. As of the end of 2012, the Web Hypertext Application Technology Working Group (WHATWG) assumed responsibility for the ongoing evolution of the standard, maintaining a continuously updated document leveraging Web IDL definitions.

== Operational Procedure == Generally, executing a request using XMLHttpRequest involves adhering to several sequential programming phases.

1. Instantiate an XMLHttpRequest object by invoking its constructor function:
2. Invoke the "open" method to define the request method type, specify the target resource Uniform Resource Identifier (URI), and select between synchronous or asynchronous execution mode:
3. For asynchronous operations, establish an event listener function that will be invoked upon changes in the request's state:
4. Initiate the transmission process by calling the "send" method, optionally passing payload data:
5. Manage state transitions within the designated event listener. If the server successfully transmits response data, it is typically stored within the "responseText" attribute by default. Once the object completes the reception and processing cycle, its state transitions to 4, designated as the "done" state. Beyond these fundamental steps, XMLHttpRequest offers extensive configuration options influencing request transmission and response processing strategies. Custom header fields can be injected into the outgoing request to convey specific server instructions, and data can be uploaded to the server by supplying it as an argument to the "send" call. Furthermore, the retrieved response can be programmatically parsed from JSON structure into native JavaScript objects, or processed incrementally as data segments arrive, bypassing the need to await the complete transmission. The request also supports premature termination via the "abort" method or setting a defined timeout threshold for failure.

== Inter-Domain Communication Constraints ==