Allow MCP clients to supply their own Blockscout PRO API key#400

Merged

akolotov merged 14 commits into

mainfrom

claude/angry-franklin-4316be

Jun 5, 2026

Commits on Jun 5, 2026

Phase 1: Add the pro_api_key_header configuration setting

akolotov
and
claude
committed
Phase 2: Create the pro_api_key_context module

akolotov
and
claude
committed
Phase 3: Apply the pro_api_key_scope decorator to all tools

akolotov
and
claude
committed
Phase 4: Resolve the effective key across the PRO API request paths

akolotov
and
claude
committed
Phase 5: Inject auth at request time in the Web3 pool

akolotov
and
claude
committed
Phase 6: Integration test - a resolved client key against the live PRO API

akolotov
and
claude
committed
Phase 7: Documentation and version bump

akolotov
and
claude
committed
Address review feedback on client-supplied PRO API key flow

akolotov
and
claude
committed
docs: clarify PRO API key authorizes upstream requests, not MCP access

akolotov
and
claude
committed
docs: condense PRO API auth section to high-level guarantees

akolotov
and
claude
committed
test: address code review feedback on PRO API key tests

akolotov
and
claude
committed
chore: bump version to 0.16.0.dev16

akolotov
and
claude
committed
chore: bump version to 0.16.0.dev16 in server.json

akolotov
and
claude
committed
Merge branch 'main' - resolve conflicts keeping dev16 and combining both test sections

akolotov
and
claude
committed