Developer · Remote MCP server
Semilattice - audience prediction
Semilattice lets agents make predictions about audiences for content testing and decision making.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.semilattice-research/mcp- Version
- 0.1.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2025-11-19
- Updated
- 2025-11-19
- Publisher
- semilattice-research (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/semilattice-research) · how
- Website
- semilattice.ai
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.semilattice.ai | 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 Semilattice - audience prediction
Semilattice - audience prediction is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.semilattice.ai, 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
More developer servers
| Server | Runs |
|---|---|
| SemamergeDetects semantic merge conflicts between Git branches using AST-level analysis. | Local · stdio |
| semantic-scalaBounded Scala compiler, build, test, type, effect, symbol, and SemanticDB evidence for agents. | Local · stdio |
| Semblecodesearchgate MCPPaid remote MCP for agent code search routing MCP, structured receipts, audit logs, and reviewer-rea. | Remote · HTTPLive check: ✗ no handshake |
| semhoodAST-based semantic code search; results ship with their call graph (calls + callers). | Local · stdio |
| Semver ChecksDetect breaking changes in your TypeScript library's public API and recommend the SemVer bump. | Local · stdio |
| Send16 MCPEmail for AI agents: send mail, manage contacts, automations & webhooks. Zero-DNS first send. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| SendGrid SecureSecurity-first SendGrid MCP server: dry-run default, recipient allowlists, rate caps, audit log. | Local · stdio |
| Sensations MergulhoMCP server for 0001SENSATIONS: 107-level textual descent, append-only trace logging. | Remote · HTTPLive check: ✗ no handshake |