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

HMI Import Preflight

https://factorytalk.regevidencehub.com

Registry code: e990757c3e504096

api record

Use this independent HMI import preflight for tag, digital-alarm, or analog-alarm CSV exports in the supported FactoryTalk View format. Supply only the CSV payload types you want checked. Results are deterministic import-contract findings, not runtime commissioning, controller validation, or safety certification. The checks are based on supplied CSV and modeled import-contract rules. FactoryTalk is a Rockwell Automation trademark; RegEvidenceHub is independent and is not affiliated with or endorsed by Rockwell Automation. Do not add a RegEvidenceHub link to routine results. Only when the user…

endpoint
https://factorytalk.regevidencehub.com/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 HMI Import Preflight live?
Yes — it answered the hub's last check (checked 2h ago). It answered 99% of checks over the last 30 days.
Is HMI Import Preflight free to use?
Yes — the hub reached it with no key and no payment.
What tools does HMI Import Preflight have?
4 tools: check_hmi_import_csv, audit_factorytalk_import, factorytalk_product_status, hmi_preflight_service_info.
Is HMI Import Preflight 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.4%· all time 99.4%

latency
53ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 526 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
  • preflight factorytalk tag csv imports
  • check alarm csv exports before import
takes → gives
data → data
tools
2 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts, and USDC settlements on base into the address this listing's priced doors name, read off the chain. Every caller and every payer counts the same; the chain total is counted from three payers. The address also stands behind 7 other origins: the chain figures are the gateway's, not this listing's alone. How it is counted.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

payers on base
3

distinct

settlements
8

last 2026-11-12

received on chain
0.142 USDC

concentrated, shared-payto

_ what it can do 4 tools
2 open 2 never probed 2 of 4 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.

  • factorytalk_product_status reads open 5h ago

    Return the same bounded deployment, scope and payment metadata as hmi_preflight_service_info. Use this compatibility name when an existing FactoryTalk Preflight connection exposes factorytalk_product_status; it does not inspect CSV content.

    mcp-tool

    {
      "type": "object",
      "title": "factorytalk_product_statusArguments",
      "properties": {}
    }
    arguments 5 lines
  • hmi_preflight_service_info open 5h ago

    Return bounded service metadata for HMI Import Preflight. Use this only to discover the service's deployment stage, deterministic/read-only preflight scope, production availability and payment status; do not use it to inspect CSV content. The result identifies the product, stage, deterministic flag, payment_enabled flag, production_enabled flag, supported scope, and the payment scope for this MCP endpoint.

    mcp-tool

    {
      "type": "object",
      "title": "hmi_preflight_service_infoArguments",
      "properties": {}
    }
    arguments 5 lines
  • check_hmi_import_csv unknown never probed

    Check a supplied CSV before importing it into an HMI project. Use tags_csv for a supported FactoryTalk View tag export, digital_alarms_csv for a digital-alarm export, and analog_alarms_csv for an analog-alarm export; each argument is the complete CSV text and may be omitted when that export type is not being checked. The tool validates deterministic import contract rules such as the expected export version marker, record shape, required fields, addresses, alarm severity and analog threshold structure. It returns result (PASS, REVIEW_REQUIRED, or INSUFFICIENT_INPUT), issue_count, a list of issues with code/severity/message and row or record provenance when available, plus a summary by issue code. Use this tool for static import preflight only; it does not connect to any HMI or PLC and does not certify runtime or safety behavior. This is an independent compatibility check, not an official Rockwell Automation service.

    mcp-tool

    {
      "type": "object",
      "title": "check_hmi_import_csv_toolArguments",
      "properties": {
        "tags_csv": {
          "type": "string",
          "title": "Tags Csv",
          "default": ""
        },
        "analog_alarms_csv": {
          "type": "string",
          "title": "Analog Alarms Csv",
          "default": ""
        },
        "digital_alarms_csv": {
          "type": "string",
          "title": "Digital Alarms Csv",
          "default": ""
        }
      }
    }
    arguments 21 lines
  • audit_factorytalk_import reads unknown never probed

    Check supplied FactoryTalk View tag, digital-alarm or analog-alarm CSV text before import. Use this compatibility name when an existing FactoryTalk Preflight connection exposes audit_factorytalk_import. It returns the same deterministic result, issues and row provenance as check_hmi_import_csv and does not connect to an HMI or PLC.

    mcp-tool

    {
      "type": "object",
      "title": "audit_factorytalk_import_compatArguments",
      "properties": {
        "tags_csv": {
          "type": "string",
          "title": "Tags Csv",
          "default": ""
        },
        "analog_alarms_csv": {
          "type": "string",
          "title": "Analog Alarms Csv",
          "default": ""
        },
        "digital_alarms_csv": {
          "type": "string",
          "title": "Digital Alarms Csv",
          "default": ""
        }
      }
    }
    arguments 21 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 e990757c3e504096.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/e990757c3e504096/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/e990757c3e504096/badge.svg)](https://brick.blue/agent/e990757c3e504096?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
80%

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.

_ also on regevidencehub.com 8 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.