# RationalBloks (remote · mcp.rationalbloks.com) Deploy production REST and Neo4j Graph APIs from JSON schemas in seconds. 49 tools. - Trust score: 64/100 (medium) - Registry status: active - Liveness: live - Owner verified: no - Last scored: 2026-09-20 ## Components - remote · `mcp.rationalbloks.com`: 64/100 (this document), [markdown](https://verifymcp.io/servers/com-rationalbloks-mcp/mcp.md), [page](https://verifymcp.io/servers/com-rationalbloks-mcp/mcp) - pypi · `rationalbloks-mcp`: 16/100, [markdown](https://verifymcp.io/servers/com-rationalbloks-mcp/rationalbloks-mcp.md), [page](https://verifymcp.io/servers/com-rationalbloks-mcp/rationalbloks-mcp) ## Channel facts - Endpoint: `https://mcp.rationalbloks.com/` - Transports: `streamable-http` - Auth: `none` - Version: `0.14.0` ## Trust breakdown 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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog) Scored 2026-09-20. - **Endpoint Security**: 46/100 - The endpoint's TLS certificate is valid, in date, and uses a strong key. - Authorisation not fully verified: this server exposes a tool marked destructive (deploy_staging) and its handshake is open, but we could not confirm whether a tool call is gated, so we do not assert it is callable unauthenticated. - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 404, which proves neither a plaintext path nor enforcement. - HSTS check failed: the Strict-Transport-Security header is absent. - DNSSEC check failed: this domain isn't protected by DNSSEC. - **Transport & Reachability**: 100/100 - Verified streamable-http transport via a live MCP handshake. - **Schema Quality & AI Usability**: 81/100 - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name). - AI-judged instruction clarity (excellent). - Context-footprint check failed: tool/resource definitions use about 9077 tokens (~174/item across 52 items; 49 tools + 3 resources), over budget; trim descriptions and params. - Usage-examples check failed: none of the tools include examples. - **Stability & Change Management**: 20/100 - Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses. - **Tool Coverage**: 100/100 - 100% of tools have a non-trivial description (not blank, and not just the tool's name). - 100% of tool parameters carry a description. - **Tool Safety**: 100/100 - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured. - All 8 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation. - An AI judge read all 51 captured unit(s) of tool text and found none that tries to manipulate the model reading it. - **Capabilities**: 100/100 - Implements a current MCP spec version (2026-07-28). ## Install ### How do I install the RationalBloks MCP server? RationalBloks is a hosted endpoint at https://mcp.rationalbloks.com/, 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. ### Claude ```bash claude mcp add --transport http com-rationalbloks-mcp 'https://mcp.rationalbloks.com/' ``` ### Cursor ```json { "mcpServers": { "com-rationalbloks-mcp": { "url": "https://mcp.rationalbloks.com/" } } } ``` ### VS Code ```json { "servers": { "com-rationalbloks-mcp": { "type": "http", "url": "https://mcp.rationalbloks.com/" } } } ``` ### Codex ```toml [mcp_servers.com-rationalbloks-mcp] url = "https://mcp.rationalbloks.com/" ``` ### opencode ```json { "$schema": "https://opencode.ai/config.json", "mcp": { "com-rationalbloks-mcp": { "type": "remote", "url": "https://mcp.rationalbloks.com/", "enabled": true } } } ``` ### OpenClaw ```bash openclaw mcp add com-rationalbloks-mcp --url 'https://mcp.rationalbloks.com/' --transport streamable-http ``` ### Hermes ```yaml mcp_servers: com-rationalbloks-mcp: url: "https://mcp.rationalbloks.com/" ``` ### Netclaw ```json { "McpServers": { "com-rationalbloks-mcp": { "Transport": "http", "Url": "https://mcp.rationalbloks.com/" } } } ``` ### Vellum ```bash assistant mcp add com-rationalbloks-mcp -t streamable-http -u 'https://mcp.rationalbloks.com/' ``` ### Other ```json { "mcpServers": { "com-rationalbloks-mcp": { "type": "http", "url": "https://mcp.rationalbloks.com/" } } } ``` The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs. ## Changelog Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims. ### 2026-09-20 (score 64, +1) No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-09-18 (score 63, +1) - [security] The server rewrote its instructions, which are the text every model session reads - [functional] Server version: 0.13.5 → 0.14.0 - [functional] New tool “list_project_jobs” ### 2026-09-17 (score 62, 0) - [security] Tool “get_job_status” rewrote its description, which is the text the model reads - [functional] Server version: 0.13.4 → 0.13.5 ### 2026-09-16 (score 62, 0) - [security] The server rewrote its instructions, which are the text every model session reads - [security] Tool “update_schema” rewrote its description, which is the text the model reads - [security] Tool “delete_graph_project” rewrote its description, which is the text the model reads - [security] Tool “delete_project” rewrote its description, which is the text the model reads - [security] Tool “create_project” rewrote its description, which is the text the model reads - [security] Tool “create_graph_project” rewrote its description, which is the text the model reads - [security] Tool “rollback_project” rewrote its description, which is the text the model reads - [security] Tool “rollback_graph_project” rewrote its description, which is the text the model reads - [security] Tool “get_schema” rewrote its description, which is the text the model reads - [security] Tool “get_job_status” rewrote its description, which is the text the model reads - [security] Tool “get_graph_schema” rewrote its description, which is the text the model reads - [security] Tool “deploy_staging” rewrote its description, which is the text the model reads - [security] Tool “deploy_production” rewrote its description, which is the text the model reads - [security] Tool “deploy_graph_staging” rewrote its description, which is the text the model reads - [security] Tool “deploy_graph_production” rewrote its description, which is the text the model reads - [functional regression] Schema quality: 157 → 174 - [functional regression] Schema quality: 157 → 173 - [functional] Server version: 0.13.3 → 0.13.4 - [functional] Server version: 0.13.2 → 0.13.3 - [functional] Server version: 0.13.0 → 0.13.2 ### 2026-09-15 (score 62, +1) - [security] The server rewrote its instructions, which are the text every model session reads - [security] Tool “deploy_staging” rewrote its description, which is the text the model reads - [security] Tool “get_graph_template_schemas” rewrote its description, which is the text the model reads - [security] Tool “get_schema_reference” rewrote its description, which is the text the model reads - [security] Tool “get_template_schemas” rewrote its description, which is the text the model reads - [security] Tool “update_graph_schema” rewrote its description, which is the text the model reads - [security] Tool “create_project” rewrote its description, which is the text the model reads - [security] Tool “deploy_graph_production” rewrote its description, which is the text the model reads - [security] Tool “deploy_graph_staging” rewrote its description, which is the text the model reads - [security] Tool “deploy_production” rewrote its description, which is the text the model reads - [security] Tool “get_project_info” rewrote its description, which is the text the model reads - [security] Tool “deploy_production” is now declared destructive - [security] Tool “deploy_staging” is now declared destructive - [security] Tool “deploy_graph_production” is now declared destructive - [security] Tool “deploy_graph_staging” is now declared destructive - [functional improvement] Stability: unverified → 0.03 - [functional] Server version: 0.12.2 → 0.13.0 - [functional] Server version: 0.12.1 → 0.12.2 - [cosmetic] “deploy_production” added an optional parameter “confirm_destructive” - [cosmetic] “deploy_staging” added an optional parameter “confirm_destructive” - [cosmetic] “update_graph_schema” added an optional parameter “dry_run” - [cosmetic] “deploy_graph_production” added an optional parameter “confirm_destructive” - [cosmetic] “deploy_graph_staging” added an optional parameter “confirm_destructive” - [cosmetic] “create_project” dropped the optional parameter “description” - [cosmetic] “create_graph_project” dropped the optional parameter “description” ### 2026-09-14 (score 61) First indexed and scored. ## MCP tools (49) ### `list_projects` (~21 tokens) List Projects List all your RationalBloks projects with their status and URLs ### `get_project` (~28 tokens) Get Project Details Get detailed information about a specific project Input parameters: - `project_id` (string, required): Project ID (UUID) ### `get_schema` (~174 tokens) Get Project Schema Get the JSON schema definition of a project in FLAT format. Returns the schema structure where each table name maps directly to field definitions. This is the same format required for create_project and update_schema. USE CASES: Review current schema before making updates, copy schema as template for new projects, verify schema structure after deployment, learn the correct schema format by example. The returned schema will be in FLAT format: {table_name: {field_name: {type, properties}}}. The response also says whether this saved schema is the deployed one: saved_schema_deployed is true when the last deploy applied it, false when it was saved after the last deploy (undeployed_changes then lists what deploying it would change), and null when no deployed schema is on record. Input parameters: - `project_id` (string, required): Project ID (UUID) ### `get_user_info` (~16 tokens) Get User Info Get information about the authenticated user ### `list_clusters` (~110 tokens) List Resource Pools List your registered BYOC resource pools (client-owned Kubernetes clusters). Each returned cluster has an 'id' you MUST pass as create_project's cluster_id to deploy a project onto your own infrastructure — owned hosting is retired, so every project we operate runs on your own cluster. Registering a pool is a UI action (create a bare Ubuntu box, authorise the key we generate, then we provision it into a cluster automatically) — this tool only lists pools you already registered, it never handles cluster credentials. ### `get_job_status` (~175 tokens) Get Job Status Check the status of a job (a create, deploy, promotion, rollback or deletion). STATUS VALUES: pending (queued), processing (in progress), completed (success), failed. Call it until the status is completed or failed: every job ends, since a job whose server stopped is failed within about three minutes, and a deploy can take up to 15 minutes. If status is 'failed', read failure_side and error: 'customer' means the project's input is proven the cause (an invalid schema, data the new schema does not fit, a change the resource pool cannot hold), and error says what to change; 'platform' means no input of the project is known to cause it: report it to RationalBloks rather than changing the schema. Input parameters: - `job_id` (string, required): Job ID returned from deployment operations ### `list_project_jobs` (~173 tokens) List Project Jobs List a project's jobs, newest first: every create, deploy, promotion, rollback, resource change and module operation, each with its status, error, failure_side and when it started and ended. A job's record is kept for the life of the project, so this is how to find out what an operation did when you no longer have its job_id (after an interruption, or in a later session): the first job of the job_type you want is the latest. Read older jobs a page at a time with offset; a page shorter than limit is the last. Input parameters: - `limit` (integer): Max jobs to return (1-1000, default 100) - `offset` (integer): Jobs to skip, newest first (default 0) - `project_id` (string, required): Project ID (UUID) ### `get_project_info` (~198 tokens) Get Project Info Get detailed project info including deployment status and resource usage. DEPLOYMENT STATUS: Running (healthy), Pending (starting), CrashLoopBackOff (init container failed - usually schema format error), ImagePullBackOff (image build failed). TROUBLESHOOTING: If status is CrashLoopBackOff, the schema is likely in wrong format (nested 'fields' key or missing 'type' properties). Use get_schema to review current schema. If replicas show 0/2, the init container (migration runner) is failing. This is almost always a schema format issue. RETURNS THE LIVE API URL: staging.url and production.url carry the deployed base URL for each environment (append /docs for the interactive OpenAPI docs); github.url is the generated repository. create_project does NOT return a URL, so this is the tool to call once get_job_status reports the deployment finished. Input parameters: - `project_id` (string, required): Project ID (UUID) ### `get_version_history` (~74 tokens) Get Version History Get the deployment and version history (git commits) for a project. Shows all schema changes with commit SHA, timestamp, and message. USE CASES: Review what changed between deployments, find the last working version before issues started, get commit SHA for rollback_project. Input parameters: - `project_id` (string, required): Project ID (UUID) ### `get_template_schemas` (~158 tokens) Get Template Schemas Get pre-built template schemas for common use cases. ⭐ USE THIS FIRST when creating a new project! Templates show the CORRECT schema format with: proper FLAT structure (no 'fields' nesting), every field has a 'type' property, foreign key relationships configured correctly, best practices for field naming and types. Available templates: Start from Scratch (every field type), Team Collaboration (workspaces, channels, messages, tasks), E-Commerce Store (customer profiles, products, orders and their line items, reviews, shipments). Each entry's 'schema' goes to create_project as is or adapted; its 'tables' notes say how each table is authorized. TIP: Study these templates to understand the correct schema format before creating custom schemas. ### `get_schema_reference` (~130 tokens) Get Schema Features Reference Get the reference for ADVANCED schema features the templates do not show — read this before adding authorization or derived fields to a schema. Covers: __policy__ (relationship-based read/write authorization with single- and multi-hop membership paths, and the rules that decide whether adopting it is safe — it replaces creator-ownership per table and fails closed on a null link), computed columns (read-only values derived from other columns), __constraints__ (composite uniqueness), __audit__ (append-only audit log), __admin_write__ (a table only admins write), and how user foreign keys are attributed on create. ### `get_subscription_status` (~19 tokens) Get Subscription Status Get your subscription tier, limits, and usage ### `get_project_usage` (~34 tokens) Get Project Usage Get resource usage metrics (CPU, memory) for a project Input parameters: - `project_id` (string, required): Project ID (UUID) ### `get_project_storage_usage` (~56 tokens) Get Project Storage Usage Get object-storage usage for a project: file count and bytes used against the plan limits. Input parameters: - `environment` (string): Environment: staging or production (default: production) - `project_id` (string, required): Project ID (UUID) ### `list_project_files` (~95 tokens) List Project Files List a project's uploaded files (metadata + public URLs), most recent first. Inspection only — files are not streamed through MCP. Input parameters: - `environment` (string): Environment: staging or production (default: production) - `limit` (integer): Max files to return (1-1000, default 100) - `offset` (integer): Pagination offset (default 0) - `project_id` (string, required): Project ID (UUID) ### `get_schema_at_version` (~47 tokens) Get Schema at Version Get the schema as it was at a specific version/commit Input parameters: - `project_id` (string, required): Project ID (UUID) - `version` (string, required): Commit SHA of the version ### `create_project` (~844 tokens) Create Project Create a new RationalBloks project from a JSON schema. ⚠️ CRITICAL RULES - READ BEFORE CREATING SCHEMA: 1\. FLAT FORMAT (REQUIRED): ✅ CORRECT: {users: {email: {type: "string", max_length: 255}}} ❌ WRONG: {users: {fields: {email: {type: "string"}}}} DO NOT nest under 'fields' key! 2\. FIELD TYPE REQUIREMENTS: • string: MUST have "max_length" (e.g., max_length: 255) • decimal: MUST have "precision" and "scale" (e.g., precision: 10, scale: 2) • datetime: Use "datetime" NOT "timestamp" • ALL fields: MUST have "type" property 3\. AUTOMATIC FIELDS (DON'T define): • id (uuid, primary key) • created_at (datetime) • updated_at (datetime) 4\. USER AUTHENTICATION: ❌ NEVER create "users", "customers", "employees" tables with email/password ✅ USE built-in app_users table Example: { "employee_profiles": { "user_id": {type: "uuid", foreign_key: "app_users.id", required: true}, "department": {type: "string", max_length: 100} } } 5\. AUTHORIZATION: Add user_id → app_users.id to enable "only see your own data" Example: { "orders": { "user_id": {type: "uuid", foreign_key: "app_users.id"}, "total": {type: "decimal", precision: 10, scale: 2} } } 6\. FIELD OPTIONS: • required: true/false • unique: true/false • default: any value • enum: ["val1", "val2"] • foreign_key: "table.id" AVAILABLE TYPES: string, text, integer, decimal, boolean, uuid, date, datetime, json, uuid_array, integer_array, text_array, float_array Array types store PostgreSQL native arrays with automatic GIN indexing: • uuid_array: UUID[] — for sets of references (e.g., tensor coordinates) • integer_array: BIGINT[] — for dimension indices, integer sets • text_array: TEXT[] — for tags, categories, label sets • float_array: DOUBLE PRECISION[] — for weight vectors, scores GIN-indexed operators: @> (contains), <@ (contained_by), && (overlaps) BACKEND ENGINE: • python (default): FastA… Input parameters: - `backend_type` (string): Backend engine: 'python' (FastAPI, default) or 'rust' (Axum, faster). Default: python - `cluster_id` (string, required): REQUIRED — BYOC resource pool ID (from list_clusters) to deploy this project onto your own cluster. Owned hosting is retired: a project we operate must run on your own infrastructure. Register a pool… - `name` (string, required): Project name - `schema` (object, required): JSON schema in FLAT format (table_name → field_name → properties). Every field MUST have a 'type' property. Use get_template_schemas to see valid examples. ### `update_schema` (~372 tokens) Update Schema Update a project's schema (saves to database, does NOT deploy). ⚠️ CRITICAL: Follow ALL rules from create_project: • FLAT format (no 'fields' nesting) • string: max_length (default 255) • decimal: precision + scale (default 10, 2) • Use "datetime" NOT "timestamp" • DON'T define: id, created_at, updated_at • NEVER create users/customers/employees tables (use app_users) ⚠️ MIGRATION RULES: • New fields MUST be "required": false OR have "default" value • Cannot add required field without default to existing tables • Safe: {new_field: {type: "string", max_length: 100, required: false}} WORKFLOW: 1\. Use get_schema to see current schema 2\. Modify following ALL rules 3\. (optional) Call update_schema with dry_run=true to preview the migration first 4\. Call update_schema (saves only) 5\. Call deploy_staging to apply changes 6\. Monitor with get_job_status DRY RUN: pass dry_run=true to preview what a deploy WOULD change — renames, drops, creates — without saving or deploying anything. The response flags destructive operations (dropped tables/columns) so you can review before applying. NOTE: Without dry_run this only saves the schema. You MUST call deploy_staging afterwards to apply changes. Input parameters: - `dry_run` (boolean): Preview the planned migration (renames/drops/creates) without saving or deploying. Nothing is applied. - `project_id` (string, required): Project ID (UUID) - `schema` (object, required): New JSON schema in FLAT format (table_name → field_name → properties). Every field MUST have a 'type' property. ### `deploy_staging` (~324 tokens) Deploy to Staging Deploy a project to the staging environment. This triggers: (1) Schema validation, (2) Docker image build, (3) GitHub commit, (4) Kubernetes deployment, (5) Database migrations. The operation is ASYNCHRONOUS - it returns immediately with a job_id. Use get_job_status with the job_id to monitor progress. Deployment typically takes 2-5 minutes depending on schema complexity. If deployment fails, read the job's error first: one that starts with 'RationalBloks platform error' is the platform's, not the schema's. Otherwise check: (1) Schema format is FLAT (no 'fields' nesting), (2) Every field has a 'type' property, (3) Foreign keys reference existing tables, (4) No PostgreSQL reserved words in table/field names. Use get_project_info to see if the deployment succeeded. A deploy that drops data is refused until you pass confirm_destructive=true after reviewing the plan. One operation runs on a project at a time: while another runs, the call is refused and the refusal names the running job; wait for it with get_job_status, then call again. While RationalBloks is being updated, the call is refused with 'RationalBloks is being updated': call it again in a few minutes. Input parameters: - `confirm_destructive` (boolean): Set true only after reviewing the plan: a deploy that drops tables, columns, entities, relationships or fields is refused without it - `project_id` (string, required): Project ID (UUID) ### `deploy_production` (~151 tokens) Deploy to Production Promote staging to production (requires paid plan) A deploy that drops data is refused until you pass confirm_destructive=true after reviewing the plan. One operation runs on a project at a time: while another runs, the call is refused and the refusal names the running job; wait for it with get_job_status, then call again. While RationalBloks is being updated, the call is refused with 'RationalBloks is being updated': call it again in a few minutes. Input parameters: - `confirm_destructive` (boolean): Set true only after reviewing the plan: a deploy that drops tables, columns, entities, relationships or fields is refused without it - `project_id` (string, required): Project ID (UUID) ### `delete_project` (~126 tokens) Delete Project Delete a project (removes GitHub repo, K8s deployments, and database). It runs as a job: poll the returned job_id with get_job_status until it is completed. One operation runs on a project at a time: while another runs, the call is refused and the refusal names the running job; wait for it with get_job_status, then call again. While RationalBloks is being updated, the call is refused with 'RationalBloks is being updated': call it again in a few minutes. Input parameters: - `project_id` (string, required): Project ID (UUID) ### `rollback_project` (~192 tokens) Rollback Project Rollback a project to a previous version. ⚠️ WARNING: This reverts schema AND code to the specified commit. Database data is NOT rolled back. Use get_version_history to find the commit SHA of the version you want to rollback to. After rollback, use get_job_status to monitor the redeployment. Rollback is useful when a schema change breaks deployment. One operation runs on a project at a time: while another runs, the call is refused and the refusal names the running job; wait for it with get_job_status, then call again. While RationalBloks is being updated, the call is refused with 'RationalBloks is being updated': call it again in a few minutes. Input parameters: - `environment` (string): Environment: staging or production (default: staging) - `project_id` (string, required): Project ID (UUID) - `version` (string, required): Commit SHA or version to rollback to ### `rename_project` (~45 tokens) Rename Project Rename a project (changes display name, not project_code) Input parameters: - `name` (string, required): New display name for the project - `project_id` (string, required): Project ID (UUID) ### `get_graph_schema` (~119 tokens) Get Graph Schema Get the graph schema definition of a project. Returns the hierarchical schema with nodes (entities) and relationships. Graph schemas define entity hierarchies and typed relationships — a different format than relational flat-table schemas. The response also says whether this saved schema is the deployed one: saved_schema_deployed is true when the last deploy applied it, false when it was saved after the last deploy (undeployed_changes then lists what deploying it would change), and null when no deployed schema is on record. Input parameters: - `project_id` (string, required): Project ID (UUID) ### `get_graph_template_schemas` (~160 tokens) Get Graph Template Schemas Get pre-built graph template schemas for common use cases. ⭐ USE THIS FIRST when creating a new graph project! Templates show the CORRECT graph schema format with: proper node definitions (description, flat_labels, schema with flat field definitions), relationship configurations (from, to, cardinality, data_schema), and hierarchical entity nesting. Available templates: Start from Scratch (hierarchy, flat labels, every field type), Social Network (people, organizations, content, follows), Knowledge Graph (topic hierarchy, articles, authors, concepts), Product Catalog (products, categories, suppliers, reviews). Each entry's 'schema' goes to create_graph_project as is or adapted. TIP: Study these templates to understand the correct graph schema format before creating custom schemas. ### `get_graph_version_history` (~61 tokens) Get Graph Version History Get the deployment and version history for a graph project. Shows all schema changes with commit SHAs, timestamps, version numbers, and messages. Use this to find a specific version for rollback operations. Input parameters: - `project_id` (string, required): Project ID (UUID) ### `get_graph_schema_at_version` (~72 tokens) Get Graph Schema at Version Get the graph schema as it existed at a specific version/commit. Use get_graph_version_history to find commit SHAs. Useful for comparing schemas across versions or auditing changes. Input parameters: - `project_id` (string, required): Project ID (UUID) - `version` (string, required): Commit SHA of the version to retrieve ### `get_graph_project_info` (~58 tokens) Get Graph Project Info Get detailed graph project information including Kubernetes deployment status, Neo4j database health, pod status, and resource usage. Use this after deployment to verify the graph project is running correctly. Input parameters: - `project_id` (string, required): Project ID (UUID) ### `create_graph_project` (~760 tokens) Create Graph Project Create a new Neo4j graph database project from a hierarchical JSON schema. ⚠️ GRAPH SCHEMA FORMAT — READ BEFORE CREATING: Graph schemas define nodes (entities) and relationships, NOT flat database tables. Each field is a dict with "type" and optional "required": true (defaults to false). SCHEMA STRUCTURE: { "nodes": { "EntityName": { "description": "What this entity represents", "flat_labels": ["AdditionalLabel"], "schema": { "field_name": {"type": "string", "required": true}, "other_field": {"type": "integer"} } } }, "relationships": { "RELATIONSHIP_TYPE": { "from": "EntityName", "to": "OtherEntity", "cardinality": "MANY_TO_MANY", "data_schema": { "field_name": {"type": "date"} } } } } FIELD TYPES: string, integer, float, boolean, date, json CARDINALITY OPTIONS: ONE_TO_ONE, ONE_TO_MANY, MANY_TO_ONE, MANY_TO_MANY HIERARCHICAL NODES: Nest entities inside parent entities to create type hierarchies. Child entities inherit parent labels automatically. Example: { "nodes": { "Animal": { "description": "Base animal entity", "flat_labels": ["LivingThing"], "schema": { "name": {"type": "string", "required": true}, "habitat": {"type": "string"} }, "Dog": { "description": "A dog (inherits Animal labels)", "flat_labels": ["Pet"], "schema": { "breed": {"type": "string", "required": true}, "trained": {"type": "boolean"} } } } }, "relationships": { "OWNS": { "from": "Person", "to": "Animal", "cardinality": "ONE_TO_MANY" } } } RULES: 1\. "nodes" key is REQUIRED — must contain at least one entity 2\. Each entity needs "description" and "schema" with field definitions 3\. Each field is {"type": "...", "required": true/false} — required defaults to false 4\. Relationship "from"/"to" must reference defined node names 5\. Relationship type… Input parameters: - `cluster_id` (string, required): REQUIRED — BYOC resource pool ID (from list_clusters) to deploy this graph project onto your own cluster. Owned hosting is retired: a project we operate must run on your own infrastructure. Register… - `name` (string, required): Project name - `schema` (object, required): Graph schema with 'nodes' and optionally 'relationships' keys. Use get_graph_template_schemas to see valid examples. ### `update_graph_schema` (~289 tokens) Update Graph Schema Update a graph project's schema (saves to database, does NOT deploy). ⚠️ Follow ALL rules from create_graph_project: • Must have "nodes" key with at least one entity • Each entity needs "description" and "schema" with field definitions • Each field is {"type": "...", "required": true/false} — required defaults to false • Relationships need "from", "to", and "cardinality" • Field types: string, integer, float, boolean, date, json • Relationship types should be UPPER_SNAKE_CASE • Entity names should be PascalCase WORKFLOW: 1\. Use get_graph_schema to see current schema 2\. Modify following all rules 3\. Call update_graph_schema (saves only) 4\. Call deploy_graph_staging to apply changes 5\. Monitor with get_job_status DRY RUN: pass dry_run=true to preview what a deploy WOULD change (renames, deletions) without saving. NOTE: This only saves the schema. You MUST call deploy_graph_staging afterwards to deploy. Input parameters: - `dry_run` (boolean): Preview the planned migration (renames/deletions) without saving or deploying. Nothing is applied. - `project_id` (string, required): Project ID (UUID) - `schema` (object, required): New graph schema with 'nodes' and optionally 'relationships' keys. ### `deploy_graph_staging` (~239 tokens) Deploy Graph to Staging Deploy a graph project to the staging environment. This triggers: (1) Schema validation, (2) Neo4j entity code generation, (3) Docker image build, (4) GitHub commit, (5) Kubernetes deployment with Neo4j instance. The operation is ASYNCHRONOUS — returns immediately with a job_id. Use get_job_status to monitor progress. Deployment typically takes 2-5 minutes. Use get_graph_project_info to verify deployment succeeded. A deploy that drops data is refused until you pass confirm_destructive=true after reviewing the plan. One operation runs on a project at a time: while another runs, the call is refused and the refusal names the running job; wait for it with get_job_status, then call again. While RationalBloks is being updated, the call is refused with 'RationalBloks is being updated': call it again in a few minutes. Input parameters: - `confirm_destructive` (boolean): Set true only after reviewing the plan: a deploy that drops tables, columns, entities, relationships or fields is refused without it - `project_id` (string, required): Project ID (UUID) ### `deploy_graph_production` (~168 tokens) Deploy Graph to Production Promote graph staging to production. Creates a separate production Neo4j instance with its own credentials and database. Requires paid plan. A deploy that drops data is refused until you pass confirm_destructive=true after reviewing the plan. One operation runs on a project at a time: while another runs, the call is refused and the refusal names the running job; wait for it with get_job_status, then call again. While RationalBloks is being updated, the call is refused with 'RationalBloks is being updated': call it again in a few minutes. Input parameters: - `confirm_destructive` (boolean): Set true only after reviewing the plan: a deploy that drops tables, columns, entities, relationships or fields is refused without it - `project_id` (string, required): Project ID (UUID) ### `delete_graph_project` (~133 tokens) Delete Graph Project Delete a graph project (removes GitHub repo, K8s deployments, Neo4j database, and credentials). It runs as a job: poll the returned job_id with get_job_status until it is completed. One operation runs on a project at a time: while another runs, the call is refused and the refusal names the running job; wait for it with get_job_status, then call again. While RationalBloks is being updated, the call is refused with 'RationalBloks is being updated': call it again in a few minutes. Input parameters: - `project_id` (string, required): Project ID (UUID) ### `rollback_graph_project` (~186 tokens) Rollback Graph Project Rollback a graph project to a previous version. ⚠️ WARNING: This reverts schema AND code to the specified commit. Neo4j data is NOT rolled back. Use get_graph_version_history to find the commit SHA of the version you want to rollback to. After rollback, the graph API will be redeployed with the old schema. One operation runs on a project at a time: while another runs, the call is refused and the refusal names the running job; wait for it with get_job_status, then call again. While RationalBloks is being updated, the call is refused with 'RationalBloks is being updated': call it again in a few minutes. Input parameters: - `environment` (string): Environment: staging or production (default: staging) - `project_id` (string, required): Project ID (UUID) - `version` (string, required): Commit SHA to rollback to ### `create_graph_node` (~196 tokens) Create Graph Node Create a single node in a deployed graph project. REQUIRES: Project must be deployed (use deploy_graph_staging first). The entity_type must match an entity key from the project schema. Use get_graph_data_schema to see available entity types and their fields. Example: entity_type: "person" entity_id: "alan-turing-001" data: {"name": "Alan Turing", "birth_year": 1912, "field": "Computer Science"} The entity_id is your unique identifier — use meaningful IDs for knowledge graphs. Input parameters: - `data` (object, required): Node properties matching the entity schema - `entity_id` (string, required): Unique identifier for the node - `entity_type` (string, required): Entity key (e.g., 'person', 'concept') - `environment` (string): Environment: staging or production (default: staging) - `project_id` (string, required): Project ID (UUID) ### `get_graph_node` (~95 tokens) Get Graph Node Get a specific node by its entity_id from a deployed graph project. Returns all node properties including created_at and updated_at timestamps. Input parameters: - `entity_id` (string, required): The node's entity_id - `entity_type` (string, required): Entity key (e.g., 'person', 'concept') - `environment` (string): Environment: staging or production (default: staging) - `project_id` (string, required): Project ID (UUID) ### `list_graph_nodes` (~121 tokens) List Graph Nodes List nodes of a specific entity type from a deployed graph project. Supports pagination with limit/offset. Returns nodes ordered by creation date (newest first). Input parameters: - `entity_type` (string, required): Entity key (e.g., 'person', 'concept') - `environment` (string): Environment: staging or production (default: staging) - `limit` (integer): Max results (default: 100, max: 1000) - `offset` (integer): Pagination offset (default: 0) - `project_id` (string, required): Project ID (UUID) ### `update_graph_node` (~108 tokens) Update Graph Node Update properties of an existing node in a deployed graph project. Only send the fields you want to change — unspecified fields remain unchanged. Input parameters: - `data` (object, required): Properties to update (partial update) - `entity_id` (string, required): The node's entity_id - `entity_type` (string, required): Entity key (e.g., 'person', 'concept') - `environment` (string): Environment: staging or production (default: staging) - `project_id` (string, required): Project ID (UUID) ### `delete_graph_node` (~99 tokens) Delete Graph Node Delete a node and all its relationships from a deployed graph project. ⚠️ This also removes all relationships connected to this node (DETACH DELETE). Input parameters: - `entity_id` (string, required): The node's entity_id - `entity_type` (string, required): Entity key (e.g., 'person', 'concept') - `environment` (string): Environment: staging or production (default: staging) - `project_id` (string, required): Project ID (UUID) ### `create_graph_relationship` (~187 tokens) Create Graph Relationship Create a relationship between two nodes in a deployed graph project. The rel_type must match a relationship key from the project schema. Use get_graph_data_schema to see available relationship types. Example: rel_type: "authored" from_id: "alan-turing-001" to_id: "on-computable-numbers-001" data: {"year": 1936} The from_id and to_id must be entity_ids of existing nodes. Input parameters: - `data` (object): Relationship properties (optional) - `environment` (string): Environment: staging or production (default: staging) - `from_id` (string, required): Source node entity_id - `project_id` (string, required): Project ID (UUID) - `rel_type` (string, required): Relationship key (e.g., 'authored', 'related_to') - `to_id` (string, required): Target node entity_id ### `get_node_relationships` (~127 tokens) Get Node Relationships Get all relationships connected to a specific node. Supports direction filtering (incoming, outgoing, both) and relationship type filtering. Input parameters: - `direction` (string): Filter: incoming, outgoing, or both (default: both) - `entity_id` (string, required): The node's entity_id - `entity_type` (string, required): Entity key of the node - `environment` (string): Environment: staging or production (default: staging) - `project_id` (string, required): Project ID (UUID) - `rel_type_filter` (string): Filter by relationship type (UPPER_SNAKE_CASE) ### `delete_graph_relationship` (~83 tokens) Delete Graph Relationship Delete a specific relationship by its internal ID. Use get_node_relationships to find relationship IDs. Input parameters: - `environment` (string): Environment: staging or production (default: staging) - `project_id` (string, required): Project ID (UUID) - `rel_id` (integer, required): Internal relationship ID (from get_node_relationships) - `rel_type` (string, required): Relationship key ### `bulk_create_graph_nodes` (~231 tokens) Bulk Create Graph Nodes Create multiple nodes at once (up to 500 per call). Uses Neo4j UNWIND for high performance. Essential for knowledge graph population — create hundreds of entities from a single book chapter or article. Each node needs: entity_id (unique string) and data (properties dict). Example: entity_type: "concept" nodes: [ {"entity_id": "quantum-mechanics-001", "data": {"name": "Quantum Mechanics", "field": "Physics"}}, {"entity_id": "wave-function-001", "data": {"name": "Wave Function", "field": "Physics"}}, {"entity_id": "superposition-001", "data": {"name": "Superposition", "field": "Physics"}} ] Input parameters: - `entity_type` (string, required): Entity key for all nodes - `environment` (string): Environment: staging or production (default: staging) - `nodes` (array, required): List of nodes. Each: {entity_id: string, data: {properties}} - `project_id` (string, required): Project ID (UUID) ### `bulk_create_graph_relationships` (~213 tokens) Bulk Create Graph Relationships Create multiple relationships at once (up to 500 per call). Uses Neo4j UNWIND for high performance. Essential for connecting knowledge — link hundreds of concepts, people, and events in one operation. Each relationship needs: from_id, to_id, and optional data (properties). Example: rel_type: "related_to" relationships: [ {"from_id": "quantum-mechanics-001", "to_id": "wave-function-001", "data": {"strength": "strong"}}, {"from_id": "quantum-mechanics-001", "to_id": "superposition-001", "data": {"strength": "strong"}} ] Input parameters: - `environment` (string): Environment: staging or production (default: staging) - `project_id` (string, required): Project ID (UUID) - `rel_type` (string, required): Relationship key for all relationships - `relationships` (array, required): List of relationships. Each: {from_id, to_id, data?} ### `search_graph_nodes` (~193 tokens) Search Graph Nodes Search for nodes by property values in a deployed graph project. Supports exact match and contains search (prefix value with ~ for contains). Examples: Exact: filters: {"name": "Alan Turing"} Contains: filters: {"name": "~turing"} (case-insensitive) Combined: entity_type: "person", filters: {"field": "~physics"} Without entity_type, searches ALL node types. Input parameters: - `entity_type` (string): Entity key to filter by (optional — omit to search all types) - `environment` (string): Environment: staging or production (default: staging) - `filters` (object, required): Property filters. Prefix value with ~ for contains search. - `limit` (integer): Max results (default: 100, max: 1000) - `offset` (integer): Pagination offset (default: 0) - `project_id` (string, required): Project ID (UUID) ### `fulltext_search_graph` (~203 tokens) Full-Text Search Graph Search across ALL string properties of ALL nodes in a deployed graph using free-text queries. Unlike search_graph_nodes (which filters by specific property), this searches every text field at once. Perfect for finding knowledge when you don't know which property contains the answer. Example: query "quantum" searches name, description, summary, notes, and all other string fields. Returns nodes with _match_fields showing which properties matched. Optionally filter by entity_type to narrow results. Input parameters: - `entity_type` (string): Entity key to filter by (optional — omit to search all types) - `environment` (string): Environment: staging or production (default: staging) - `limit` (integer): Max results (default: 50, max: 500) - `offset` (integer): Pagination offset (default: 0) - `project_id` (string, required): Project ID (UUID) - `query` (string, required): Search text (case-insensitive, min 2 chars) ### `traverse_graph` (~256 tokens) Traverse Graph Walk the graph from a starting node, discovering connected knowledge. Returns all nodes reachable within max_depth hops, with their distance from the start. Essential for exploring knowledge graphs — find related concepts, trace connections, discover clusters. Example: Start from "Alan Turing", traverse outgoing relationships up to 3 hops deep: start_entity_type: "person" start_entity_id: "alan-turing-001" max_depth: 3 direction: "outgoing" Supports filtering by relationship types and direction. Input parameters: - `direction` (string): Direction: outgoing, incoming, or both (default: both) - `environment` (string): Environment: staging or production (default: staging) - `limit` (integer): Max results (default: 100, max: 1000) - `max_depth` (integer): Maximum traversal depth (default: 3, max: 10) - `project_id` (string, required): Project ID (UUID) - `relationship_types` (array): Filter by relationship types (UPPER_SNAKE_CASE). Omit for all types. - `start_entity_id` (string, required): Entity ID of the starting node - `start_entity_type` (string, required): Entity key of the starting node ### `get_graph_statistics` (~77 tokens) Get Graph Statistics Get statistics about a deployed graph: total node count, total relationship count, counts per entity type, counts per relationship type. Essential for understanding the current state of a knowledge graph before adding more data. Input parameters: - `environment` (string): Environment: staging or production (default: staging) - `project_id` (string, required): Project ID (UUID) ### `get_graph_data_schema` (~112 tokens) Get Graph Data Schema Get the runtime schema of a DEPLOYED graph project — shows the actual entity types and relationship types available for data operations. Returns: Available entity keys (for create_graph_node, list_graph_nodes, etc.) and relationship keys (for create_graph_relationship, etc.). ⭐ USE THIS FIRST before creating nodes/relationships to know what entity_type and rel_type values are valid. Input parameters: - `environment` (string): Environment: staging or production (default: staging) - `project_id` (string, required): Project ID (UUID) ## Diagnostics Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-rationalbloks-mcp/mcp#diagnostics ## Score history - 2026-09-20: 64 - 2026-09-19: 63 - 2026-09-18: 63 - 2026-09-17: 62 - 2026-09-16: 62 - 2026-09-15: 62 - 2026-09-14: 61 ## Common questions ### What is the RationalBloks MCP server? RationalBloks is an MCP server listed in the public MCP registry as com.rationalbloks/mcp. Deploy production REST and Neo4j Graph APIs from JSON schemas in seconds. 49 tools. This page covers its hosted endpoint (https://mcp.rationalbloks.com/). ### Is the RationalBloks MCP server safe to use? RationalBloks scores 64 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 RationalBloks MCP server expose? RationalBloks exposes 49 tools: list_projects, get_project, get_schema, get_user_info, list_clusters, and 44 more. Their descriptions and schemas cost roughly 8,108 tokens of context every time the server is loaded. ### Does the RationalBloks MCP server require authentication? No. We connected to RationalBloks without credentials and it answered, so anything it exposes is reachable by anyone who knows the address. ### Is the RationalBloks MCP server still maintained? RationalBloks is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced. ## Links - Remote endpoint: https://mcp.rationalbloks.com/ - Repository: https://github.com/rationalbloks/rationalbloks-mcp - Changelog RSS feed: https://verifymcp.io/servers/com-rationalbloks-mcp/mcp.xml - Changelog JSON feed: https://verifymcp.io/servers/com-rationalbloks-mcp/mcp.json - HTML version of this page: https://verifymcp.io/servers/com-rationalbloks-mcp/mcp