_ registry / mcp streamable-http · checked 2h ago

seedbase

https://seedba.se

Registry code: 776c5393064ed70d

api record

SeedBase generates realistic, foreign-key-consistent synthetic test data. Free tier, no credit card. Typical flow: call list_projects to find the project (or create_project + import_schema for a new one), optionally get_ddl to inspect or create the schema in a local database, then generate_test_data to produce SQL INSERTs. Authentication: create a free account at https://seedbase.dev/register, then a SeedBase API key (dr_sk_...) under Settings -> API keys, and send it as 'Authorization: Bearer <key>' or 'apiKey' header.

endpoint
https://seedba.se/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is seedbase live?
Yes — it answered the hub's last check (checked 2h ago). It answered 99% of checks over the last 30 days.
Is seedbase free to use?
No — it asks for a key or a login before it will serve.
What tools does seedbase have?
6 tools: list_projects, import_schema, generate_test_data, fetch_generation, get_ddl, create_project.
Is seedbase safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.4%

90 days 99.4%· all time 99.4%

latency
129ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 174 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • unknown → live
_ what it is for
used for
  • generate synthetic sql test data
  • import a database schema
  • get schema as create table ddl
takes → gives
code, text → code
tools
3 reads3 changes data
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 6 tools
6 auth-required 6 of 6 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • list_projects reads auth-required 15h ago

    List your SeedBase projects (id, name, database type). Use this first to find the project to work with.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • import_schema changes data auth-required never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "project",
        "content"
      ],
      "properties": {
        "format": {
          "type": "string",
          "description": "Optional hint: sql, csv, tsv, json, or an ORM name (django, prisma, sqlalchemy, …). Auto-detected when omitted."
        },
        "content": {
          "type": "string",
          "description": "The schema source text (e.g. the DDL)"
        },
        "project": {
          "type": "string",
          "description": "Project id (UUID) or project name"
        }
      },
      "additionalProperties": false
    }
    arguments 22 lines
  • generate_test_data changes data auth-required never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "project"
      ],
      "properties": {
        "rows": {
          "type": "integer",
          "minimum": 1,
          "description": "Rows per table (optional; plan limits apply)"
        },
        "seed": {
          "type": "integer",
          "description": "Seed for deterministic output (optional)"
        },
        "project": {
          "type": "string",
          "description": "Project id (UUID) or project name"
        }
      },
      "additionalProperties": false
    }
    arguments 22 lines
  • fetch_generation reads auth-required 12h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "generation_id"
      ],
      "properties": {
        "generation_id": {
          "type": "string",
          "description": "The generation id (UUID) reported by generate_test_data"
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • get_ddl reads auth-required 12h ago

    Get a project's schema as CREATE TABLE statements. Accepts a project id or name and an optional SQL dialect (postgresql, mysql, sqlite, mssql).

    mcp-tool

    {
      "type": "object",
      "required": [
        "project"
      ],
      "properties": {
        "dialect": {
          "enum": [
            "postgresql",
            "mysql",
            "sqlite",
            "mssql"
          ],
          "type": "string",
          "description": "SQL dialect for the DDL (default: the project's database type)"
        },
        "project": {
          "type": "string",
          "description": "Project id (UUID) or project name"
        }
      },
      "additionalProperties": false
    }
    arguments 23 lines
  • create_project changes data auth-required never probed

    Create a new, empty SeedBase project. Use import_schema afterwards to add the schema.

    mcp-tool

    {
      "type": "object",
      "required": [
        "name"
      ],
      "properties": {
        "name": {
          "type": "string",
          "description": "Project name"
        },
        "db_type": {
          "enum": [
            "postgresql",
            "mysql",
            "sqlite",
            "mssql"
          ],
          "type": "string",
          "description": "Target database type (default: postgresql)"
        }
      },
      "additionalProperties": false
    }
    arguments 23 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 776c5393064ed70d.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/776c5393064ed70d/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/776c5393064ed70d/badge.svg)](https://brick.blue/agent/776c5393064ed70d?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.