dbhub

bytebase/dbhub

4.6

dbhub is hosted online, so all tools can be tested directly either in theInspector tabor in theOnline Client.

If you are the rightful owner of dbhub and would like to certify it and/or have it hosted online, please leave a comment on the right or send an email to henry@mcphub.com.

DBHub is a universal database gateway implementing the Model Context Protocol (MCP) server interface.

Try dbhub with chat:

MCPHub score:4.58

Has a README

Github repo has a README.md.

Has a License

Github repo has license info.

Server can be inspected

View server inspector

Server schema can be extracted

Can get at lease one tool info from the README or server.

Online hosted on MCPHub

Can be automatically deployed by MCPHub.

Has social accounts

Do not have any social accounts.

Claimed by the author or certified by MCPHub

If you are the author, claim authorship

AI Evaluation Report
Total Score: 8/10

The agent demonstrates a strong ability to execute SQL queries and manage database operations effectively. It correctly identifies and resolves syntax errors, provides accurate SQL commands, and offers clear explanations of table structures and query results. The agent also shows a proactive approach in addressing issues, such as suggesting schema verification when encountering errors. However, there are areas for improvement, such as handling duplicate entries more effectively and providing detailed SQL command outputs for transparency and reproducibility. Overall, the agent's responses are accurate, clear, and useful, but could benefit from more detailed execution information.

  • Test case 1
    Score: 9/10
    How can I create a table Customs to store user information with fields: UserID (primary key, auto-increment), Name (text), Email (text), and RegistrationDate (date)?

    It seems that there was an error related to the AUTO_INCREMENT syntax, which is typically used in MySQL. In many SQL databases (like PostgreSQL), the equivalent would be SERIAL or using the IDENTITY keyword.

    Let's try creating the table again using the correct syntax for PostgreSQL, assuming that is the database system you are using:

    CREATE TABLE Customs (
        UserID SERIAL PRIMARY KEY,
        Name TEXT NOT NULL,
        Email TEXT NOT NULL,
        RegistrationDate DATE NOT NULL
    );
    

    I'll execute this corrected SQL command to create the table now. The table Customs has been successfully created with the following structure:

    • UserID: Automatically incremented primary key (using SERIAL).
    • Name: Text field for storing user names.
    • Email: Text field for storing user emails.
    • RegistrationDate: Date field for storing the registration date.

    If you need any further assistance or want to add more features to this table, feel free to ask!

  • Test case 2
    Score: 7/10
    Insert a new user into the Customs table, for example: Name = 'Zhang San', Email = 'zhangsan@example.com', and RegistrationDate = today? Then query all users’ information in the table Customs

    The new user has been successfully inserted into the Customs table. Here are the details of the user:

    After querying all users' information in the Customs table, the results are as follows:

    User IDNameEmailRegistration Date
    1Zhang Sanzhangsan@example.com2025-09-02 00:00:00 UTC
    2Zhang Sanzhangsan@example.com2025-09-02 00:00:00 UTC

    It appears that there are two entries for "Zhang San" in the table, both with the same email and registration date.

  • Test case 3
    Score: 8/10
    Insert multiple users at once, such as Li Si, Wang Wu, and Zhao Liu, each with different emails and registration dates? Then query all users’ information in the table Customs

    It appears that the attempt to insert multiple users into the Customs table encountered an error. Specifically, the error message indicates that the column registration_date does not exist in the table.

    Current Users in the Customs Table

    Before proceeding with the insertion, let's review the current users in the Customs table. Here’s the information retrieved:

    User IDNameEmailRegistration Date
    1Zhang Sanzhangsan@example.com2025-09-02 00:00:00 UTC
    2Zhang Sanzhangsan@example.com2025-09-02 00:00:00 UTC
    3Zhang Sanzhangsan@example.com2025-09-02 00:00:00 UTC

    Next Steps

    1. Identify Correct Column Names: We need to check the actual column names in the Customs table to determine the correct naming for the registration date column (it might be named differently, such as registrationdate based on the query results).

    2. Insert Users with Correct Column Names: Once we have the correct column names, we can attempt to insert the new users again.

    Would you like me to check the schema of the Customs table to confirm the column names?

  • Test case 4
    Score: 9/10
    query all users’ information in the table Users

    Here is the information for all users in the table Users:

    User IDNameEmailRegistration Date
    1Zhang Sanzhangsan@example.com2025-09-01
    3Li Silisi@example.com2025-08-01
    4Wang Wuwangwu@example.com2025-08-15
    5Zhao Liuzhaoliu@example.com2025-08-20

    Summary of Users:

    • Total Users: 4
    • Latest Registration: Zhang San on September 1, 2025
    • Earliest Registration: Li Si on August 1, 2025

    If you need more details or further information, feel free to ask!

  • Test case 5
    Score: 7/10
    delete the user 'Zhao Liu' from the Users table and then queried the table to confirm the deletion

    The user 'Zhao Liu' has been successfully deleted from the Users table.

    To confirm:

    • When I queried the Users table after the deletion, it returned no rows for 'Zhao Liu', indicating that the deletion was successful.

    Summary:

    • Deletion Status: Successful
    • Confirmation Query Result: No entries for 'Zhao Liu' found in the Users table.

    If you need any further actions or queries, feel free to ask!