Data · Remote MCP server
SuprSend
Hosted SuprSend MCP server: users, lists, workflows, templates, and notification data.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
com.suprsend/mcp- Version
- 0.2.0
- Status
- Active
- Category
- data
- Transport
- Streamable HTTP
- Published
- 2026-10-03
- Updated
- 2026-10-03
- Publisher
- com.suprsend
- Namespace
- Namespace verified by the MCP Registry via the domain suprsend.com · how
- Website
- www.suprsend.com
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.suprsend.com/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 SuprSend
SuprSend is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.suprsend.com/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, www.suprsend.com, 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 data servers
| Server | Runs |
|---|---|
| SuperlocalmemoryLocal-first AI memory with knowledge graphs and hybrid search. 17+ AI tools via MCP. Free. | Local · stdio |
| SuperpracticeMarketing and practice analytics for law firms: leads, meetings, attribution, ads, SEO, pipeline. | Remote · HTTPLive check: sign-in required |
| Supost MCPSearch listings, message posters, and create drafts on SUpost, the marketplace for Stanford. | Remote · HTTPLive check: ✓ handshake |
| SupplyGraph.AI DataOfficial SupplyGraph.AI data MCP: POIs, parks, regions, industry chains, and companies. | Remote · HTTPLive check: ✓ handshake |
| SupstackEvidence-based supplement research, dosing, safety, and interactions as agent-callable tools. | Local · stdio |
| Surety BondsSurety Bond Encyclopedia: search 6,900+ U.S. surety bond requirements, all 50 states. | Remote · HTTPLive check: ✓ handshake |
| Surf HutSigned proof-of-time, 30-day stash, live NOAA surf data. No auth. The hut keeps honest clocks. | Remote · HTTPLive check: ✓ handshake |
| Survey MCP ServerMCP server for conducting dynamic, conversational surveys with structured data collection. | Local · stdio, HTTP |