AI assistants have become one of the main doors through which people reach information. This week we opened our own data to that door: MetalTakip, the live Turkish gold-market platform we build and operate, now runs an MCP server. As far as we know, it is the first gold-market MCP server in Turkey.
What shipped
MCP (Model Context Protocol) is the open standard that lets AI assistants connect to external data sources. Anthropic open-sourced it in November 2024; in December 2025 it moved under the Linux Foundation, with every major AI vendor backing it. Our server is keyless, stateless and read-only. Connect Claude, or any assistant that supports custom MCP connectors, and it can:
- pull the engine’s latest daily market digest,
- query derived indicators we compute ourselves: the physical gold premium, quarter-coin and PAXG premiums, gold/silver and gold/bitcoin ratios, year-over-year physical flow changes,
- search and fetch from our public analysis archive.
No sign-up, no API key, no write access.
The part we actually care about: what it refuses to serve
Building the endpoint was the easy half. The half that took thought was encoding the boundaries:
- No raw third-party data leaves the server. Our upstream providers license data to us, not through us; redistribution limits are enforced in code, not in a policy document.
- Only our own content and our own calculations are served: the digests our engine writes, the ratios and premiums we derive.
- Every output is informational. The server carries the same regulatory line our platform does: market information, never investment advice.
This is the same discipline that runs our Content Engine, which has published autonomously on MetalTakip since July 2026: the rules are not a review step bolted on at the end; they are part of the machine. When we say “governed engines,” this is what we mean, and the MCP server is a small, public, verifiable example of it. You do not have to take our word for any of this; connect an assistant and inspect what comes back.
Why this matters beyond one endpoint
Two reasons. First, agent-ready is becoming a real property of products. Assistants increasingly act on users’ behalf, and data that can be queried cleanly, inside known limits, will simply be used more than data that cannot. Second, for our clients: the engines we build for brands can expose their outputs the same way, to the client’s own AI stack, under the client’s own rules. The gold-market server is our proof that we run this pattern on ourselves first.
Try it
Add https://www.metaltakip.com/api/mcp as a custom connector in an MCP-capable assistant and ask it, for example, for today’s physical premium or the current gold/bitcoin ratio. MetalTakip’s own launch write-up (in Turkish) walks through the setup step by step. It is a V0: scope is deliberately narrow, and feedback is welcome.
Yusuf Oskay Dağlı is the founder of Find Below, which builds and runs governed autonomous engines for content and ad spend.