Skip to content
Back to the index

smithsonian

pipeworx.ioInfrastructure

No liveness check has reached it yet; it has been in the index since 10 Oct 2026. How this is checked

Smithsonian is a hosted MCP server that exposes search and object-retrieval tools for the Smithsonian Open Access collection. Developers and AI agents can call its JSON-RPC endpoint to find collection items and fetch detailed metadata, creators, dates, and image links.

Inferred · not functionally tested

WebAPICloud-managed
smithsonian preview
Visit pipeworx.io

Overview

6 features

Purpose: Accessing and retrieving Smithsonian Open Access collection data through an AI-agent-compatible interface.

Inferred · not functionally tested

Audience: developers building AI agents and data applications

Inferred · not functionally tested

Functions: data_extraction

Inferred · not functionally tested

Interfaces: API: indicated (inferred, not tested) · MCP: indicated (inferred, not tested) · CLI: unknown · Self-hosting: unknown

Recorded constraints: pricing: unknown · license: Proprietary · platforms: WEB · deployment: browser, api_only, cloud_managed

Constraint provenance is unknown; confirm requirements with the publisher.

Record sources: gateway.pipeworx.io. These links do not verify the individual claims.

In the API design, testing & docs space, smithsonian takes a focused approach. Inferred · not functionally tested: It focuses on accessing and retrieving Smithsonian Open Access collection data through an AI-agent-compatible interface. Inferred · not functionally tested: It is built as a B2B product for developers building AI agents and data applications. Basis unknown · not verified: It runs on the web and API.

Pipeworx builds and maintains smithsonian. Inferred · not functionally tested: Among its 6 catalogued features are collection search, object retrieval, and JSON-RPC endpoint. Inferred · not functionally tested: Catalogued interfaces include an MCP server and a public API.

Summary written by a language model from the project’s public pages.

Tasks: Inferred · not functionally tested

  • Collection search
  • Object retrieval
  • JSON-RPC endpoint
  • MCP tools
  • Image links
  • Live playground

Topics: Inferred · not functionally tested

Tags
smithsonian-open-accessmcp-servercultural-heritage-dataai-agent-tools

JSON profile · Text profile · Access guide

Built with & integrations

Hosting
Cloudflare
Connectors
MCPAPI
Runs on
BrowserAPI-onlyCloud-managed
Detected from
Cloudflare
cf-ray header

Trust & compliance

Public signals
HTTPS

Indexing history

1

What PulseGate has recorded for this listing

  1. Indexed10 Oct · 00:02 UTC
    Smithsonian seen via MCP Registry (official)
    Source: MCP Registry (official) · Open

Frequently asked questions about smithsonian

What does smithsonian do?
Inferred · not functionally tested: Smithsonian focuses on accessing and retrieving Smithsonian Open Access collection data through an AI-agent-compatible interface. It is catalogued under API design, testing & docs on PulseGate.
Who should use smithsonian?
Inferred · not functionally tested: smithsonian is a B2B product built for developers building AI agents and data applications.
What platforms does smithsonian run on?
Basis unknown · not verified: smithsonian runs on the web and API.
Is smithsonian still active?
Unverified. smithsonian has not been re-checked since it entered the index, so there is no finding either way — and only a positive finding would say otherwise.
What projects are similar to smithsonian?
Similar projects tracked by PulseGate include snb-ch, solscan, and social-signal.snb-chsolscansocial-signal
Who develops smithsonian?
smithsonian is developed by Pipeworx.
Does smithsonian have an API or integrations?
Inferred · not functionally tested: Yes — smithsonian exposes an MCP server and a public API.

Also in API design, testing & docs

Same category — not a similarity match