Model Context Protocol
Your assistant gets hands.
Never your wallet.
Connect Claude, ChatGPT or Cursor to your Inleed account. Your assistant can read, diagnose and fix with 206 tools — and everything that costs money stops at a confirmation link only you can click.
https://mcp.inleed.com/mcp
claude mcp add --transport http inleed https://mcp.inleed.com/mcp \
--header "Authorization: Bearer $INLEED_TOKEN"// Claude Code, Cursor and VS Code read this shape.
{
"mcpServers": {
"inleed": {
"type": "http",
"url": "https://mcp.inleed.com/mcp",
"headers": { "Authorization": "Bearer inl_live_…" }
}
}
}// Desktop cannot open a streamable-HTTP server from its config file,
// so it goes through the mcp-remote bridge. Or use the connector UI.
{
"mcpServers": {
"inleed": {
"command": "npx",
"args": [
"-y", "mcp-remote", "https://mcp.inleed.com/mcp",
"--header", "Authorization: Bearer inl_live_…"
]
}
}
}Settings → Connectors → Add custom connector
https://mcp.inleed.com/mcp/k/inl_live_…
Claude.ai and ChatGPT cannot attach an Authorization
header, so the token travels in the path instead.
That URL is password-equivalent — treat it as one.
In ChatGPT the "Create" button appears only after
Settings → Connectors → Advanced → Developer mode.
Every one of these needs a token, and the inl_live_… above is a placeholder —
replace it with your own. Mint one under Menu → API access → Create token in
the client area; the Read-only preset is the right first choice.
How tokens work.
No token? Start here
A second MCP server carries the product catalogue, pricing and domain availability. It needs no token and no account, so you can point a client at it and see real tools answer before you sign up for anything.
# No token, no account. Try it right now.
curl -X POST https://mcp.inleed.com/public/mcp \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'https://mcp.inleed.com/public/mcp— no authenticationhttps://mcp.inleed.com/api/public/v1— the same data over REST- /.well-known/mcp.json — machine-readable descriptor, on the API host
What it can and cannot do
Four guarantees that hold no matter what the model decides to try.
Scopes filter the tool list
A tool your token has no scope for is not refused — it is never listed. The model cannot be talked into calling a tool it cannot see.
Absent beats deniedOne scope gates all spending
write:billing is required by every operation that can create a charge. Withhold it and nothing on the token can spend, whatever the model tries.
The money gateMoney stops at a link
Anything that costs money or cannot be undone returns a confirmation link instead of executing. You approve it in the client area, signed in, against a preview the model did not write.
ConfirmationsInjected text is data, never instructions
A TXT record or a log line can say “ignore previous instructions”. The defence is scope filtering, ownership checks and the confirmation tier — not a text filter.
Why out of band