RationalBloks

by rationalbloks.com MCP server in Cloud & infrastructure, indexed and not reviewed

HostedLocalvendor's own

Not reviewed

No score, grade or rank. This listing is facts from the official MCP registry and our own checks, and it stays out of the rankings until the panel reviews it.

How the index works

Deploy production REST and Neo4j Graph APIs from JSON schemas in seconds.

What the official MCP registry says

Facts

MCP registry
com.rationalbloks/mcp · 0.16.0
Endpoint
https://mcp.rationalbloks.com/
Packages
pypi rationalbloks-mcp stdio
PyPI / week
213
GitHub stars
1
Registry entry
updated 7 Oct 2026

From the official MCP registry, the package registries and our own checks. JSON · Markdown

Why it's listed

  • It's published in the registry under rationalbloks.com, a namespace the registry only gives to whoever proves they control that domain.

Being indexed says nothing about quality, and nobody can pay for it. Is this yours? Ask for a review.

Tools it lists 50 · about 13,624 tokens of context · checked 6 days ago

ToolWhat it doesHint
list_projectsList ProjectsList all your RationalBloks projects with their status and URLsread-only
get_projectGet Project DetailsGet detailed information about a specific projectread-only
get_schemaGet Project SchemaGet 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.…read-only
get_user_infoGet User InfoGet information about the authenticated userread-only
list_clustersList Resource PoolsList 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…read-only
get_job_statusGet Job StatusCheck 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:…read-only
list_project_jobsList Project JobsList 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…read-only
get_project_infoGet Project InfoGet detailed project info including deployment status and resource usage. DEPLOYMENT STATUS: Running (healthy), Pending (starting), CrashLoopBackOff (init container failed - usually schema format error),…read-only
get_version_historyGet Version HistoryGet 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…read-only
get_template_schemasGet Template SchemasGet 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'…read-only
get_schema_referenceGet Schema Features ReferenceGet 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…read-only
get_subscription_statusGet Subscription StatusGet your subscription tier, limits, and usageread-only
get_project_usageGet Project UsageGet resource usage metrics (CPU, memory) for a projectread-only
get_project_storage_usageGet Project Storage UsageGet object-storage usage for a project: file count and bytes used against the plan limits.read-only
list_project_filesList Project FilesList a project's uploaded files (metadata + public URLs), most recent first. Inspection only — files are not streamed through MCP.read-only
get_schema_at_versionGet Schema at VersionGet the schema as it was at a specific version/commitread-only
create_projectCreate ProjectCreate 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:…writes
update_schemaUpdate SchemaUpdate 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…writes
patch_schemaPatch SchemaChange PART of a project's schema (saves to database, does NOT deploy). Send only the change. The server applies it to the saved schema, in order and all together, and keeps every table and field it does not touch —…writes
deploy_stagingDeploy to StagingDeploy 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…writes
deploy_productionDeploy to ProductionPromote 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…writes
delete_projectDelete ProjectDelete 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,…writes
rollback_projectRollback ProjectRollback 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…writes
rename_projectRename ProjectRename a project (changes display name, not project_code)writes
get_graph_schemaGet Graph SchemaGet 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…read-only
get_graph_template_schemasGet Graph Template SchemasGet 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,…read-only
get_graph_version_historyGet Graph Version HistoryGet 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.read-only
get_graph_schema_at_versionGet Graph Schema at VersionGet 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.read-only
get_graph_project_infoGet Graph Project InfoGet 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.read-only
create_graph_projectCreate Graph ProjectCreate 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…writes
update_graph_schemaUpdate Graph SchemaUpdate 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…writes
deploy_graph_stagingDeploy Graph to StagingDeploy 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…writes
deploy_graph_productionDeploy Graph to ProductionPromote 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…writes
delete_graph_projectDelete Graph ProjectDelete 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…writes
rollback_graph_projectRollback Graph ProjectRollback 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…writes
create_graph_nodeCreate Graph NodeCreate 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…writes
get_graph_nodeGet Graph NodeGet a specific node by its entity_id from a deployed graph project. Returns all node properties including created_at and updated_at timestamps.read-only
list_graph_nodesList Graph NodesList nodes of a specific entity type from a deployed graph project. Supports pagination with limit/offset. Returns nodes ordered by creation date (newest first).read-only
update_graph_nodeUpdate Graph NodeUpdate properties of an existing node in a deployed graph project. Only send the fields you want to change — unspecified fields remain unchanged.writes
delete_graph_nodeDelete Graph NodeDelete a node and all its relationships from a deployed graph project. ⚠️ This also removes all relationships connected to this node (DETACH DELETE).writes
create_graph_relationshipCreate Graph RelationshipCreate 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:…writes
get_node_relationshipsGet Node RelationshipsGet all relationships connected to a specific node. Supports direction filtering (incoming, outgoing, both) and relationship type filtering.read-only
delete_graph_relationshipDelete Graph RelationshipDelete a specific relationship by its internal ID. Use get_node_relationships to find relationship IDs.writes
bulk_create_graph_nodesBulk Create Graph NodesCreate 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:…writes
bulk_create_graph_relationshipsBulk Create Graph RelationshipsCreate 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…writes
search_graph_nodesSearch Graph NodesSearch 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":…read-only
fulltext_search_graphFull-Text Search GraphSearch 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…read-only
traverse_graphTraverse GraphWalk 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…read-only
get_graph_statisticsGet Graph StatisticsGet 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…read-only
get_graph_data_schemaGet Graph Data SchemaGet 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…read-only

What https://mcp.rationalbloks.com/ answered to tools/list, asked without credentials over MCP 2026-07-28. The token figure is the size of the list as sent, divided by four; a model sees about that much before it calls anything. Full definitions, input schemas included, are in the listing's JSON under mcpTools.

How its tools read to an agent 0 errors · 17 warnings · 1 note

  • warnTC07create_graph_projectthe description is about 648 tokens
  • warnTC07create_projectthe description is about 653 tokens
  • warnTC07patch_schemathe description is about 505 tokens
  • warnTC13bulk_create_graph_nodesnodes[].data (object with no properties)
  • warnTC13bulk_create_graph_relationshipsrelationships[].data (object with no properties)
  • warnTC13create_graph_nodedata (object with no properties)
  • warnTC13create_graph_projectschema (object with no properties)
  • warnTC13create_graph_relationshipdata (object with no properties)
  • warnTC13create_projectschema (object with no properties)
  • warnTC13patch_schemaoperations[] (object with no properties)
  • warnTC13search_graph_nodesfilters (object with no properties)
  • warnTC13update_graph_nodedata (object with no properties)
  • warnTC13update_graph_schemaschema (object with no properties)
  • warnTC13update_schemaschema (object with no properties)
  • warnTC21delete_projectdescribed almost the same as delete_graph_project (92% of the same words)
  • warnTC21deploy_productiondescribed almost the same as deploy_graph_production (83% of the same words)
  • warnTC23server50 tools
  • noteTC24server50 of 50 tools have no outputSchema

The checks from /check and anchor check, run each day on the list above: about 13,624 tokens of definitions. Not part of the score yet. Check your own server.

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.