Merchantry.
For agents

Give the modelyour side.

these systems talk to Claude directly, so it answers from your record instead of a guess.

each one speaks MCP, the protocol agents use to reach a tool. you paste an address and a token into Claude, Codex, or anything else that supports it, and the model can query your data the same way you can. nothing gets copied anywhere. the agent reads through the same permissions your account already has.

Addresses

Network Intelhttps://netintel-mcp.merchantry.systems/mcp
Your real network, enriched and queryable.
Tidbitshttps://tidbits.merchantry.systems/mcp
Free/OSS-first tools when agents get stuck.
Knowledge Editionshttps://knowledge.merchantry.systems/mcp
Evidence-bound public knowledge for agents and people.

The config

Mint a token on your account page, then drop this into your MCP client. Every system you have access to goes in the same block.

{
  "mcpServers": {
    "netintel": {
      "url": "https://netintel-mcp.merchantry.systems/mcp",
      "headers": { "Authorization": "Bearer mk_YOUR_TOKEN" }
    },
    "tidbits": {
      "url": "https://tidbits.merchantry.systems/mcp",
      "headers": { "Authorization": "Bearer mk_YOUR_TOKEN" }
    },
    "knowledge-editions": {
      "url": "https://knowledge.merchantry.systems/mcp",
      "headers": { "Authorization": "Bearer mk_YOUR_TOKEN" }
    }
  }
}

The token starts with mk_ and only reaches the systems you already have. Revoke it on the same page and the agent loses access immediately. In Claude you can skip the token entirely: add the address under Settings, Connectors, Add custom connector, and it will open a browser window to sign you in instead.

What to ask it

The point is that these answer from your record rather than from training data, so the useful questions are the ones a general model cannot answer at all.

p.s. if a system is not listed here, it has no agent surface yet.

✂ need one for your own data?

This is the part I get hired for.

The hard bit is never the protocol. It is deciding what an agent should be allowed to see, and building the layer that answers honestly.

Beware the defaultMerchantry, by Zain Merchant