Other · Remote MCP server
Meniscus
Liquid glass design system for AI agents: specs, recipes and reference renders for every platform.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
site.meniscus/meniscus- Version
- 3.0.0
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP
- Published
- 2026-09-27
- Updated
- 2026-09-27
- Publisher
- site.meniscus
- Namespace
- Namespace verified by the MCP Registry via the domain meniscus.site · how
- Website
- meniscus.site
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://meniscus.site/mcp | None |
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.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
How to connect Meniscus
Meniscus is a remote MCP server: there is nothing to install. Its endpoint is https://meniscus.site/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.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
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
Site checks
The website's own root, meniscus.site, was checked for the files that tell AI systems about a site.
| File | Result |
|---|---|
/llms.txt | Real file, HTTP 200 · 2026-10-04 |
/.well-known/mcp.json | No real file found |
/.well-known/ai-plugin.json | No real file found |
/agents.json | No real file found |
More other servers
| Server | Runs |
|---|---|
| MemxusPersistent memory layer that saves and recalls your project context and preferences. | Remote · HTTPLive check: ✓ handshake |
| MencoroTrack and manage how your brand appears in AI answers: rank, mentions, sentiment, share of voice. | Remote & Local · HTTP, stdioLive check: sign-in required |
| MendriftMCP server for ML drift detection, MLflow registry diffing, and HMAC-gated model rollback. | Local · stdio |
| MengramLong-term memory for AI agents: semantic facts, episodic events, and procedural workflows. | Remote · HTTPLive check: sign-in required |
| MenloComplete a Menlo application, authorize carrier quote requests and answer quote follow-ups. | Remote · HTTPLive check: ✓ handshake |
| Menor Preço Hoje - MPHPreços e ofertas locais em Lages via MCP para consumidores e agentes de IA. | Remote · HTTPLive check: ✓ handshake |
| MentionAgentLink building outreach from your agent: review drafts, send the batch, answer publisher replies. | Remote · HTTPLive check: sign-in required |
| MentionedOn Discovery Evidence ToolsAssess AI-discovery readiness, plan visibility fixes, and summarize scan evidence. Read-only. | Remote · HTTPLive check: ✓ handshake |