Catalysis Hub for Claude Desktop

Created By
QuentinCodya year ago
Overview

What is Catalysis Hub?

Catalysis Hub is a database that provides access to computational catalysis research data, including reaction energetics, surface structures, DFT calculation parameters, and publication metadata. It allows users to interact with this data through Claude Desktop.

How to use Catalysis Hub?

To use Catalysis Hub, set it up in Claude Desktop by editing the configuration file to include the Catalysis Hub server details. After setup, you can ask Claude to query the database for specific information.

Key features of Catalysis Hub?

  • Access to a comprehensive database of catalysis research data.
  • Ability to perform queries using natural language through Claude.
  • Support for GraphQL interface for advanced data retrieval.

Use cases of Catalysis Hub?

  1. Searching for recent publications on specific catalysts.
  2. Analyzing reaction mechanisms and energetics.
  3. Comparing different catalyst materials based on adsorption energies.

FAQ from Catalysis Hub?

  • Can I access all catalysis data through Claude?

Yes, you can query a wide range of data related to catalysis research.

  • What should I do if Claude cannot access Catalysis Hub?

Ensure the configuration is correct and restart Claude Desktop. If issues persist, contact support.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
QuentinCody
Star
0
Language
TypeScript
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

a day ago