What do you want to do?

PostgreSQL SELECT over financial / market / alt-data tables — returns structured rows. Hard rules (query fails otherwise): - SELECT only, no CTE (`WITH ... AS`) — use subqueries. - Period columns are TEXT, not dates — `period_end` is 'YYYY-MM'. Compare as strings (`period_end >= '2024-01'`); a `::date` cast on it fails. - Filter structured tables by ticker (`WHERE ticker IN ('AAPL','MSFT')`; screening: add `ticker NOT LIKE '%-%'` to drop preferred stock). Tables by domain (get_table_schema gives columns + coverage note): - Market: price_volume_history (OHLCV history; MUST filter ticker + time_frame), index_price, equity_extended_rt (pre/after/overnight quotes) - Fundamentals: financial_statements (GAAP income/balance/cashflow), company_snapshot (ratios, per-share, growth) - Earnings: earning_call_summary, earning_call_calendar - Analyst: analyst_ratings, analyst_ratings_consensus - Ownership: insider_and_institution_activities - 8-K events: executive_change, company_deal_events, debt_issuance, securities_offering - Executives: executive_profile, executive_compensation - Alt-data: macro / industry / trade / AI-supply-chain — call list_tables(categories=[...])

Search the catalog of 3500+ MCP servers at thedailyworkflow.com. Args: query: Free-text search (matches name, description, keywords). Example: "notion", "postgres database". category: Filter by category. Common values: databases, web, filesystem, cloud, productivity, communication, dev, ai, search, monitoring. client: Filter by supported MCP client. Values: claude-desktop, cursor, cline, windsurf, continue, goose. language: Filter by implementation language. Values: typescript, python, go, rust, java. limit: Max results to return (1-25, default 10). Returns: Dict with `count` and `results` (list of MCP server summaries). Each result has: slug, name, description, categories, language, transport, supported_clients, stars, repo_url, page_url (link to full info). Use this when the user asks for an MCP server matching some need ("find me an MCP for X", "what MCP servers work with Cursor", "Slack MCP servers"). After choosing a candidate, call get_mcp_install_config to get ready-to-paste setup.

Run one SQL statement against an app's PostgreSQL addon (owner/admin only). Read-only by default: the statement runs in a READ ONLY transaction that is rolled back. With allow_write=true it CAN WRITE: INSERT/UPDATE/DELETE and DDL (DROP, ALTER, TRUNCATE) are committed immediately and cannot be undone. Before setting allow_write, show the user the exact SQL and get their explicit confirmation. Results are capped at 1000 rows; statements time out after 15s.

SQL from a question and a schema (CREATE TABLE statements or a JSON description of tables and columns), for postgres (default), mysql, sqlite or bigquery. The tables and columns used are checked against the schema; a query that does not match it is retried once, then refused. Writes (INSERT, UPDATE, DELETE, DDL) are refused unless allowWrite is true. The query is not run. Price: $0.003 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

Find or search for an MCP server, connector, integration, agent or skill for a task (e.g. query Postgres, automate a browser, take payments, send email). Returns the top 3 verified working options with a one-line install, in about 3 KB. Example: {"task":"query a Postgres database"}

Convert a SQL statement from one dialect to another — mysql, postgres, sqlite, tsql, oracle, snowflake, bigquery, redshift, spark, hive, presto, trino, duckdb, clickhouse, databricks, doris, starrocks and more. Deterministic parser (sqlglot), not an LLM: the same input always produces the same output, and syntax errors come back with the exact line and column. Use it when migrating queries between databases or debugging dialect-specific syntax.

Analyze Postgres SQL/migrations for destructive operations, locking risk, correctness traps (NULL handling that silently returns wrong results), anti-patterns, and query cost. Returns a deterministic verdict (ok/warn/block) with findings. Pass the optional `schema` argument (your CREATE TABLE/INDEX DDL) to also get EXPLAIN-based cost analysis run on a throwaway scratch Postgres — no separate tool or DB connection needed.

Find MCP servers, agent skills (SKILL.md) and coding-agent plugins for a task. Pass a plain-language task (e.g. 'query my Postgres from Cursor', 'post to Slack from Claude Code') or keywords. The task is parsed for kind (MCP/skill/plugin), client (Cursor, Claude Code, Codex, VS Code), remote vs local and language; results are ranked by relevance (full-text + semantic match), with stars, recent commits, a valid one-click config and a license only as tie-breakers. Every result explains why it matches. type, client and remote are strict filters (client grok-bot = MCP servers with a public HTTPS endpoint).

Run a read-only SQL query against an app's Postgres database and return up to 200 result rows. SELECT only — writes and DDL (INSERT/UPDATE/DELETE/ALTER/DROP/…) are rejected server-side; use vibekit_chat or vibekit_submit_task to have the agent make data or schema changes. Call vibekit_db_schema first to learn the tables. SQL string, max 5000 chars.

Full-text search messages in a specific group. Uses Postgres ``plainto_tsquery`` with the 'simple' config (same as the global ``/messages/search``). Scoped to non-soft-deleted rows. Caller must be a member. Hits are in ``items``; ``results`` is a DEPRECATED duplicate of the same list. ``count`` is how many hits this response holds; ``has_more`` is true when more match than ``limit`` allowed.

Use when you have a product's name, domain or kind in mind: send a short query ('stripe.com', 'postgres', 'invoicing') with filters for category, agent level, access or payment. Returns the products we drove, sorted by agent level (0-5), each with where our agent stopped; a task in plain words: choose_provider_for_task, one product in full: get_provider. Read-only, no key needed; up to 100 a page.

Search every server in the official MCP Registry (about 57,000, refreshed daily) by what you need, e.g. 'query a Postgres database', 'send email', 'Figma designs': GitHub stars, whether the name is a verified domain, version, install or connect command and a card. One result per repository. Read a server's README and tools before connecting it.

Run a read-only SQL query on the core Postgres replica. Tables: users, customers, shipments, api_keys, incident_log.

Find PostgreSQL Discord discussions semantically related to a query. Returns only the channel, approximate date range, and participants of relevant conversations — never message content or links (per the Discord community agreement).

Search FULL BILL TEXT -- not just known-bill-number lookup. `q` is matched against titles, descriptions, AND ingested document text via Postgres websearch_to_tsquery (supports "quoted phrases", OR, and -exclusion, same syntax as a search engine), with a fuzzy pg_trgm title-similarity fallback when the exact query has no hits. `q` can ALSO be a bill number ("HB 123", "H.B. 123", "hb123" all match) and that fast path is tried first. Optionally filter by jurisdiction (two-letter state code or name), chamber, and status. For a curated cross-state slice of a subject (e.g. "every AI bill in the country") rather than an ad-hoc keyword search, call list_topics first -- its membership rules also match on structured subject tags this full-text search does not see.

Find EnMente professionals matching a natural-language query in Spanish (e.g. "psiquiatra TDAH adultos", "psicóloga pareja online", "duelo adulto mayor"). Uses Postgres FTS over name, role, specialties, tagline, category, and bio. Returns ranked matches with relevance score. Each match includes a `pricing` object (currency CLP, services with price and duration) when fresh pricing data exists — `pricing.available` is false with no invented price otherwise.

Find MCP servers and Agent Skills for a dev task. Free-text query (every term must match name, vendor, verdict, install or category; common words like postgres, e2e, scraping are expanded) and optional category slug from list_categories (a dev task such as 'database' or a type such as 'agent-skill'). Empty query lists the category.

Search MCP servers by keyword or partial name (e.g. 'github', 'postgres'). Returns ranked matches with health/trust. Also returns: resolved_query (auto typo fix), disambiguate (when unsure), known_brand (we recognize a strong product but it has no official MCP — e.g. CodeRabbit), research (watchlist/confirmed_absent), query_intent (brand_lookup|category|package|install_gate|junk — does not change ranking), intent_cta (preflight when they asked an install-gate question). Prefer official_match=true rows. Never invent servers.

Recommends open-source projects for a need (e.g. 'MCP server to query Postgres', 'self-hosted Google Photos replacement', 'terminal coding agent'), from Repolode's comparisons of similar projects: the default pick, strong alternatives and specialists, when to choose and avoid each, plus a scenario guide. Projects are judged on code substance, engineering, real usage (downloads) and maintenance, not stars alone. Falls back to keyword search when no comparison covers the need.

Estimate PostgreSQL sequential-scan and index-scan cost from table rows, table pages, selectivity, and storage type. Uses the same four-input model as the browser calculator.

Find prediction markets by free-text query; returns slugs for other endpoints. Full-text search over the canonical market catalog (Postgres FTS + trigram in live mode). Returns slugs, blended probabilities, and match confidence. Empty result sets return 200 with a suggestion listing valid categories. [HTTP: GET /v1/probability/search · price $0.02 via x402 · docs https://x402-factory.com/docs/probability.search]

List the SQL databases (D1 or Neon Postgres) on my account, including which owned site (if any) each is attached to. Call this BEFORE db_query/db_schema-style work to discover a databaseId — those live on a per-database MCP server reached via GET /api/v1/databases/{id} (see llms.txt), which this id feeds.

Reads the data INSIDE a managed Postgres database, as the console's data view does: tables, rows (sorted, found), a table's info, one cell, a related row, one read-only SQL query, CSV export, saved queries. Changes nothing. Action help lists every action's arguments and the rules, for this tool and postgres_data_change.

Execute any valid SQL statement, including data definition language (DDL), data control language (DCL), data query language (DQL), or data manipulation language (DML) statements, on a Cloud SQL for MySQL, Cloud SQL for PostgreSQL, or Cloud SQL for SQL Server instance. To support the `execute_sql` tool, a Cloud SQL instance and request must meet the following requirements: * The value of `data_api_access` must be set to `ALLOW_DATA_API`. * For PostgreSQL and SQL Server instances, the `database` field is required. For MySQL instances, the `database` field is optional. * For built-in database users (supported for MySQL, PostgreSQL, and SQL Server, and required for SQL Server because Cloud SQL for SQL Server doesn't support IAM database authentication): * Specify the `user` field and the `password_secret_version` field. * The value of `password_secret_version` must be the resource name of a regional secret version in Secret Manager stored in the same region as the Cloud SQL instance, such as `projects/12345/locations/us-central1/secrets/my-password-secret/versions/1` or `projects/12345/locations/us-central1/secrets/my-password-secret/versions/latest`. * The caller must have the `secretmanager.secretVersions.access` permission on the secret version. * For IAM database authentication (supported for MySQL and PostgreSQL only; not supported for SQL Server): * For a MySQL instance, the database flag `cloudsql_iam_authentication` must be set to `on`. * For a PostgreSQL instance, the database flag `cloudsql.iam_authentication` must be set to `on`. * An IAM user account or IAM service account (`CLOUD_IAM_USER` or `CLOUD_IAM_SERVICE_ACCOUNT`) must exist on the instance. After you use the `create_instance` tool to create a MySQL or PostgreSQL instance, you can use the `create_user` tool to create an IAM user account for the user currently logged in to the project. The `execute_sql` tool has the following limitations: * If a SQL statement returns a response larger than 10 MB, then the response will be truncated. * The `execute_sql` tool has a default timeout of 30 seconds. If a query runs longer than 30 seconds, then the tool returns a `DEADLINE_EXCEEDED` error. If you receive errors similar to "IAM authentication is not enabled for the instance" on a MySQL or PostgreSQL instance, then you can use the `get_instance` tool to check the value of the IAM database authentication flag for the instance. If you receive errors like "The instance doesn't allow using executeSql to access this instance", then you can use the `get_instance` tool to check the `data_api_access` setting. When you receive authentication errors for a built-in database user (including all SQL Server requests): 1. Check if the specified database user exists on the instance using the `list_users` tool. 2. Verify that `password_secret_version` references a valid regional Secret Manager secret version in the same region as the Cloud SQL instance and that the caller has the `secretmanager.secretVersions.access` permission on the secret version. 3. Check if the caller has the `cloudsql.instances.executeSql` IAM permission on the project (included in roles such as Cloud SQL Instance User (`roles/cloudsql.instanceUser`) or Cloud SQL Admin (`roles/cloudsql.admin`)). When you receive authentication errors for IAM database authentication (MySQL and PostgreSQL only): 1. Check if the currently logged-in user account exists as an IAM user on the instance using the `list_users` tool. 2. If the IAM user account doesn't exist, then use the `create_user` tool to create the IAM user account for the logged-in user. 3. If the currently logged-in user doesn't have the proper database user roles, then you can use the `update_user` tool to grant database roles to the user. For example, the `cloudsqlsuperuser` role can provide an IAM user with many required permissions. 4. Check if the currently logged-in user has the correct IAM permissions assigned for the project. You can use the `gcloud projects get-iam-policy [PROJECT_ID]` command to check if the user has the proper IAM roles or permissions assigned for the project. * The user must have `cloudsql.instances.login` permission to do automatic IAM database authentication. * The user must have `cloudsql.instances.executeSql` permission to execute SQL statements using the `execute_sql` tool or `executeSql` API. * Common IAM roles that contain the required permissions: Cloud SQL Instance User (`roles/cloudsql.instanceUser`) or Cloud SQL Admin (`roles/cloudsql.admin`). When receiving an `ExecuteSqlResponse`, always check the `message` and `status` fields within the response body. A successful HTTP status code doesn't guarantee full success of all SQL statements. The `message` and `status` fields will indicate if there were any partial errors or warnings during SQL statement execution.

Search the iHerb product database using a natural-language query, benefit keyword, ingredient name, or brand name. Uses the PostgreSQL GIN full-text search index first (fast, relevance-ranked), then falls back to a broader ILIKE scan if FTS yields no results.