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

querymind-connect

https://querymind.co.kr

Registry code: 26eb369914191472

api record

QueryMind provides read-only business data answers. Prefer an approved q_* tool when its definition matches the question. For uncovered questions use ask; follow clarifications with clarify, pending jobs with result and evidence with explain. Respond in the user's language, preserving numbers, units, filters and uncertainty. no_rows or outside_data_range is not zero: explain why the question cannot be answered. Never invent missing data, bypass access rules or write to the business database.

endpoint
https://querymind.co.kr/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 querymind-connect live?
Yes — it answered the hub's last check (checked 8h ago). It answered 100% of checks over the last 30 days.
Is querymind-connect free to use?
Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
What tools does querymind-connect have?
13 tools: onboard, ask, connect_database, define, review, set_access_rule, invite, capabilities, ….
Is querymind-connect 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
100%

90 days 100%· all time 100%

latency
9,099ms

last good check

priced tools
0

of 13 tools

_ answered our checks, 90 days 3 checks · signed record
  • unknown → live
_ 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 13 tools
13 auth-required 13 of 13 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.

  • onboard auth-required never probed

    Start a durable job to learn the connected database structure. Reuses a running job for the same database. Check onboarding_status; candidates requiring approval are handled with review.

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {},
      "additionalProperties": false
    }
    arguments 6 lines
  • ask auth-required never probed

    Send a natural-language question to the analysis engine. Reads business data without modifying it, but creates QueryMind query jobs, audit records, conversation context and usage records. Returns an answer, state, limited result rows and evidence. If state=clarifying_question, ask the user the returned question before calling clarify.

    mcp-tool

    {
      "type": "object",
      "required": [
        "question"
      ],
      "properties": {
        "question": {
          "type": "string",
          "description": "The user's natural-language data question; preserve their business meaning."
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • connect_database auth-required never probed

    Create a secure setup link for the user's business database. Show the link to the user. Credentials must be entered there, never in chat. The link expires in 10 minutes and is single-use. Use a read-only database account.

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {
        "kind": {
          "type": "string",
          "description": "postgres, mysql, mssql or oracle; omit if unknown."
        },
        "name": {
          "type": "string",
          "description": "Optional display name for this database."
        }
      },
      "additionalProperties": false
    }
    arguments 15 lines
  • define auth-required never probed

    Propose a business definition for this user's questions only. First send term and definition, then show the preview to the user. Send confirm_token only after their explicit confirmation. Use undo_def_id to undo or list=true to list definitions.

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {
        "list": {
          "type": "boolean",
          "description": "Set true to list personal definitions."
        },
        "term": {
          "type": "string",
          "description": "Business term to define."
        },
        "preview": {
          "type": "boolean",
          "description": "Defaults to true."
        },
        "definition": {
          "type": "string",
          "description": "The user's intended business definition."
        },
        "undo_def_id": {
          "type": "string",
          "description": "ID of a personal definition to undo."
        },
        "confirm_token": {
          "type": "string",
          "description": "Token from a preview explicitly approved by the user."
        }
      },
      "additionalProperties": false
    }
    arguments 31 lines
  • review auth-required never probed

    List or propose approval/rejection of onboarding candidates (table labels, joins, code dictionaries). An administrator must confirm changes through a secure reauthentication link.

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {
        "action": {
          "enum": [
            "list",
            "approve",
            "dismiss"
          ],
          "type": "string",
          "description": "list, approve or dismiss."
        },
        "candidate_ids": {
          "type": "array",
          "items": {
            "type": "integer"
          },
          "description": "Candidate IDs returned by list."
        }
      },
      "additionalProperties": false
    }
    arguments 23 lines
  • set_access_rule auth-required never probed

    Propose which rows a role can access. Changes take effect only after an administrator reauthenticates and confirms through a secure link, never through chat alone.

    mcp-tool

    {
      "type": "object",
      "required": [
        "role",
        "table",
        "predicate"
      ],
      "properties": {
        "role": {
          "enum": [
            "viewer",
            "analyst",
            "admin"
          ],
          "type": "string",
          "description": "Role affected by the rule."
        },
        "table": {
          "type": "string",
          "description": "Table to which the rule applies."
        },
        "predicate": {
          "type": "string",
          "description": "SQL WHERE condition, for example dept_id = 101."
        },
        "description": {
          "type": "string",
          "description": "Business explanation of the proposed rule."
        }
      },
      "additionalProperties": false
    }
    arguments 32 lines
  • invite auth-required never probed

    Administrators can create a single-use invitation link valid for 24 hours. Share the link yourself; this tool does not send email. The recipient signs in or signs up through the link and uses the same connector address.

    mcp-tool

    {
      "type": "object",
      "required": [
        "email"
      ],
      "properties": {
        "role": {
          "enum": [
            "admin",
            "analyst",
            "viewer"
          ],
          "type": "string",
          "description": "Role in the organization; defaults to analyst."
        },
        "email": {
          "type": "string",
          "description": "Recipient email, which becomes their login ID."
        }
      },
      "additionalProperties": false
    }
    arguments 22 lines
  • capabilities auth-required never probed

    Describe the connected data source, access limits and setup status. Before sign-in, returns public connection guidance only.

    mcp-tool

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

    Retrieve the answer, state, limited result rows and evidence for the job_id returned by ask or clarify with state=pending. Completing retrieval can record QueryMind usage; business data remains read-only.

    mcp-tool

    {
      "type": "object",
      "required": [
        "job_id"
      ],
      "properties": {
        "job_id": {
          "type": "integer",
          "description": "The job_id returned by ask or clarify."
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • usage auth-required 8h ago

    Return this month's question usage, account limits and connected database count.

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {},
      "additionalProperties": false
    }
    arguments 6 lines
  • clarify auth-required never probed

    Continue the previous ask after the engine requests clarification. May create a QueryMind query job and update audit records, conversation context and usage records; business data remains read-only. Send the user's choice or additional explanation; do not invent their choice.

    mcp-tool

    {
      "type": "object",
      "required": [
        "choice"
      ],
      "properties": {
        "choice": {
          "type": "string",
          "description": "The user's choice or additional explanation."
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • explain auth-required 8h ago

    Show the data source, query conditions (SQL), time basis and access restrictions for a recent answer accessible to this connection.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "audit_id": {
          "type": "integer",
          "description": "Omit to explain the most recent ask answer."
        }
      },
      "additionalProperties": false
    }
    arguments 10 lines
  • onboarding_status auth-required 8h ago

    Return onboarding stage, status and next steps, with question examples when available.

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {
        "job_id": {
          "type": "string",
          "description": "Omit for the most recent onboarding job for the current database."
        }
      },
      "additionalProperties": false
    }
    arguments 11 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 26eb369914191472.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/26eb369914191472/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/26eb369914191472/badge.svg)](https://brick.blue/agent/26eb369914191472?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.