Inside an MCP Server: How entity-intel-mcp Works
Ten tools, seven sources, and a gap is never reported as a no.
Video #331 ยท AI agents and MCP
Steps in the video
- 0:00 Ten tools, seven sources, and a gap is never reported as a no
- 0:26 The idea
- 0:50 Setup
- 1:07 A client in forty lines
- 1:24 Connect
- 2:01 The server assembly
- 2:18 One envelope for every answer
- 2:36 An adapter is one register
- 2:56 Failure is never a fact
- 3:17 Merging with provenance
- 4:39 Use it from a client
- 5:04 The order of calls
- 5:26 What this does not show
- 5:41 Mistakes to avoid
- 6:06 My take and next steps
- 6:23 Recap
Files
- adapter.ts (70 lines)
- availability.ts (15 lines)
- claude_config.json (13 lines)
- client.py (55 lines)
- envelope.ts (66 lines)
- pick.ts (29 lines)
- rec_entity.json (283 lines)
- rec_norway.json (25 lines)
- rec_ownership.json (187 lines)
- server.ts (42 lines)
- show.py (49 lines)
Tested with
Python 3.12.15
What this does not show
Lookups are answers recorded from one live run on 14 November 2026 (public data, one UK group and one Norwegian company); officer lookups and sanctions screening are not shown; the newest MCP spec read has dropped the initialize handshake this server still uses.
Sources
- https://modelcontextprotocol.io/specification/2026-07-28/basic/transports/stdio.md
- https://modelcontextprotocol.io/specification/2026-07-28/basic/versioning.md
- https://modelcontextprotocol.io/specification/2026-07-28/server/tools.md
- https://www.gov.uk/government/publications/people-with-significant-control-summary-guidance/summary-guidance-for-companies-register-of-people-with-significant-control-pscs
Learning IT by Example.