Use Deeptech Navigator inside your AI tools

What you get

• Without a token (anyone): the public picture — national overview, sector deep-dives, technology trends, city rankings, top patent filers, recently funded startups, and search across the free kinds.
• With a token: everything your plan already includes on the website — the startup directory and full profiles with funding rounds (Startup Explorer), patent-filer profiles, filing lists, full patent records and inventor search (Technical Insights), plus investor and ecosystem lookups (any paid plan).

The endpoint is https://mcp.deeptechnavigator.com/mcp. A token never expands what you can see — it simply lets an AI tool use the access you already have.

Step 1 — create your token

Go to your account page and use Connect AI tools (MCP) → Create token. The token (it starts with dtn_) is shown once — copy it immediately. Treat it like a password: anyone holding it can spend your daily data budget. If it leaks, revoke it on the same page; revocation takes effect on the next call. One token works from all your devices at once, and you can hold up to five (e.g. one per tool) so revoking one never locks out the rest.

Step 2 — connect your client

Claude (claude.ai and the desktop app)

1. Open Settings → Connectors → Add custom connector (custom connectors are available on paid Claude plans).
2. Name it Deeptech Navigator, then paste one of these as the URL:
   • Full access — your token embedded in the address: https://mcp.deeptechnavigator.com/t/dtn_…your token…/mcp
   • Free tools only — https://mcp.deeptechnavigator.com/mcp
3. Leave Advanced settings blank and click Add.

The two boxes under Advanced settings are an OAuth login, not a header name/value pair. Unlike Manus or Cursor, Claude has nowhere here to put a header — so do not type Authorization in the first box or your token in the second. Filling one gives “A client id must be provided with a client secret”; filling both sends you to a login page that doesn’t exist (Cannot GET /authorize). Leave both empty and put the token in the URL. Because that address contains your token, treat the whole link like a password — never paste it into a shared chat or screenshot it, and revoke the token if it leaks.

Some Claude accounts show a Request headers section under Advanced settings (a gradual rollout). If yours does, you can instead use the plain endpoint with the header Authorization set to Bearer dtn_…your token…, which keeps the token out of the URL.

Claude Code (terminal)

claude mcp add --transport http deeptech https://mcp.deeptechnavigator.com/mcp \
  --header "Authorization: Bearer dtn_…your token…"

Cursor

Add to ~/.cursor/mcp.json(or the project’s .cursor/mcp.json):

{
  "mcpServers": {
    "deeptech": {
      "url": "https://mcp.deeptechnavigator.com/mcp",
      "headers": { "Authorization": "Bearer dtn_…your token…" }
    }
  }
}

VS Code (Copilot agent mode)

Add to .vscode/mcp.json:

{
  "servers": {
    "deeptech": {
      "type": "http",
      "url": "https://mcp.deeptechnavigator.com/mcp",
      "headers": { "Authorization": "Bearer dtn_…your token…" }
    }
  }
}

Windsurf

Add to ~/.codeium/windsurf/mcp_config.json with the same url + headers shape as Cursor above.

Manus

In the MCP configuration dialog set Transport Type to HTTP, Server URL to https://mcp.deeptechnavigator.com/mcp, then add a custom header with name Authorization and value Bearer dtn_…your token….

The value must start with Bearer (with the space).A bare token in that box is not recognised as a login, so the connector quietly falls back to free access and every paid result comes back as “locked” — it looks like your token failed when the header simply wasn’t read.

ChatGPT

ChatGPT’s connector form has no header field, so there are two honest options:

• Free tools, no token: add a connector with authentication set to None and the URL https://mcp.deeptechnavigator.com/mcp.
• Full access: embed the token in the URL: https://mcp.deeptechnavigator.com/t/dtn_…your token…/mcp. That URL is your token — treat the whole link like a password, never share a screenshot of it, and revoke the token if the link ever leaks.

Anything else

Any client that speaks MCP over Streamable HTTP works: point it at https://mcp.deeptechnavigator.com/mcp and send Authorization: Bearer dtn_… if it supports custom headers.

Step 3 — ask real questions

• “Which Indian cities lead in space-tech startups, and who are the top filers there?”
• “Find startups working on solid-state batteries and show their funding history.”
• “List IIT Madras’s recent patent filings and summarise what they cover.”
• “Which technologies are accelerating fastest in filings since 2022?”
• “Profile this investor and show their deep-tech portfolio.”

Answers cite Deeptech Navigator as the source, and IP links carry the same caveat as the site: name-matched candidates, not verified ownership records.

Fair use & troubleshooting

• Your daily fair-use budget is shared between the website and every connector — it meters what you fetch, not how many devices you connect.
• “A client id must be provided with a client secret” or “Cannot GET /authorize”(Claude): your token went into the OAuth boxes. We don’t use OAuth — remove the connector, add it again with the token in the URL, and leave Advanced settings empty.
• 401 / “invalid token”: the token was mistyped, revoked, or expired — mint a fresh one on /account.
• Connected, but everything comes back “locked” or only the free tools appear:your token isn’t reaching us. In a header-based client the value must read Bearer dtn_… — a bare token, or a token in an OAuth field, is ignored and you get anonymous access. Check that first; if the client lists only 8 tools instead of 16, that confirms it.
• A “teaser” answer with an upgrade note:your account doesn’t currently include that plan — the connector mirrors website access exactly, live on every call.
• “Daily fair-use limit reached”: access resumes automatically within 24 hours; ask us if your work needs more.
• “temporarily disabled” (503): brief maintenance on our side — no action needed.