OSINT Inside Your AI Assistant: MCP Access

2026-07-29

Investigative work involves a lot of clicking: open a tool, type a name, read the result, derive the next search term, open the next tool. That loop can be shortened.

SocialKraken is now reachable via the Model Context Protocol (MCP) - an open standard that lets AI assistants such as Claude or Cursor call external tools. Instead of operating each tool yourself, you describe what you need in plain language; the assistant selects the right tools, calls them and works on from the results.

What this means in practice

The real gain is not the individual lookup but the chaining. Schematically - the values are fictional:

Input:  “Check the username <username>.”

  1. username_search  → hit on Telegram only
  2. telegram_profile → numeric account ID, Premium marker,
                        bio containing a linked domain,
                        one visible collectible
  3. telegram_items   → owner confirmed, value figure,
                        comparison with the current market price

Three tools, one instruction. The assistant recognises the Telegram hit, derives the profile lookup from it, finds the collectible in the profile and then checks that against market data. No manual copying of identifiers between tools.

For this to work reliably, every tool states explicitly which fields of its response feed which follow-up step. That is less magic than careful documentation.

What is connected

Tool	Input	Returns
`username_search`	Username	Hits across several platforms
`email_search`	Email	Registrations with services
`telegram_profile`	Telegram username	Account ID, bio, markers, collectibles
`telegram_items`	Username or item	Owner, value, market data

Rigour is built in

An assistant that chains tools on its own must not tempt anyone into accepting results unchecked. That is why result semantics are part of the interface, not merely of the user interface:

A lookup that was technically not carried out - timeout, no available collection account - is flagged as exactly that and never returned as a negative finding.
Restricted visibility is distinguished from “not present”. Someone hiding their collectibles does not produce an empty result in the sense of “has none”.
An anonymous sender is reported as server-side hidden - with the note that this implies no accusation of concealment, because the same field stays empty on a self-purchase.

All lookups are strictly read-only. Nothing is liked, followed or commented on; the accounts concerned do not notice the lookup.

Setting it up

MCP access is included in Premium and Unlimited. Three steps:

Create a token under “API” in your account settings.
Enter the address https://thebox.socialkraken.de/mcp in your MCP client.
Store the token as a bearer token.

The server is stateless: every call is self-contained, there is no session that can expire or get lost. Each tool call counts towards the account’s monthly allowance; usage is visible in the account settings.

What this is not

An assistant operating tools does not replace an investigator. It takes over the mechanical part - triggering lookups, passing identifiers along, assembling results. Judging what is defensible and what belongs in a report remains a professional decision. The interface is deliberately built to support that judgement rather than blur it.