RationalBloks
https://mcp.rationalbloks.com/ ↗
Description
Deploy production REST and Neo4j Graph APIs from JSON schemas in seconds. 48 tools.
What our measurements say
RationalBloks is a remote MCP server published at mcp.rationalbloks.com. It has been probed 6 times since 9/14/2026. It answered in 6 of them (100.0%), a near-uninterrupted record. Median response time is 148 ms, placing it among the faster endpoints. It exposes a broad tool surface of 48 tools. On the protocol side it speaks the 2026-07-28 stateless spec.
Agent readability score
Can an LLM agent pick the right tool here — names, descriptions and parameter clarity are assessed.
Agent readability score
Strengths
- Tool names are generally descriptive and action-oriented (e.g., 'deploy_staging', 'rollback_project')
- Many descriptions include specific use cases and constraints (e.g., 'FLAT format requirements')
- Parameters are clearly defined with required/optional status and data types
Weaknesses
- Some tool names are too generic (e.g., 'get_project' vs 'get_project_info')
- A few descriptions are cut off or incomplete (e.g., 'get_schema' description ends mid-sentence')
- Parameter types like 'data' in graph tools lack specific field definitions
get_schema— Description cut off mid-sentenceget_project— Too generic compared to 'get_project_info'create_graph_node— Parameter 'data' lacks specific field definitionsdelete_project— No error handling details specified
Verdict
Event narrative
Risk: low
- 2026-09-14T06:26:32.997Z — smokeOk changed from null to false · Potential compliance risk detected
- 2026-09-14T08:31:43.472Z — smokeOk changed from false to null · Risk indication reverted, requires investigation
Advice
Schema compliance
tools/list structure, inputSchema validity, and a functional smoke test — the components of the 0-100 score.
- tools/list schema valid
- inputSchema is valid JSON Schema
- Smoke test failed · last run:
- Cold-start: cold 38ms → warm 38ms (penalty 0ms)
Tools
Tools the server advertised in the latest measurement — measured, not catalog-claimed.
list_projectsList all your RationalBloks projects with their status and URLs
get_projectGet detailed information about a specific project
project_idstringrequired
get_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. 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}}}
project_idstringrequired
get_user_infoGet information about the authenticated user
list_clustersList 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_statusCheck the status of a deployment job. STATUS VALUES: pending (job queued), running (deployment in progress), completed (success), failed (deployment failed). TIMELINE: Typical deployment takes 2-5 minutes. If status is 'running' for >10 minutes, check get_project_info for detailed pod status. If status is 'failed', use get_project_info to see deployment errors and check schema format (must be FLAT, no 'fields' nesting).
job_idstringrequired
get_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), 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.
project_idstringrequired
get_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 before issues started, get commit SHA for rollback_project.
project_idstringrequired
get_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' property, foreign key relationships configured correctly, best practices for field naming and types. Available templates: E-commerce (products, orders, customers), Team collaboration (projects, tasks, users), General purpose templates. You can use these templates directly with create_project or modify them for your needs. TIP: Study these templates to understand the correct schema format before creating custom schemas.
get_schema_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 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), and how user foreign keys are attributed on create.
get_subscription_statusGet your subscription tier, limits, and usage
get_project_usageGet resource usage metrics (CPU, memory) for a project
project_idstringrequired
Availability history
Event log
Derived by comparing consecutive probes — changes in era, protocol version, build and reachability.
- Added to watch — era: Dual-era
Get your badge
Add this badge to your README — it updates automatically as measurements change.
[](https://mcpmetrics.io/servers/com-rationalbloks-mcp)<a href="https://mcpmetrics.io/servers/com-rationalbloks-mcp"><img src="https://mcpmetrics.io/badge/com.rationalbloks/mcp/era.svg" alt="mcpmetrics"></a>You are seeing the last 7 days. Sign up for the full history. Which check failed and why is in the dashboard.
Sign up free to seeSimilar MCP servers
The catalog entries whose name and description are closest to this one, found with the same index the search box uses.
- RationalBloksmcp.rationalbloks.com
Deploy production REST APIs from JSON schemas in seconds. Manage projects, schemas, and deployments.
- Unix week number from secondsagent-observatory-sensor.nolimit-observatory.workers.dev
Unix week number from seconds
- Unix quarter 1-4 from secondsagent-observatory-sensor.nolimit-observatory.workers.dev
Unix quarter 1-4 from seconds
- Unix day-of-year from secondsagent-observatory-sensor.nolimit-observatory.workers.dev
Unix day-of-year from seconds
- Current UTC hour from unix secondsagent-observatory-sensor.nolimit-observatory.workers.dev
Current UTC hour from unix seconds
- Unix month 1-12 from secondsagent-observatory-sensor.nolimit-observatory.workers.dev
Unix month 1-12 from seconds
Comments
Sign in to write a comment
No comments yet. Be the first.