Ross ERP Data Dictionary

REMOTE · MCP.ROSSDATA.DEV · SCANNED AUG 6

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

Available components

67 67 Trust /100

Trust breakdown (6 categories)

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. How we score →

Endpoint Security63

The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
Authorisation not fully verified: no authorisation is required to call this server, and 21 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail

Transport & Reachability100

Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass

Schema Quality & AI Usability77

AI-judged instruction clarity (excellent).Pass
Context-footprint check failed: tool/resource definitions use about 2594 tokens (~123/item across 21 items; 21 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
Usage-examples check failed: none of the tools include examples. See how to fix → Fail

Stability & Change Management7

Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial

Tool Coverage100

100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
100% of tool parameters carry a description.Pass

Capabilities100

Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · mcp.rossdata.dev

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add --transport http dev-rossdata-data-dictionary https://mcp.rossdata.dev/mcp

# ~/.codex/config.toml

[mcp_servers.dev-rossdata-data-dictionary]
url = "https://mcp.rossdata.dev/mcp"

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-rossdata-data-dictionary": {
      "type": "remote",
      "url": "https://mcp.rossdata.dev/mcp",
      "enabled": true
    }
  }
}

# add to OpenClaw

openclaw mcp add dev-rossdata-data-dictionary --url https://mcp.rossdata.dev/mcp --transport streamable-http

# ~/.hermes/config.yaml

mcp_servers:
  dev-rossdata-data-dictionary:
    url: "https://mcp.rossdata.dev/mcp"

// mcp.json

{
  "mcpServers": {
    "dev-rossdata-data-dictionary": {
      "type": "http",
      "url": "https://mcp.rossdata.dev/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

6 Aug 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
5 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
4 Aug 26 66

First indexed and scored.

Show 2 earlier entries Hide earlier entries

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 6 Aug 2026 · Probed https://mcp.rossdata.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject	Issuer	Valid from	Valid until	Key	Signature	Serial
CN=*.rossdata.dev	CN=YR1,O=Let's Encrypt,C=US	3 Aug 2026	1 Nov 2026	RSA 2048	SHA256-RSA	6480f7b12ec918d60d8b2102a5b1571bedd
SANs: *.rossdata.dev, rossdata.dev
CN=YR1,O=Let's Encrypt,C=US (CA)	CN=Root YR,O=ISRG,C=US	3 Sept 2025	2 Sept 2028	RSA 2048	SHA256-RSA	a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA)	CN=ISRG Root X1,O=Internet Security Research Group,C=US	13 May 2026	2 Sept 2032	RSA 4096	SHA256-RSA	f24b6d17f9d9ad7cb1c9fea78782699f

DNSSEC insecure

Validation of mcp.rossdata.dev. — Not signed

Zone	DS	Keys	Algorithms	Outcome
.	trust_anchor	20326, 38696	8, 8	Verified
dev.	present	60074	8	Verified
rossdata.dev.	absent			Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation

Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result	No authorisation required
HTTP status	200

Header	Value
strict-transport-security	max-age=63072000

Transports 2 probes

Transport	URL	Outcome	Status	Location
streamable-http	https://mcp.rossdata.dev/mcp	Verified	200
http (plaintext)	http://mcp.rossdata.dev/mcp	HTTPS enforced	308	https://mcp.rossdata.dev/mcp

MCP tools — 21 exposed · ~2,237 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens

facility_programs ~102

Cross-link a UI facility to the vanilla program(s) that implement it — 'what code runs this screen?'. Each program carries a match label: declared (named by the facility's menu entry, authoritative) or titleId (TITLE id equals the facility code). Complements lookup_facility (which gives the facility's tables and call graph). Metadata only — no source body.

Input Output Examples

Name	Type	Req	Description
code	string	yes	Facility code, e.g. AP_A_002

No output schema declared.

No examples provided.

facility_stats ~86

Overview of the Ross ERP 8.0 application layer — the client menu tree of UI facilities (screens, reports, inquiries, maintenance functions): total facilities, and their breakdown by system (e.g. ACCOUNTS_PAYABLE), database (FIN/MAN) and class (REPORT, MAINTENANCE, INQUIRY, ...). Use this first to orient before browsing facilities.

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

find_column ~68

Look up a single column by exact name across the whole Ross ERP 8.0 schema: its description, valid values, notes, every table that carries it, and any foreign-key roles it plays.

Input Output Examples

Name	Type	Req	Description
name	string	yes	Column name, e.g. POSTING_DATE or GL_ACCOUNT

No output schema declared.

No examples provided.

get_ddl ~56

Return the CREATE TABLE (DDL) for a Ross ERP 8.0 table, with column descriptions as comments plus primary-key and foreign-key constraints.

Input Output Examples

Name	Type	Req	Description
name	string	yes	Table name, e.g. GL_ACCOUNTS

No output schema declared.

No examples provided.

graph_neighbors ~67

List the knowledge-graph neighbours of an object — the programs, tables, views and procedures directly connected to it, with relationship type and direction.

Input Output Examples

Name	Type	Req	Description
limit	integer	—	Max neighbours (default 100)
name	string	yes	Object name, e.g. GL_ACCOUNTS

No output schema declared.

No examples provided.

list_facilities ~195

Browse and filter Ross ERP 8.0 UI facilities (menu screens/functions). Filter by system, database, class, a name/code substring, or withTables (only facilities whose table cluster is known); paginate with limit/offset. Returns summaries — use lookup_facility for full detail.

Input Output Examples

Name	Type	Req	Description
class	string	—	Class filter: REPORT \| MAINTENANCE \| INQUIRY \| UPDATE \| TRANSACTION \| ARCHIVE \| CODES
database	string	—	Database filter: FIN or MAN
limit	integer	—	Max facilities (default 100)
offset	integer	—	Pagination offset (default 0)
q	string	—	Name or code substring, e.g. CHECK or AP_
system	string	—	System filter, e.g. ACCOUNTS_PAYABLE or GENERAL_LEDGER
withTables	boolean	—	Only facilities with a known table cluster (default false)

No output schema declared.

No examples provided.

list_objects ~148

Browse and filter Ross ERP 8.0 objects (tables / views / procedures / functions). Filter by type, database, module, or a name substring; paginate with limit/offset. Returns object summaries — use lookup_table for full detail.

Input Output Examples

Name	Type	Req	Description
db	string	—	Database filter, e.g. FIN or MAN
limit	integer	—	Max objects (default 100)
module	string	—	Module filter, e.g. GL or PO
offset	integer	—	Pagination offset (default 0)
q	string	—	Name substring filter, e.g. GL_
type	string	—	Object type filter: table \| view \| procedure \| function

No output schema declared.

No examples provided.

list_programs ~240

Browse and filter Ross ERP 8.0 vanilla programs (application source, metadata only). Filter by module (ap, gl, ic, sop, ...), type (a=archive, i=inquiry, m=maintenance, r=report, s=server, l=load, u=utility, ...), layer (base | vendor-core), titled (only programs that declare a TITLE id), or a substring of basename/title; paginate with limit/offset. Returns summaries — use lookup_program for full detail.

Input Output Examples

Name	Type	Req	Description
layer	string	—	Source layer: base \| vendor-core
limit	integer	—	Max programs (default 100)
module	string	—	Module filter, e.g. ap, gl, ic, sop
offset	integer	—	Pagination offset (default 0)
q	string	—	Substring of basename or title, e.g. check_register
titled	boolean	—	Only programs that declare a TITLE program-id (default false)
type	string	—	Program-type letter, e.g. r (report), m (maintenance), i (inquiry), s (server)

No output schema declared.

No examples provided.

lookup_facility ~116

Full detail for one Ross ERP 8.0 UI facility by code: its name, system, database, class, GEMBASE program, help text, menu paths, the physical table cluster it touches — core (the working set the screen is built on) and reference (control/lookup tables) — and its call graph: the facilities this one invokes (calls) and the facilities that invoke it (calledBy), parsed from the program source.

Input Output Examples

Name	Type	Req	Description
code	string	yes	Facility code, e.g. AP_A_002

No output schema declared.

No examples provided.

lookup_program ~187

Full detail for one Ross ERP 8.0 vanilla program, by TITLE program-id (e.g. AP_A_002) or source basename (e.g. ap_a_check_register): its module, type, layer, declared title, internal PROCEDURE_FORM procedures, the Data Dictionary tables it references — each classified read vs read-write (a write is a FIND IN.../LOCK=WRITE update, an ADD, or a DELETE) with a writeCount — its call graph (the programs it invokes and the programs that invoke it, from PERFORM "GEM<mod>:<prog>"), the menu facilities it backs, and — for programs with no TITLE label — a display name carried from the menu facility's registry description. Metadata only — no source body.

Input Output Examples

Name	Type	Req	Description
id	string	yes	Program id or basename, e.g. AP_A_002 or ap_a_check_register

No output schema declared.

No examples provided.

lookup_table ~74

Full schema for a Ross ERP 8.0 object (table / view / procedure / function): columns with type, nullability, keys, descriptions and valid values, foreign keys in and out, related tables, and usage.

Input Output Examples

Name	Type	Req	Description
name	string	yes	Object name, e.g. GL_ACCOUNTS or ACCOUNT_TYPES

No output schema declared.

No examples provided.

path_between ~57

Find the shortest path between two objects in the Ross ERP 8.0 knowledge graph (how A reaches B through calls / references / accesses).

Input Output Examples

Name	Type	Req	Description
from	string	yes	Start object name
to	string	yes	Destination object name

No output schema declared.

No examples provided.

program_facilities ~107

Reverse of facility_programs: which UI facilities (menu screens / reports / inquiries) a vanilla program backs — 'what screens does this program run?'. One program often serves several facilities. Lookup by TITLE id (e.g. AP_I_001) or basename (e.g. ap_i_vendors); each facility carries the same declared / titleId match label.

Input Output Examples

Name	Type	Req	Description
id	string	yes	Program id or basename, e.g. AP_I_001 or ap_i_vendors

No output schema declared.

No examples provided.

program_stats ~122

Overview of the Ross ERP 8.0 program catalog — every vanilla application-source program (metadata only, no source body): total programs, how many declare a TITLE id, how many carry Data Dictionary table links, total program→table edges, read/write counts (withWrites programs, writeEdges program→table write edges), base vs vendor-core split, program→program call-graph counts (programs with outbound calls, total call edges) and how many back a menu facility, plus the module and type breakdowns. Use this first to orient before browsing programs.

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

schema_stats ~57

Overview of the Ross ERP 8.0 schema in one call: object counts by type, module list, total/distinct columns, audit-twin pairs, and the top tables/columns/modules. Use this first to orient before drilling in.

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search_all ~142

Cross-domain search in one call — spans schema objects, columns, UI facilities and vanilla programs at once. Use this when you don't yet know which layer a term lives in (e.g. 'check register' is a screen, a program and a table). Scope to one layer with type = object | column | facility | program (default all); limit is per domain.

Input Output Examples

Name	Type	Req	Description
limit	integer	—	Max results per domain (default 25)
query	string	yes	Search text, e.g. check register or posting_date
type	string	—	Restrict to one domain (default all). 'table' is accepted as an alias for object.

No output schema declared.

No examples provided.

search_columns ~65

Search the Ross ERP 8.0 schema by name (and column descriptions). Returns matching objects and columns.

Input Output Examples

Name	Type	Req	Description
limit	integer	—	Max results per group (default 25)
query	string	yes	Search text, e.g. posting_date or GL_ACCOUNTS

No output schema declared.

No examples provided.

search_facilities ~85

Search Ross ERP 8.0 UI facilities by code, name, help text, program or tag. Use this to find the screen/report for a task, e.g. 'check register' or 'purchase order receipts'.

Input Output Examples

Name	Type	Req	Description
limit	integer	—	Max results (default 25)
query	string	yes	Search text, e.g. check register or AP_A

No output schema declared.

No examples provided.

search_programs ~86

Search Ross ERP 8.0 vanilla programs by basename, TITLE program-id, title, module or type. Use this to find the program behind a task, e.g. 'check register' or 'ap_a'.

Input Output Examples

Name	Type	Req	Description
limit	integer	—	Max results (default 25)
query	string	yes	Search text, e.g. check register or AP_A_002

No output schema declared.

No examples provided.

table_facilities ~98

Reverse lookup: which UI facilities (screens/reports/programs) touch a given Ross ERP 8.0 table — split into core (facilities whose working set includes it) and reference (facilities that use it as a control/lookup), each with how many times the program source accesses it. Answers 'what screens read or write this table?'.

Input Output Examples

Name	Type	Req	Description
table	string	yes	Table name, e.g. GL_ACCOUNTS

No output schema declared.

No examples provided.

table_programs ~79

Reverse lookup: which vanilla Ross ERP 8.0 programs reference a given table (validated against the Data Dictionary). Answers 'what code touches this table?' — complements table_facilities (which answers 'what screens touch it?'). Metadata only — no source body.

Input Output Examples

Name	Type	Req	Description
table	string	yes	Table name, e.g. GL_ACCOUNTS

No output schema declared.

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

4 Aug 6 Aug