Other · Remote MCP server
Rarefied Earth Groundwork MCP
Rarefied Earth Groundwork MCP: company memory for AI agents. 14-day full-access trial, no card.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.Rarefied-Earth/groundwork- Version
- 1.7.1
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP
- Published
- 2026-07-31
- Updated
- 2026-07-31
- Publisher
- Rarefied-Earth (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/Rarefied-Earth) · how
- Website
- rarefied.earth/groundwork
- Repository
- github.com/Rarefied-Earth/groundwork
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://connector.rarefied.earth/public/mcp | None |
| Streamable HTTP | https://connector.rarefied.earth/mcp | Authorization (required, secret) |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Endpoint
https://connector.rarefied.earth/public/mcp(HTTP)- Reachable
- Yes (HTTP 503)
- Handshake
- HTTP 503
- Checked on
- 2026-10-05
- Endpoint
https://connector.rarefied.earth/mcp(HTTP)- Reachable
- Yes (HTTP 503)
- Handshake
- HTTP 503
- Checked on
- 2026-10-05
How to connect Rarefied Earth Groundwork MCP
Rarefied Earth Groundwork MCP is a remote MCP server: there is nothing to install. Its endpoints are https://connector.rarefied.earth/public/mcp and https://connector.rarefied.earth/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The registry entry declares an HTTP header for the connection: Authorization (required, secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More other servers
| Server | Runs |
|---|---|
| Ranomics PlatformWet-lab triage for AI binder-design agents. Yeast display, mammalian display, DMS at library scale. | Remote · HTTPLive check: ✓ handshake |
| RapierMarkdown editor in one offline HTML file: the agent edits passages, you keep or drop each change. | Remote · HTTPLive check: ✓ handshake |
| Raposa Aval - human approvalHuman approval for AI agents: a named person approves or rejects, silence is not consent. | Local · stdio |
| RapportscoreConversational AI Coaching from calls; permissioned Team Dynamics reports in a limited U.S. pilot. | Remote · HTTPLive check: sign-in required |
| RatchetYour agent asks before it acts, so the same real-world action is attempted at most once. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| rawmemRead-only MCP access to a local append-only evidence ledger for AI agent sessions. | Local · stdio |
| Raza SORRaza Rizwan's record: ask how much of your workflow AI can automate; governed, cited answers. | Remote · HTTPLive check: sign-in required |
| RazeExplore Raze services, pricing, projects, availability, and confirmed introduction bookings. | Remote · HTTPLive check: ✓ handshake |