SeedBase Test Data
REMOTE · SEEDBA.SE · 2 COMPONENTS
Generate realistic, FK-consistent synthetic test data for your databases from your AI assistant.
Available components
Last scanned (3 hours ago)
Scores higher than 99% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Testing and QA
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability84
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 564 tokens (~94/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://seedba.se/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=seedba.se | CN=YE2,O=Let's Encrypt,C=US | 5 Oct 2026 | 3 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 60e8168d2d8ef28e8050f0b906b1b62da17 |
| SANs: seedba.se | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of seedba.se. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| se. | present | 59407 | 8 | Verified |
| seedba.se. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="seedbase-mcp"
Bearer realm="seedbase-mcp"| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | same-origin |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://seedba.se/mcp | Verified | 200 | |
| http (plaintext) | http://seedba.se/mcp | HTTPS enforced | 308 | https://seedba.se/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
create_project Create project ~51
Create a new, empty SeedBase project. Use import_schema afterwards to add the schema.
| Name | Type | Req | Description |
|---|---|---|---|
| db_type | string | – | Target database type (default: postgresql) |
| name | string | yes | Project name |
| Name | Type | Req | Description |
|---|---|---|---|
| db_type | string | yes | – |
| id | string | yes | – |
| name | string | yes | – |
No examples provided.
fetch_generation Fetch generation result ~60
Fetch a previously started generation by id: returns its status, and the SQL INSERT statements once completed. Use this when generate_test_data reported the generation as still running.
| Name | Type | Req | Description |
|---|---|---|---|
| generation_id | string | yes | The generation id (UUID) reported by generate_test_data |
| Name | Type | Req | Description |
|---|---|---|---|
| download_url | string | – | Authenticated download endpoint for the complete SQL (send your API key as 'Authorization: Bearer …'). |
| generation_id | string | yes | – |
| sql | string | – | Complete SQL INSERTs. Absent when the result is too large — download it from download_url instead; no partial SQL is ever returned. |
| sql_chars | integer | – | – |
| status | string | yes | – |
| truncated | boolean | – | True when the SQL was too large to inline. The response then contains NO sql; fetch the complete file from download_url. |
No examples provided.
generate_test_data Generate test data ~83
Generate a fresh synthetic dataset for a project and return it as SQL INSERT statements. Optionally set rows per table. The data is foreign-key consistent.
| Name | Type | Req | Description |
|---|---|---|---|
| project | string | yes | Project id (UUID) or project name |
| rows | integer | – | Rows per table (optional; plan limits apply) |
| seed | integer | – | Seed for deterministic output (optional) |
| Name | Type | Req | Description |
|---|---|---|---|
| download_url | string | – | Authenticated download endpoint for the complete SQL (send your API key as 'Authorization: Bearer …'). |
| generation_id | string | yes | – |
| sql | string | – | Complete SQL INSERTs. Absent when the result is too large — download it from download_url instead; no partial SQL is ever returned. |
| sql_chars | integer | – | – |
| status | string | yes | – |
| truncated | boolean | – | True when the SQL was too large to inline. The response then contains NO sql; fetch the complete file from download_url. |
No examples provided.
get_ddl Get schema DDL ~76
Get a project's schema as CREATE TABLE statements. Accepts a project id or name and an optional SQL dialect (postgresql, mysql, sqlite, mssql).
| Name | Type | Req | Description |
|---|---|---|---|
| dialect | string | – | SQL dialect for the DDL (default: the project's database type) |
| project | string | yes | Project id (UUID) or project name |
| Name | Type | Req | Description |
|---|---|---|---|
| ddl | string | yes | – |
| dialect | string | yes | – |
No examples provided.
import_schema Import schema ~142
Import a database schema into a project from pasted content: SQL DDL (CREATE TABLE …, raw pg_dump/mysqldump schema output works), SQL INSERT dumps, CSV/TSV, JSON, or ORM model code (Django, Prisma, SQLAlchemy, …). Replaces the project's current schema.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | The schema source text (e.g. the DDL) |
| format | string | – | Optional hint: sql, csv, tsv, json, or an ORM name (django, prisma, sqlalchemy, …). Auto-detected when omitted. |
| project | string | yes | Project id (UUID) or project name |
| Name | Type | Req | Description |
|---|---|---|---|
| fk_count | integer | yes | – |
| table_count | integer | yes | – |
| tables | array | – | – |
| warnings | array | – | – |
No examples provided.
list_projects List projects ~32
List your SeedBase projects (id, name, database type). Use this first to find the project to work with.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| projects | array | yes | – |
No examples provided.
How do I install the SeedBase Test Data MCP server?
SeedBase Test Data is a hosted endpoint at https://seedba.se/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · seedba.se
claude mcp add --transport http marcelglaeser-seedbase 'https://seedba.se/mcp'
What is the SeedBase Test Data MCP server?
SeedBase Test Data is an MCP server listed in the public MCP registry as io.github.marcelglaeser/seedbase. Generate realistic, FK-consistent synthetic test data for your databases from your AI assistant. This page covers its hosted endpoint (https://seedba.se/mcp).
Is the SeedBase Test Data MCP server safe to use?
SeedBase Test Data scores 93 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the SeedBase Test Data MCP server expose?
SeedBase Test Data exposes 6 tools: list_projects, get_ddl, generate_test_data, fetch_generation, create_project, import_schema. Their descriptions and schemas cost roughly 444 tokens of context every time the server is loaded.
Does the SeedBase Test Data MCP server require authentication?
Yes. SeedBase Test Data asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the SeedBase Test Data MCP server still maintained?
SeedBase Test Data is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.