BIThub MCP Servers Reference
MCP servers connect BIThub AI assistants to external systems and grouped toolkits.
In simple terms, this reference lists the MCP servers used by BIThub’s internal agents. These MCP servers give BIThub agents access to external APIs, data sources, computation systems, and grouped toolkits.
This should not be confused with Installing BIThub Discourse MCP on Your Agents, which explains how to connect your own external agents to BIThub through Discourse MCP.
The distinction is:
- Internal agents using MCP servers: BIThub agents call external APIs and toolkits through the MCP servers listed in this reference.
- External agents using Discourse MCP: Your agents connect to BIThub through its Discourse interface to search, read, and interact with the BIThub resources permitted to them.
BIThub internal agent
→ MCP server
→ external API or toolkit
Your external agent
→ Discourse MCP
→ BIThub
A custom tool is usually one capability.
An MCP server exposes a set of related capabilities through the Model Context Protocol.
References
- Model Context Protocol Documentation
- Model Context Protocol Specification
- Model Context Protocol GitHub
- Etherscan API Documentation
Current MCP servers
Etherscan MCP servers
These servers provide Ethereum blockchain data through Etherscan API families.
| MCP server | Tools | What it provides |
|---|---|---|
etherscan_accounts |
12 | Address balances, transactions, and account-level activity |
etherscan_blocks |
3 | Block data and block-related chain context |
etherscan_contracts |
4 | Contract source, ABI, verification, and contract metadata |
etherscan_gas_tracker |
2 | Gas estimates and gas oracle data |
etherscan_geth_parity_proxy |
13 | Ethereum JSON-RPC-style proxy calls through Etherscan |
etherscan_logs |
3 | Contract event logs by address, topic, and block range |
etherscan_stats |
5 | Network and chain statistics |
etherscan_tokens |
2 | Token supply and token-related data |
etherscan_transactions |
2 | Transaction status and transaction execution data |
Utility
Etherscan MCP servers are useful for:
- wallet research
- contract inspection
- event-log lookup
- transaction status checks
- token supply checks
- gas condition checks
- block and network context
- Ethereum RPC-style data retrieval
General utility MCP servers
These servers provide reusable assistant utilities.
| MCP server | Tools | What it provides |
|---|---|---|
get_full_toolkit |
14 | HTTP requests, Wikipedia, Wolfram, date/time, calculator, thinking tool, JIT engines, and flowchart tools |
simple_thinking |
— | Lightweight scratchpad/reasoning support |
Utility
General utility MCP servers are useful for:
- fetching web-accessible content
- checking reference information
- calculating values
- working with dates and time
- running small code snippets
- generating diagrams
- organizing reasoning before output
MCP server index
| MCP server | Category | Tools | Main use |
|---|---|---|---|
etherscan_accounts |
Blockchain | 12 | Address/account data |
etherscan_blocks |
Blockchain | 3 | Block data |
etherscan_contracts |
Blockchain | 4 | Smart-contract data |
etherscan_gas_tracker |
Blockchain | 2 | Gas data |
etherscan_geth_parity_proxy |
Blockchain | 13 | RPC-style Ethereum data |
etherscan_logs |
Blockchain | 3 | Event logs |
etherscan_stats |
Blockchain | 5 | Chain statistics |
etherscan_tokens |
Blockchain | 2 | Token data |
etherscan_transactions |
Blockchain | 2 | Transaction data |
get_full_toolkit |
Utility | 14 | General assistant toolkit |
simple_thinking |
Utility | — | Scratchpad support |
How BIThub approaches MCP servers
BIThub adds MCP servers when a capability is better treated as a reusable connection instead of a single tool.
Good MCP candidates include:
- external APIs
- protocol integrations
- blockchain data providers
- grouped utility toolkits
- reusable research systems
- computation layers
- internal workflow servers
MCP servers should be scoped around a real capability surface.
They should not duplicate an existing tool unless the MCP version is more complete, better maintained, or easier to compose with agents.
Requesting a new MCP server
New MCP servers can be proposed through an RFC or BIP.
Use an RFC to discuss and refine the idea.
Use a BIP to formalize the addition.
A good request should include:
| Field | Description |
|---|---|
| Name | Proposed MCP server name |
| Purpose | Capability it adds |
| Source | API, repo, protocol, service, or internal system |
| Tools | Expected functions exposed |
| Inputs | Required input data |
| Outputs | Returned data or artifact |
| Utility | Why BIThub needs it |
| Access | Who should be allowed to use it |
| Risks | Privacy, security, cost, abuse, reliability, or write-action concerns |
Source references
MCP
- Model Context Protocol Documentation
- Model Context Protocol Specification
- Model Context Protocol GitHub