Data Collection

scigantic.com

A search and discovery tool for public scientific data archives, providing metadata, schema cards, data access instructions, and file listings.

1 endpoint8 known toolsFirst detected September 24, 2026Last detected September 24, 2026

ENDPOINT 1

https://api.scigantic.com/mcp

No auth detected

MCP server metadata

Name: scigantic
Version: 0.1.0

Capabilities

toolsprompts

Server instructions

Scigantic exposes a catalog of public scientific data archives. Use search_archives to find datasets, get_schema_card to understand a dataset's structure, list_archive_files to inspect contents, and get_sample_notebook for a worked example. lookup_paper goes from a paper to its underlying datasets.

Known tools 8

search_archives

Search the Scigantic catalog of public scientific data archives by natural-language query.

Inferred read-only

get_archive

Get full metadata for one archive by id, including its schema card (structure summary) when one exists.

Inferred read-only

get_schema_card

Get the compact schema card for an archive: file format, columns, sample rows/headers, sidecar docs (READMEs/data dictionaries) and a copy-paste starter cell.

Inferred read-only

get_data_access

Get how to load a dataset in YOUR OWN environment: storage location plus copy-paste code snippets (from the dataset's schema card, or generated as a fallback).

Inferred read-only

list_archive_files

List a sample of the files/objects in an archive's storage (the cached file tree).

Inferred read-only

get_sample_notebook

Get the pre-executed starter notebook for an archive — a worked example of loading and exploring the data.

Inferred read-only

lookup_paper

Resolve a research paper (by arXiv id, DOI, URL, or title) and return its metadata plus any Scigantic archives linked to or suggested by it.

Inferred read-only

list_compute_tiers

List the compute tiers available for launching a Scigantic notebook (CPU/GPU options and hourly cost).

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.scigantic]
url = "https://api.scigantic.com/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "scigantic": {
      "type": "http",
      "url": "https://api.scigantic.com/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: scigantic
Remote MCP URL: https://api.scigantic.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "scigantic": {
      "url": "https://api.scigantic.com/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "scigantic": {
      "type": "http",
      "url": "https://api.scigantic.com/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "scigantic",
  "transport": "streamable-http",
  "url": "https://api.scigantic.com/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.