Skip to content
External endpointresponds

Ross ERP Data Dictionary

Structure-only reference for the vanilla Ross ERP 8.0 schema, UI menu tree, and program catalog.

Endpoint URL
https://mcp.rossdata.dev/mcp
Current status
responds
Last checked
Aug 17, 2026, 05:04 AM UTC
Check
MCP initialize · 8s limit
Latency
295 ms
Response record
2 of 2 rounds
Transport
streamable-http
Source
mcp_registry
Registry name
dev.rossdata/data-dictionary

Current observation

This endpoint answered at its latest recorded check.

What this server reports about itself

Self-reported at initialize. Not verified by Licium.

Server name
rossdata.dev
Version
1.0.0
Capability keys
tools
Tool names
schema_stats, list_objects, find_column, lookup_table, search_columns, search_all, get_ddl, graph_neighbors, path_between, facility_stats, list_facilities, search_facilities, lookup_facility, table_facilities, facility_programs, program_stats, list_programs, search_programs, lookup_program, table_programs, program_facilities
Instructions excerpt

Reference for the standard Ross ERP 8.0 database schema (FIN + MAN). It describes the shape of the database, not its contents: table and column definitions, DDL, the UI menu tree and the program catalog. No business data, no customer records, no program source — structure only. SCHEMA layer: start with schema_stats to orient, list_objects to browse/filter by type or module, find_column to locate a column across tables. Use lookup_table for a full object, search_columns to find objects/columns, get_ddl for CREATE TABLE, and graph_neighbors / path_between to explore how objects connect. Not sure which layer a term lives in? search_all spans schema, facilities and programs in one call. APPLICATION layer: the client menu tree of UI facilities (screens / reports / inquiries / maintenance functions). Use facility_stats to orient, list_facilities / search_facilities to find a screen, lookup_facility for a facility's program, help, the tables it touches, and the facilities it invokes / is in

Reported Aug 17, 2026, 05:04 AM UTC.

Check history

Oldest to newest. Each row is one recorded check.

  1. responds
    MCP initialize · 8s limit · HTTP 200 · 425ms
  2. responds
    MCP initialize · 8s limit · HTTP 200 · 295ms