Model Context Protocol

Put NetX data
inside your LLM.

Every daily report and every library document is exposed over MCP, so Claude, ChatGPT, Grok or your own agent can query them directly — no scraping, no copy-paste, no stale context. One endpoint, eight tools.

https://mcp.telnetx.com/mcpSetup guides

Access is issued per client — requests open soon.

Why connect it

Grounded, not guessed Answers come from the actual daily reports — metrics, risk scores and written summaries — instead of whatever the model remembers about NetX.
Reports carry guidance Each report ships an llm_guidance block telling the model how to read it — what the numbers mean, and what not to over-claim from them.
Served from the edge The MCP surface reads a published edge store, not the machines that generate the reports — so it stays up even when generation is down.
Full history Not just today. Ask for a specific date, or list back through the archive to compare how a metric moved.

Tools

Eight tools over two data sets — the daily report pipelines and the research library.

Daily reports

ToolArgumentsWhat it returns
list_report_domains—List every report domain available. Call this first when unsure which domain to use.
list_reportsdomain, network?, limit?Recent reports for one domain, newest first, as lightweight summaries.
get_reportdomain, network?, dateFull report for one domain on a specific UTC date, including its llm_guidance block.
get_latest_reportdomain, network?Most recent report for one domain, same full content as get_report.

NetX Library

ToolArgumentsWhat it returns
list_library_documents—Every analyzed document in the research corpus — id, title, date, novelty score, digest headline.
get_library_documentidThe full three-pass analysis (critique, report, digest) for one corpus document.
get_library_synthesis—The single holistic synthesis across the whole corpus — cross-document claims, contradictions, open risks.
get_library_context_pack—Curated glossary, canonical facts and guardrails, meant to be attached to an LLM session.

Domains

The domain argument on the four report tools accepts these five keys.

KeyPipelineExtra argument
networkNetwork Healthrequires network: mainnet | testnet
socialX (Twitter) Activity—
bscBSC On-Chain Activity—
communityTelegram Community—
pricePrice & Market—

Authentication

Two ways in, depending on what your client supports. Both are unlocked by the same wallet sign-in.

Bearer token Send Authorization: Bearer <token> on every request. Simplest path — used by mcp-remote bridges and clients that allow custom headers.
OAuth 2.1 Full authorization-code flow with PKCE and dynamic client registration, for connectors that only speak OAuth. You approve access by signing with your wallet on the consent screen.
Access is not open to the public yet. The endpoint is live, but both the bearer token and the OAuth consent passcode are issued per client. Wallet-based self-service key issuance is in testing — the setup guides below are here so you know what to expect when it opens.

Integrations

The endpoint speaks Streamable HTTP, so anything MCP-compatible can connect.

Claude, ChatGPT & Grok — remote connector

In your client's connector settings, add a custom/remote MCP server and paste the endpoint URL. The client discovers the OAuth flow automatically and walks you through the consent screen.

  1. Open connector settingsSettings → Connectors (Claude), or the equivalent MCP/custom-connector panel in your client.
  2. Add the endpointPaste https://mcp.telnetx.com/mcp as the server URL. Leave the transport on the default (Streamable HTTP).
  3. Authorize The client redirects you to a consent screen. Enter the passcode you were issued and approve.
  4. Ask somethingTry "what does the latest NetX mainnet report say about risk?" — the model picks the tool itself.

Local clients — via mcp-remote

For clients that only launch local stdio servers, bridge with mcp-remote and pass the bearer token as a header.

claude_desktop_config.json
{
  "mcpServers": {
    "netx-daily-reports": {
      "command": "npx",
      "args": [
        "-y", "mcp-remote",
        "https://mcp.telnetx.com/mcp",
        "--header", "Authorization:Bearer ${MCP_TOKEN}"
      ],
      "env": { "MCP_TOKEN": "<your token>" }
    }
  }
}

Anything else — raw JSON-RPC

The endpoint is a plain POST. List the tools to check your credentials work:

tools/list
curl -X POST https://mcp.telnetx.com/mcp \
  -H "Authorization: Bearer $MCP_TOKEN" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

…then call one:

tools/call
{
  "jsonrpc": "2.0",
  "id": 2,
  "method": "tools/call",
  "params": {
    "name": "get_latest_report",
    "arguments": { "domain": "network", "network": "mainnet" }
  }
}
Prefer plain HTTP? The same reports are available over a read-only REST API. Endpoints and data shapes are in the docs.
Read the docs