Developer · Remote MCP server
Tenantsdb
Multi-tenant database orchestration: isolated Postgres, MySQL, MongoDB, Redis tenants on demand.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
com.tenantsdb/tenantsdb- Version
- 1.0.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-07-30
- Updated
- 2026-07-30
- Publisher
- com.tenantsdb
- Namespace
- Namespace verified by the MCP Registry via the domain tenantsdb.com · how
- Listed under
- PostgreSQL MCP servers, MySQL MCP servers, MongoDB MCP servers, Redis MCP servers
- Website
- tenantsdb.com
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://api.tenantsdb.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 Tenantsdb
Tenantsdb is a remote MCP server: there is nothing to install. Its endpoint is https://api.tenantsdb.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, tenantsdb.com, was checked for the files that tell AI systems about a site.
| File | Result |
|---|---|
/llms.txt | No real file found |
/.well-known/mcp.json | No real file found |
/.well-known/ai-plugin.json | No real file found |
/agents.json | No real file found |
More developer servers
| Server | Runs |
|---|---|
| TemperaPersistent episodic memory for AI coding: capture, retrieve, brief, dream cycle, cross-project. | Local · stdio |
| TempoGraphCode graph context engine with 24 MCP tools. 170+ languages via tree-sitter. | Local · stdio |
| temporal-mcpWall-clock awareness for LLM agents. Two tools: elapsed-time-between-turns + day rollover detection. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| Tempreon - Personal AI MemoryPerson-owned AI memory that learns, not just stores - portable context for any MCP client. | Remote · HTTPLive check: sign-in required |
| Tenki Sandbox MCPDisposable microVM sandboxes for AI agents: run code, read/write files, git, preview URLs. | Local · stdio |
| TensorcadDesign transformer LLM architectures and report their parameters, FLOPs, memory and cost. | Local · stdio |
| Tentra - Memory for AI Coding AgentsMemory for AI coding agents. Call graphs + refactor safety + persistent code context. 35 MCP tools. | Remote & Local · SSE, stdioLive check: sign-in required |
| TeramindMCP server for Teramind's insider-threat/employee-monitoring API (read-only, metadata-only surface). | Local · stdio |