Summary
Protocol answers with a knowledge base behind them.
DeFi mechanics change faster than any model's training data, which is exactly where a curated knowledge base earns its place. The protocol-specific bases matter more than the default one: asking a Lido question against the Lido base returns a narrower, more current answer than a general search. The ping tool is worth using first when a search comes back thin, so you can tell an empty result from an unreachable API.
What it is
A Node MCP server that connects a client to BrianKnows' blockchain knowledge engine, so questions about protocols are answered from a curated knowledge base.
What you get
- A ping tool, for checking the BrianKnows API is responsive before you trust an empty answer
- A search tool, querying the knowledge engine for blockchain and DeFi information
- An agent tool, for a conversation with the BrianKnows agent about DeFi protocols
- A choice of knowledge base: public-knowledge-box by default, plus protocol-specific ones for Circle, Lido, Polygon, Taiko, NEAR, Clave, Starknet and Consensys
- A cache of your 5 most recent searches, for going back to a result without re-querying
Requirements
Node.js v18 or higher and a BrianKnows API key in `BRIAN_API_KEY`. The README's client entry names `mcp-brianknows`, which npm does not have.