_ registry / mcp streamable-http · checked 1h ago

rossdata.dev

https://mcp.rossdata.dev

Registry code: ce08711dceead758

api record

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…

endpoint
https://mcp.rossdata.dev/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is rossdata.dev live?
Yes — it answered the hub's last check (checked 1h ago). It answered 99% of checks over the last 30 days.
Is rossdata.dev free to use?
Yes — the hub reached it with no key and no payment.
What tools does rossdata.dev have?
21 tools: path_between, table_facilities, facility_programs, graph_neighbors, table_programs, program_facilities, lookup_facility, find_column, ….
Is rossdata.dev safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
98.8%

90 days 99.3%· all time 99.3%

latency
239ms

last good check

priced tools
0

of 21 tools

_ answered our checks, 90 days 440 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
used for
  • look up an erp table schema
  • get create table ddl
  • find a column across tables
  • find programs behind a ui screen
  • trace links between database objects
takes → gives
text → data, code
tools
21 reads
note
documentation mirror
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 21 tools
10 open 11 never probed 10 of 21 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • list_facilities reads open 1h ago

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "q": {
          "type": "string",
          "description": "Name or code substring, e.g. CHECK or AP_"
        },
        "class": {
          "type": "string",
          "description": "Class filter: REPORT | MAINTENANCE | INQUIRY | UPDATE | TRANSACTION | ARCHIVE | CODES"
        },
        "limit": {
          "type": "integer",
          "maximum": 1000,
          "minimum": 1,
          "description": "Max facilities (default 100)"
        },
        "offset": {
          "type": "integer",
          "minimum": 0,
          "description": "Pagination offset (default 0)"
        },
        "system": {
          "type": "string",
          "description": "System filter, e.g. ACCOUNTS_PAYABLE or GENERAL_LEDGER"
        },
        "database": {
          "type": "string",
          "description": "Database filter: FIN or MAN"
        },
        "withTables": {
          "type": "boolean",
          "description": "Only facilities with a known table cluster (default false)"
        }
      },
      "additionalProperties": false
    }
    arguments 37 lines
  • program_stats reads open 8h ago

    Overview of the Ross ERP 8.0 program catalog — every 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.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • schema_stats reads open 8h ago

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • search_programs reads open 15h ago

    Search Ross ERP 8.0 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'.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "maximum": 100,
          "minimum": 1,
          "description": "Max results (default 25)"
        },
        "query": {
          "type": "string",
          "description": "Search text, e.g. check register or AP_A_002"
        }
      },
      "additionalProperties": false
    }
    arguments 19 lines
  • search_columns reads open 15h ago

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

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "maximum": 100,
          "minimum": 1,
          "description": "Max results per group (default 25)"
        },
        "query": {
          "type": "string",
          "description": "Search text, e.g. posting_date or GL_ACCOUNTS"
        }
      },
      "additionalProperties": false
    }
    arguments 19 lines
  • search_facilities reads open 15h ago

    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'.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "maximum": 100,
          "minimum": 1,
          "description": "Max results (default 25)"
        },
        "query": {
          "type": "string",
          "description": "Search text, e.g. check register or AP_A"
        }
      },
      "additionalProperties": false
    }
    arguments 19 lines
  • search_all reads open 5h ago

    Cross-domain search in one call — spans schema objects, columns, UI facilities and 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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "type": {
          "enum": [
            "all",
            "object",
            "column",
            "facility",
            "program"
          ],
          "type": "string",
          "description": "Restrict to one domain (default all). 'table' is accepted as an alias for object."
        },
        "limit": {
          "type": "integer",
          "maximum": 100,
          "minimum": 1,
          "description": "Max results per domain (default 25)"
        },
        "query": {
          "type": "string",
          "description": "Search text, e.g. check register or posting_date"
        }
      },
      "additionalProperties": false
    }
    arguments 30 lines
  • list_objects reads open 1h ago

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "q": {
          "type": "string",
          "description": "Name substring filter, e.g. GL_"
        },
        "db": {
          "type": "string",
          "description": "Database filter, e.g. FIN or MAN"
        },
        "type": {
          "type": "string",
          "description": "Object type filter: table | view | procedure | function"
        },
        "limit": {
          "type": "integer",
          "maximum": 1000,
          "minimum": 1,
          "description": "Max objects (default 100)"
        },
        "module": {
          "type": "string",
          "description": "Module filter, e.g. GL or PO"
        },
        "offset": {
          "type": "integer",
          "minimum": 0,
          "description": "Pagination offset (default 0)"
        }
      },
      "additionalProperties": false
    }
    arguments 33 lines
  • facility_stats reads open 1h ago

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • list_programs reads open 8h ago

    Browse and filter Ross ERP 8.0 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.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "q": {
          "type": "string",
          "description": "Substring of basename or title, e.g. check_register"
        },
        "type": {
          "type": "string",
          "description": "Program-type letter, e.g. r (report), m (maintenance), i (inquiry), s (server)"
        },
        "layer": {
          "type": "string",
          "description": "Source layer: base | vendor-core"
        },
        "limit": {
          "type": "integer",
          "maximum": 1000,
          "minimum": 1,
          "description": "Max programs (default 100)"
        },
        "module": {
          "type": "string",
          "description": "Module filter, e.g. ap, gl, ic, sop"
        },
        "offset": {
          "type": "integer",
          "minimum": 0,
          "description": "Pagination offset (default 0)"
        },
        "titled": {
          "type": "boolean",
          "description": "Only programs that declare a TITLE program-id (default false)"
        }
      },
      "additionalProperties": false
    }
    arguments 37 lines
  • path_between reads unknown never probed

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

    mcp-tool

    {
      "type": "object",
      "required": [
        "from",
        "to"
      ],
      "properties": {
        "to": {
          "type": "string",
          "description": "Destination object name"
        },
        "from": {
          "type": "string",
          "description": "Start object name"
        }
      },
      "additionalProperties": false
    }
    arguments 18 lines
  • table_facilities reads unknown never probed

    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?'.

    mcp-tool

    {
      "type": "object",
      "required": [
        "table"
      ],
      "properties": {
        "table": {
          "type": "string",
          "description": "Table name, e.g. GL_ACCOUNTS"
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • facility_programs reads unknown never probed

    Cross-link a UI facility to the 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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "code"
      ],
      "properties": {
        "code": {
          "type": "string",
          "description": "Facility code, e.g. AP_A_002"
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • graph_neighbors reads unknown never probed

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

    mcp-tool

    {
      "type": "object",
      "required": [
        "name"
      ],
      "properties": {
        "name": {
          "type": "string",
          "description": "Object name, e.g. GL_ACCOUNTS"
        },
        "limit": {
          "type": "integer",
          "maximum": 500,
          "minimum": 1,
          "description": "Max neighbours (default 100)"
        }
      },
      "additionalProperties": false
    }
    arguments 19 lines
  • table_programs reads unknown never probed

    Reverse lookup: which standard 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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "table"
      ],
      "properties": {
        "table": {
          "type": "string",
          "description": "Table name, e.g. GL_ACCOUNTS"
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • program_facilities reads unknown never probed

    Reverse of facility_programs: which UI facilities (menu screens / reports / inquiries) a 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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "type": "string",
          "description": "Program id or basename, e.g. AP_I_001 or ap_i_vendors"
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • lookup_facility reads unknown 11h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "code"
      ],
      "properties": {
        "code": {
          "type": "string",
          "description": "Facility code, e.g. AP_A_002"
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • find_column reads unknown 11h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "name"
      ],
      "properties": {
        "name": {
          "type": "string",
          "description": "Column name, e.g. POSTING_DATE or GL_ACCOUNT"
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • lookup_table reads unknown 5h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "name"
      ],
      "properties": {
        "name": {
          "type": "string",
          "description": "Object name, e.g. GL_ACCOUNTS or ACCOUNT_TYPES"
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • get_ddl reads unknown 11h ago

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

    mcp-tool

    {
      "type": "object",
      "required": [
        "name"
      ],
      "properties": {
        "name": {
          "type": "string",
          "description": "Table name, e.g. GL_ACCOUNTS"
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • lookup_program reads unknown 5h ago

    Full detail for one Ross ERP 8.0 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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "type": "string",
          "description": "Program id or basename, e.g. AP_A_002 or ap_a_check_register"
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id ce08711dceead758.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/ce08711dceead758/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/ce08711dceead758/badge.svg)](https://brick.blue/agent/ce08711dceead758?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.